Data routing options for a VPN

Patent metadata

Field	Value
Publication number	US-12149506-B2
Application number	US-202318219362-A
Country	US
Kind code	B2
Filing date	Jul 7, 2023
Priority date	Apr 23, 2020
Publication date	Nov 19, 2024
Grant date	Nov 19, 2024

Abstract

One example method of operation may include determining whether a data request initiated by a client device to obtain data from a remote server should be forwarded by a virtual private network (VPN) server or outside of the VPN server, forwarding, via the client device, a data fetch outside of the virtual private network (VPN) server in communication with the client device, to obtain the data from the remote server, and the remote server is identified on a list identifying servers requiring non-VPN communications, receiving the data from the remote server, via the client device, outside of the VPN server, forwarding, via the client device, a request for additional data to the VPN server, and receiving the additional data from the VPN server at the client device.

First claim

What is claimed is:

1. A method comprising
determining whether a data request initiated by a client device to obtain data from a remote server should be forwarded by a virtual private network (VPN) server or outside of the VPN server by identifying a domain name of the remote server included in a domain name system (DNS) request associated with the data request and by determining the domain name is on a list, identifying servers requiring non-VPN communications, stored in a routing module of the client device;
forwarding, via the client device, a data fetch outside of the virtual private network (VPN) server in communication with the client device, to obtain the data from the remote server;
receiving the data from the remote server, via the client device, outside of the VPN server;
forwarding, via the client device, a request for additional data to the VPN server; and
receiving the additional data from the VPN server at the client device.

2. The method of claim 1 , comprising
storing an IP address and a VPN or non-VPN server data routing designation, indicating whether to route the data through the VPN server or outside the VPN server, in a VPN client application memory of the client device.

3. The method of claim 1 , comprising
wherein the list comprises one or more of an IP address deny list blocking certain IP addresses from using the VPN server to route the data and an IP address allow list permitting certain IP addresses to use the VPN server to route the data.

4. The method of claim 1 , comprising
wherein the list comprises one or more of a domain name deny list blocking certain domain names from using the VPN server to route the data and a domain name allow list permitting certain domain names to use the VPN server to route the data.

5. The method of claim 2 , comprising
responsive to the DNS request being routed via the non-VPN server route, forwarding the IP address, via the non-VPN server route.

6. The method of claim 5 , comprising
routing future requests associated with the client device identifying the IP address via the non-VPN server route.

7. The method of claim 1 , wherein the data request is initiated from a client device application seeking streaming media content data.

8. A client device comprising
a processor configured to determine whether a data request initiated by the client device to obtain data from a remote server should be forwarded by a virtual private network (VPN) server or outside of the VPN server by identifying a domain name of the remote server included in a domain name system (DNS) request associated with the data request and by determining the domain name is on a list, identifying servers requiring non-VPN communications, stored in a routing module of the client device;
a transmitter configured to forward a data fetch outside of the virtual private network (VPN) server in communication with the client device, to obtain the data from the remote server;
a receiver configured to receive the data from the remote server, via the client device, outside of the VPN server;
wherein the transmitter is further configured forward a request for additional data to the VPN server; and
wherein the receiver is further configured to receive the additional data provided by the VPN server to the client device.

9. The client device of claim 8 , wherein the processor is further configured to
store an IP address and a VPN or non-VPN server data routing designation, indicating whether to route the data through the VPN server or outside the VPN server, in a VPN client application memory of the client device.

10. The client device of claim 8 , wherein the list comprises one or more of an IP address deny list blocking certain IP addresses from using the VPN server to route the data and an IP address allow list permitting certain IP addresses to use the VPN server to route the data.

11. The client device of claim 8 , wherein the list comprises one or more of a domain name deny list blocking certain domain names from using the VPN server to route the data and a domain name allow list permitting certain domain names to use the VPN server to route the data.

12. The client device of claim 9 , wherein the processor is further configured to
responsive to the DNS request being routed via the non-VPN server route, forward the IP address, via the non-VPN server route.

13. The client device of claim 9 , wherein the processor is further configured to
route future requests associated with the client device identifying the IP address via the non-VPN server route.

14. The client device of claim 8 , wherein the data request is initiated from a client device application seeking streaming media content data.

15. A non-transitory computer readable storage medium comprising instructions that when executed cause a processor to perform:
determining whether a data request initiated by a client device to obtain data from a remote server should be forwarded by a virtual private network (VPN) server or outside of the VPN server by identifying a domain name of the remote server included in a domain name system (DNS) request associated with the data request and by determining the domain name is on a list, identifying servers requiring non-VPN communications, stored in a routing module of the client device;
forwarding, via the client device, a data fetch outside of the virtual private network (VPN) server in communication with the client device, to obtain the data from the remote server;
receiving the data from the remote server, via the client device, outside of the VPN server;
forwarding, via the client device, a request for additional data to the VPN server; and
receiving the additional data from the VPN server at the client device.

16. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:
storing an IP address and a VPN or non-VPN server data routing designation, indicating whether to route the data through the VPN server or outside the VPN server, in a VPN client application memory of the client device.

17. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:
wherein the list comprises one or more of an IP address deny list blocking certain IP addresses from using the VPN server to route the data and an IP address allow list permitting certain IP addresses to use the VPN server to route the data.

18. The non-transitory computer readable storage medium of claim 15 , wherein the processor is further configured to perform:
wherein the list comprises one or more of a domain name deny list blocking certain domain names from using the VPN server to route the data and a domain name allow list permitting certain domain names to use the VPN server to route the data.

19. The non-transitory computer readable storage medium of claim 16 , wherein the processor is further configured to perform:
responsive to the DNS request being routed via the non-VPN server route, forwarding the IP address, via the non-VPN server route.

20. The non-transitory computer readable storage medium of claim 19 , wherein the processor is further configured to perform:
routing future requests associated with the client device identifying the IP address via the non-VPN server route.

Assignees

• Connectify Inc

Inventors

• Lutz Brian
• Cunningham Kevin
• Gizis Alexander
• Prodoehl Brian

Classifications

• H04L45/72

  Routing based on the source address · CPC title

• H04L12/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 title

• H04L63/0236

  Filtering by address, protocol, port number or service, e.g. IP-address or URL · CPC title

• H04L63/0272 Primary

  Virtual private networks · CPC title