US 12,149,506 B2
Data routing options for a VPN
Brian Lutz, Philadelphia, PA (US); Kevin Cunningham, Swarthmore, PA (US); Alexander Gizis, Philadelphia, PA (US); and Brian Prodoehl, Plymouth Meeting, PA (US)
Assigned to Connectify, Inc., Philadelphia, PA (US)
Filed by Connectify, Inc., Philadelphia, PA (US)
Filed on Jul. 7, 2023, as Appl. No. 18/219,362.
Application 18/219,362 is a continuation of application No. 17/236,929, filed on Apr. 21, 2021, granted, now 11,743,235.
Claims priority of provisional application 63/014,638, filed on Apr. 23, 2020.
Prior Publication US 2023/0353541 A1, Nov. 2, 2023
This patent is subject to a terminal disclaimer.
Int. Cl. H04L 9/40 (2022.01); H04L 12/46 (2006.01); H04L 45/00 (2022.01)
CPC H04L 63/0272 (2013.01) [H04L 12/4641 (2013.01); H04L 45/72 (2013.01); H04L 63/0236 (2013.01)] 20 Claims
OG exemplary drawing
 
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.