Rule-based routing to resources through a network

• US 9,197,538 B2
• Filed: 10/24/2013
• Issued: 11/24/2015
• Est. Priority Date: 12/10/2003
• Status: Expired due to Fees

• Current Assignee: Aventail LLC
• Original Assignee: Aventail LLC
• Inventors: Hopen, Chris, Sauve, Bryan, Hoover, Paul, Perry, Bill
• Primary Examiner(s): Hirl, Joseph P
• Assistant Examiner(s): BEHESHTI SHIRAZI, SAYED ARESH
• Application Number:
  US14/061,988
• Publication Number:
  US 20140053237A1
• Time in Patent Office: 761 Days
• Field of Search: 726/12, 726/13, 726/15, 370/397, 709/204, 709/217, 709/223, 709/224, 709/225, 709/229, 709/238, 709/249
• US Class Current: 1/1
• CPC Class Codes: G06F 21/6218 to a system of files or objects, e.g. local or distributed file system or database
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 45/14 Routing performance; Theoretical aspects
• CPC Class Codes: H04L 47/70 Admission control; Resource allocation
• CPC Class Codes: H04L 61/5007 Internet protocol [IP] addresses
• CPC Class Codes: H04L 63/0272 Virtual private networks
• CPC Class Codes: H04L 63/029 Firewall traversal, e.g. tunnelling or, creating pinholes
• CPC Class Codes: H04L 63/10 for controlling access to devices or network resources
• CPC Class Codes: H04L 63/101 Access control lists [ACL]
• CPC Class Codes: H04L 67/63 Routing a service request depending on the request content or context

Abstract

Techniques for determining which resource access requests are handled locally at a remote computer, and which resource access requests are routed or “redirected” through a virtual private network. One or more routing or “redirection” rules are downloaded from a redirection rule server to a remote computer. When the node of the virtual private network running on the remote computer receives a resource access request, it compares the identified resource with the rules. Based upon how the identified resource matches one or more rules, the node will determine whether the resource access request is redirected through the virtual private network or handled locally (e.g., retrieved locally from another network). A single set of redirection rules can be distributed to and employed by a variety of different virtual private network communication techniques.

Claims

1. A method of creating redirection rules for routing resource access requests from a computer to a network, the method comprising:

receiving, using a hardware processor, input at a user interface that identifies an inclusion redirection rule to associate with a resource, wherein a processor executing instructions out of a memory creates creating an inclusion redirection rule for at least one existing resource definition that is associated with the resource;

receiving an input over the user interface that identifies an exclusion redirection rule to associate with the resource the input associated with an exclusion resource definition, wherein the processor executing instructions out of the memory creates an exclusion redirection rule for the exclusion resource definition that is associated with the resource;

receiving a request to access an internet protocol (IP) address over a network interface;

ignoring the request to access the IP address after comparing an IP address range size associated with the inclusion redirection rule with an IP address range size associated with the exclusion redirection rule, and when the IP address exclusion rule range size matches the IP address inclusion rule range size.

2. The method recited in claim 1, further comprising combining the inclusion redirection rule with the exclusion redirection rule into a redirection rule list.

3. The method recited in claim 1, wherein the existing resource definition is maintained by a policy server for controlling access to the resource defined in the at least one existing resource definition.

4. The method recited in claim 1, further comprising:

receiving input with a second resource definition; and

creating a second inclusion redirection rule for the second resource definition.

5. The method recited in claim 1, wherein the existing resource definition includes the Internet protocol (IP) address for the resource.

6. The method recited in claim 1, wherein the existing resource definition includes a name for the resource.

7. The method recited in claim 6, wherein the name is a domain name.

8. The method recited in claim 6, wherein the name is a host name.

9. The method recited in claim 1, wherein the existing resource definition includes a universal resource locator (URL) address for the resource.

10. The method recited in claim 1, wherein the exclusion resource definition includes an Internet protocol (IP) address for the resource.

11. The method recited in claim 1, wherein the exclusion resource definition includes a name for the exclusion resource.

12. The method recited in claim 11, wherein the name is a domain name.

13. The method recited in claim 11, wherein the name is a host name.

14. The method recited in claim 1, wherein the exclusion resource definition includes a universal resource locator (URL) address for the exclusion resource.