[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
Sequence for Redirecting Traffic
The following list describes the sequence of events
that occurs when a subscriber tries to access a restricted service:
- A subscriber opens a Web browser and attempts to access
a restricted server; for example, http://a.com.
- A next-hop policy on the JUNOSe router sends this request
to the redirect server instead of to the requested server.
The policy does not affect the destination address
(resolved from a.com) in the IP packets.
- For environments that have the SRC software installed
on a Solaris platform, the IP Filter process running on the same host
as the redirect server filters traffic and redirects traffic arriving
on port 80 on the host’s incoming interface.
- The captured request is redirected to an address and a
port where the redirect server listens.
- The redirect server opens a TCP port (8800 by default)
and sends the type of response configured—an HTTP 200 (OK) or
a small HTML document that encodes a refresh in the meta header of
the of the file—to the subscriber’s browser for the requests.
- The subscriber browser follows the redirect request and
opens the captive portal page on the portal server.
[Contents]
[Prev]
[Next]
[Index]
[Report an Error]
