|This article needs additional citations for verification. (February 2011) (Learn how and when to remove this template message)|
A captive portal is a 'landing' web page, presented by a Layer 3[definition needed] brand or Layer 2 Operator[definition needed] and shown to users before they gain broader access to URL or http-based Internet services. Often used to present a landing or log-in page, the portal intercepts observed packets until such time as the user is authorized to launch browser sessions. After being redirected to a web page which may require authentication, payment, acceptance of EULA/acceptable use policies or other valid credentials that the host and user agree to, the user is granted conditional Internet access. Captive portals are used for a broad range of mobile and pedestrian broadband services, including cable and commercially provided Wi-Fi, home hotspots and others, and can also be used to provide access to enterprise and residential wired networks (such as apartment houses, hotel rooms, business centers).
The login page itself is presented to the client, and is stored either locally at the gateway, or at the web server hosting that page (requiring access to an approved access list, or "white-list", an essential feature of the secure enterprise). Depending on the feature set of the gateway, multiple web servers can be white-listed (say for iframes or links within the login page). In addition to white-listing the URLs of web hosts, some gateways can white-list TCP ports. The MAC address of attached clients can also be used to bypass the login process for specified devices.
This technique has occasionally been referred to as UAM (Universal Access Method) in implementations and standards forums.
Captive portals are mainly used in wireless open networks, where the users are shown a welcome message informing them of the conditions of access (allowed ports, liability, etc.). Administrators tend to do this so that their own users take responsibility for their actions and to avoid any major problems. It is discussed whether this delegation of responsibility is legally valid.
Often captive portals are used for marketing and commercial communication purposes. In order to do this, access to Internet is done via WiFi as an incentive to exchange personal data that the user provides by filling out a registration form. The online form either automatically opens in a device's browser, or appears when the user opens their browser and tries to visit any webpage. In other words, the user is "captive" - unable to browse freely until they accept the terms and conditions, or see the displayed advertisements that are shown in the registry form or welcome page. This allows the provider of this service to display or send advertisements to users who connect to the WiFi access point. This type of service is also sometimes known as social WiFi, as they may ask for a social network account to login (such as Facebook).
The user can find many types of content in the captive portal, and it's frequent to allow access to the Internet in exchange for viewing content or performing a certain action (generally providing personal data to enable commercial contact); thus, the marketing use of the captive portal is a tool for lead generation (business contacts or potential clients).
There is more than one way to implement a captive portal.
Client traffic can also be redirected using ICMP redirect on the layer 3 level.
Redirect by DNS
When a client requests a website, DNS is queried by the browser. In a captive portal, the firewall will make sure that only the DNS server(s) provided by the network's DHCP can be used by unauthenticated clients (or, alternatively, it will forward all DNS requests by unauthenticated clients to that DNS server). This DNS server will return the IP address of the captive portal page as a result of all DNS lookups.
In order to perform redirection by DNS the captive portal uses DNS hijacking to perform an action similar to a man-in-the-middle attack. To limit the impact of DNS poisoning typically a TTL of 0 is used.
Circumvention of captive portals
Captive portals have been known to have incomplete firewall rule sets. In some deployments the rule set will route DNS requests from clients to the Internet, or the provided DNS server will fulfill arbitrary DNS requests from the client. This allows a client to bypass the captive portal and access the open Internet by tunneling arbitrary traffic within DNS packets.
Some captive portals may be configured to allow appropriately equipped user agents to detect the captive portal and automatically authenticate. User agents and supplemental applications such as Apple's Captive Portal Assistant can sometimes transparently bypass the display of captive portal content against the wishes of the service operator as long as they have access to correct credentials, or they may attempt to authenticate with incorrect or obsolete credentials, resulting in unintentional consequences such as accidental account locking.
A captive portal that uses MAC addresses to track connected devices can sometimes be circumvented by connecting a router that allows setting of the router MAC address. Many router firmwares call this MAC cloning. Once a computer or tablet has been authenticated to the captive portal using a valid username and valid password, the MAC address of that computer or tablet can be entered into the router which will often continue to be connected through the captive portal as it shows to have the same MAC address as the computer or tablet that was previously connected.
Some of these implementations merely require users to pass an SSL encrypted login page, after which their IP and MAC address are allowed to pass through the gateway. This has been shown to be exploitable with a simple packet sniffer. Once the IP and MAC addresses of other connecting computers are found to be authenticated, any machine can spoof the MAC address and IP of the authenticated target, and be allowed a route through the gateway. For this reason some captive portal solutions created extended authentication mechanisms to limit the risk for usurpation.
Captive portals require the use of a browser; this is usually the first application that users start, but users who first use an email client or other may find the connection not working without explanation, and will then need to open a browser to validate. It is however sometimes possible to use email and other facilities that do not rely on DNS (e.g. if the application specifies the connection IP rather than the web address). A similar problem can occur if the client uses AJAX or joins the network with pages already loaded into its browser, causing undefined behavior when such a page tries HTTP requests to its origin server.
Platforms that have Wi-Fi and a TCP/IP stack but do not have a web browser that supports HTTPS cannot use many captive portals. Such platforms include the Nintendo DS running a game that uses Nintendo Wi-Fi Connection. Non-browser authentication is possible using WISPr, an XML-based authentication protocol for this purpose, or MAC-based authentication or authentications based on other protocols.
It is also possible for a platform vendor to enter into a service contract with the operator of a large number of captive portal hotspots to allow free or discounted access to the platform vendor's servers via the hotspot's walled garden. One such example is the 2005 deal between Nintendo and Wayport to provide free WiFi access to Nintendo DS users at certain McDonald's restaurants. Also, VoIP SIP ports could be allowed to bypass the gateway to allow phones to work.
- "Nintendo And Wayport Join Forces To Bring Free U.S. Wi-Fi Access To Nintendo DS Users". gamesindustry.biz. Retrieved 24 November 2015.