A
CCESS
G
ATEWAY
System Administration
87
The NSE will process HTTP requests for that “magic” IP address (configurable on the AAA page), and will
reply with an HTTP redirection (which may include a number of signed redirection parameters) to a
configured URL. By following the HTTP redirection, the subscriber will reach the target URL, and he/she
will then be served a page containing whatever information is relevant (account and/or other specific
information).
The figure above illustrates destination HTTP redirection, assuming a DNS query string for
a magic IP address of 1.1.1.1, and a portal page URL of portal1.myhotel.com. Given this
configuration, the following would apply:
•
is intercepted by the NSE, which responds with the magic IP
address. Then, the subscriber’s browser sends an HTTP request to the magic IP and sets the Host
header to
•
The NSE will process the HTTP request and will analyze the Host header to find the redirection URL
that corresponds to
which is portal1.myhotel.com in this example. The NSE will
then craft an HTTP redirection response that contains the portal page URL, followed by a query
string. The string will include various redirection parameters, time-stamped and signed, if signing is
enabled for that entry (which it is not in this example).
•
The subscriber will follow the redirection string and will land on the portal page URL. The portal
will verify and analyze the query string and then will return the relevant information (likely about the
subscriber’s account status, depending on what the portal is configured to handle).
•
After successful redirection occurs the list of signed parameters and signature methods are passed to
the portal page.
HTTP/1.0 302 RD
http://portal1.myhotel.com/details?OS=<Original Server>&UI=<NSE’s
ID>&MA=<subscriber’s MAC>&RN=<Room
name>&PORT=<VLAN>&SIP=<subscriber’s IP>&TS=<timestamp>&NONCE=<16
chars>&SIGN=<signature>& SIGNED=<list of signed parameters>&
METHOD=<signature method>
Summary of Contents for AG 2300
Page 1: ......