1)
If the URL configured by the
portal web-server is an IP address, the following issues are not involved;
2)
If the URL configured in the
portal web-server is a domain name, the following issues are involved: Before
version D029: If the URL is a domain name, the AP has to find a DNS server to
resolve the URL in the first step, and then send a probe message after the
second step. If there was a problem in the first step and the AP could not
resolve the URL, no probe was sent and the AP pushed the page directly, so the
escape would not take effect (no DNS was assigned); if there was a problem in
the second step and no response to the probe message (the server down), the
escape would take place (DNS was assigned). The problem with the old version
was that if the server did not have DNS, the AP would not be able to sense that
the server was down and the terminal would not be able to escape or
authenticate. So in the new version, if the AP is not equipped with DNS, even
if the server does not down, it will still trigger an escape.
