This DNS server will in turn return the IP address of the captive portal as a response to all DNS lookups made by unauthenticated clients. The firewall could also redirect any DNS queries from unauthenticated clients to the local DNS server. In DNS based redirection the firewall ensures that only the DNS server(s) provided by DHCP may be used by authenticated clients. The client HTTP request is forwarded to a server in the local network which issues a server-side redirect with a HTTP 302 Found status code, which will redirect the client to the captive portal. However, when the browser makes a HTTP request to the resolved IP address, the request is intercepted by a firewall acting as a transparent proxy. In this case, DNS queries from unauthenticated clients are resolved as normal. ![]() There are several ways to implement a captive portal: ![]() ![]() They are typically used for authentication on Wi-Fi hotspots, but can be used to control wired network access as well. What you describe is called a captive portal.
0 Comments
Leave a Reply. |