DNS-based captive portal with integrated transparent proxy to protect against user device caching incorrect IP address

• US 9,756,019 B2
• Filed: 05/15/2014
• Issued: 09/05/2017
• Est. Priority Date: 05/16/2013
• Status: Active Grant

• Current Assignee: Guest-tek Interactive Entertainment Ltd.
• Original Assignee: Guest-tek Interactive Entertainment Ltd.
• Inventors: Warrick, Peter S., Ong, David T.
• Primary Examiner(s): Pyzocha, Michael
• Application Number:
  US14/279,008
• Publication Number:
  US 20140344890A1
• Time in Patent Office: 1,209 Days
• CPC Class Codes: G06F 21/10 Protecting distributed programs or content, e.g. vending or licensing of copyrighted material protection in video systems or pay television H04N7/16 ; Digital rights management [DRM]
• CPC Class Codes: H04L 61/4511 using domain name system [DNS]
• CPC Class Codes: H04L 63/0263 Rule management
• CPC Class Codes: H04L 63/0281 Proxies
• CPC Class Codes: H04L 63/08 for authentication of entities cryptographic mechanisms or cryptographic arrangements for entity authentication H04L9/32

Abstract

A captive portal system includes a login database, a web server, and a name server. The name server receives a DNS request from a user device, queries the login database to determine whether the user device is logged in, and responds to the DNS request with the IP address of the web server as a resolved IP address of the specified domain name when the user device is not logged in. The web server accepts a connection request from the user device to the IP address of the web server, receives an HTTP request specifying a non-local target URL from the user device, queries the login database to determine whether the user device is logged in according to the source address of the user device, and acts as a transparent proxy between the user device and the non-local target URL when the user device is logged in.

Claims

1. A captive portal system for controlling access from user devices to an external network, the captive portal system comprising:

a storage device storing a login database, the login database specifying source addresses of user devices that are currently logged in;

a web server coupled to the storage device and a computer network, and configured with an IP address accessible on the computer network; and

a name server coupled to the storage device and the computer network, and operable to resolve domain names to IP addresses;

wherein the name server is configured to;

receive a DNS request from a user device to resolve a target domain name;

query the login database to determine whether the user device is logged in according to a source address of the user device;

respond to the DNS request with the IP address of the web server as a resolved IP address of the target domain name when the user device is not logged in; and

respond to the DNS request with a correct IP address of the target domain name in response to the name server determining that the user device is logged in; and

the web server is configured to;

accept a connection request from the user device to the IP address of the web server, the connection request to the IP address of the web server occurring as a result of the name server previously determining the user device to not be logged in and the user device caching the IP address of the web server provided by the name server as the resolved IP address of the target domain name;

receive an HTTP request specifying a non-local target URL from the user device over the connection, wherein the non-local target URL is not a URL provided by the web server;

query the login database to determine whether the user device is logged in according to the source address of the user device;

respond to the HTTP request by acting as a transparent proxy between the user device and the non-local target URL to thereby allow the user device to receive content of the non-local target URL in response to the web server determining that the user device is logged in; and

respond to the HTTP request with alternate content different than that provided at the non-local target URL when the user device is not logged in.

2. The captive portal system of claim 1, wherein:

the storage device further stores a list of cleared sites; and

the name server is further configured to determine whether the target domain name is a cleared site and to respond to the DNS request with the correct IP address of the target domain name in response to the name server determining that the target domain name is a cleared site.

3. The captive portal system of claim 1, wherein:

the storage device further stores a list of cleared sites; and

the web server is further configured to determine whether the non-local target URL is a cleared site and to respond to the HTTP request by acting as the transparent proxy between the user device and the non-local target URL to thereby allow the user device to receive the content of the non-local target URL in response to the web server determining that the non-local target URL is a cleared site.

4. The captive portal system of claim 1, wherein the alternate content is a browser redirection message causing a web browser running on the user device to automatically redirect to a login portal.

5. The captive portal system of claim 1, wherein the alternate content is a first page of content from a login portal.

6. The captive portal system of claim 1, wherein the alternate content is a splash page with a user-clickable link or button to a login portal.

7. The captive portal system of claim 1, wherein the web server is further configured to:

retrieve original content from another web server; and

generate the alternate content by modifying the original content retrieved from the other web server.

8. The captive portal system of claim 1, wherein:

the HTTP request is received from the user device over a secure connection and specifies a non-local HTTPS target URL; and

the web server is further configured to decrypt and re-encrypt data while acting as the transparent proxy between the user device and the non-local target URL to thereby allow the user device to receive the content of the non-local HTTPS target URL in response to the web server determining that the user device is logged in.

9. The captive portal system of claim 1, further comprising a firewall configured with rules to redirect all DNS queries received from the user device to the name server.

10. The captive portal system of claim 9, wherein:

the name server comprises a first name server for logged in devices, and a second name server for non-logged in devices; and

the firewall is configured with rules to redirect all DNS queries from logged in user devices to the first name server, and to redirect all DNS queries received from non-logged in user devices to the second name server.

11. The captive portal system of claim 1, further comprising a firewall configured with a default rule to block all traffic from non-logged in user devices to non-cleared addresses on the external network.

12. A method of controlling access within a captive portal from user devices to an external network, the method comprising:

tracking in a login database source addresses of user devices that are currently logged in;

receiving, by a name server, a DNS request from a user device to resolve a target domain name;

querying, by the name server, the login database to determine whether the user device is logged in according to a source address of the user device;

responding, by the name server, to the DNS request with an IP address of a web server accessible to the user device from within the captive portal as a resolved IP address of the target domain name when the user device is not logged in;

responding, by the name server, to the DNS request with a correct IP address of the target domain name in response to the name server determining that the user device is logged in;

accepting, by the web server accessible to the user device from within the captive portal, a connection request from the user device to the IP address of the web server, the connection request to the IP address of the web server occurring as a result of the name server previously determining the user device to not be logged in and the user device caching the IP address of the web server provided by the name server as the resolved IP address of the target domain name;

receiving, by the web server, an HTTP request specifying a non-local target URL from the user device over the connection, wherein the non-local target URL is not a URL provided by the web server;

querying, by the web server, the login database to determine whether the user device is logged in according to the source address of the user device;

responding, by the web server, to the HTTP request by acting as a transparent proxy between the user device and the non-local target URL to thereby allow the user device to receive content of the non-local target URL in response to the web server determining that the user device is logged in; and

responding, by the web server, to the HTTP request with alternate content different than that provided at the non-local target URL when the user device is not logged in.

13. The method of claim 12, further comprising redirecting all DNS queries received from the user device to the name server.

14. The method of claim 13, wherein:

the name server comprises a first name server for logged in devices, and a second name server for non-logged in devices;

the method further comprising;

redirecting all DNS queries from logged in user devices to the first name server; and

redirecting all DNS queries received from non-logged in user devices to the second name server.

15. A non-transitory computer-readable medium comprising computer executable instructions that when executed by one or more computers cause the one or more computers to perform a method of controlling access within a captive portal from user devices to an external network, the method comprising:

tracking in a login database source addresses of user devices that are currently logged in;

receiving, by a name server, a DNS request from a user device to resolve a target domain name;

querying, by the name server, the login database to determine whether the user device is logged in according to a source address of the user device;

responding, by the name server, to the DNS request with an IP address of a web server accessible to the user device from within the captive portal as a resolved IP address of the target domain name when the user device is not logged in;

responding, by the name server, to the DNS request with a correct IP address of the target domain name in response to the name server determining that the user device is logged in;

accepting, by the web server accessible to the user device from within the captive portal, a connection request from the user device to the IP address of the web server, the connection request to the IP address of the web server occurring as a result of the name server previously determining the user device to not be logged in and the user device caching the IP address of the web server provided by the name server as the resolved IP address of the target domain name;

receiving, by the web server, an HTTP request specifying a non-local target URL from the user device over the connection, wherein the non-local target URL is not a URL provided by the web server;

querying, by the web server, the login database to determine whether the user device is logged in according to the source address of the user device;

responding, by the web server, to the HTTP request by acting as a transparent proxy between the user device and the non-local target URL to thereby allow the user device to receive content of the non-local target URL in response to the web server determining that the user device is logged in; and

responding, by the web server, to the HTTP request with alternate content different than that provided at the non-local target URL when the user device is not logged in.

16. A computer server in a captive portal system, the computer server comprising:

a first network interface coupled to a local computer network;

a second network interface coupled to an external computer network;

a memory device storing software instructions; and

one or more processors coupled to the memory device;

wherein, by the one or more processors executing the software instructions loaded from the memory device, the one or more processors are configured to;

receive a DNS request from a user device on the local computer network to resolve a target domain name on the external computer network;

query a login database to determine whether the user device is logged in at a time of the DNS request according to a source address of the user device;

respond to the DNS request with an IP address of the computer server as a resolved IP address of the target domain name when the user device is not logged in at the time of the DNS request;

respond to the DNS request with a correct IP address of the target domain name in response to determining that the user device is logged in at the time of the DNS request;

accept a connection request from the user device on the local computer network to the IP address of the computer server, the connection request coming sometime after the DNS request, the connection request to the IP address of the web server occurring as a result of the name server previously determining the user device to not be logged in and the user device caching the IP address of the web server provided by the name server as the resolved IP address of the target domain name;

receive an HTTP request specifying a non-local target URL from the user device over the connection, wherein the non-local target URL is not a URL provided by the computer server;

query the login database to determine whether the user device is logged in at a time of the HTTP request according to the source address of the user device;

respond to the HTTP request by acting as a transparent proxy between the user device and the non-local target URL to thereby allow the user device to receive content of the non-local target URL in response to determining that the user device is logged in at the time of the HTTP request; and

respond to the HTTP request with alternate content different than that provided at the non-local target URL when the user device is not logged in at the time of the HTTP request.

17. The computer server of claim 16, further comprising:

a storage device storing a list of cleared sites;

wherein the one or more processors are further configured to check whether the target domain name is a cleared site and to respond to the DNS request with the correct IP address of the target domain name in response to determining that the target domain name is a cleared site.

18. The computer server of claim 16, wherein the alternate content is selected from the group consisting of:

a browser redirection message causing a web browser running on the user device to automatically redirect to a login portal;

a first page of content from the login portal; and

a splash page with a user-clickable link or button to the login portal.

19. The computer server of claim 16, wherein the one or more processors are further configured to:

retrieve original content from another web server; and

generate the alternate content by modifying the original content retrieved from the other web server.

20. The computer server of claim 16, wherein:

the HTTP request is received from the user device over a secure connection and specifies a non-local HTTPS target URL; and

the one or more processors are further configured to decrypt and re-encrypt data while acting as the transparent proxy between the user device and the non-local target URL to thereby allow the user device to receive the content of the non-local HTTPS target URL in response to determining that the user device is logged in at the time of the HTTP request.