Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Navigation  Back up to About Overview 
ContentIndex
  
[+] Expand All
[-] Collapse All

 A  B  C  D  E  F  I  J  L  M  N  P  R  S  T  U  V  W

 

A

action classes in the sample residential portal
application protocols, managing
architecture    
enterprise service portal
 

B

bandwidth on demand.     See BoD    
BoD (bandwidth on demand)    
services
subscriptions
 

C

callback interface
captive portal    
implementing
preventing access to resources
configuration level in Enterprise Manager Portal
conventions    
notice icons
text
CORBA (Common Object Request Broker Architecture)    
plug-in interface    
enterprise service portal
remote API
customer support    1
contacting JTAC
 

D

DCU (destination class usage)
demonstration applications
deployment scenarios    
enterprise service portal
destination class usage
devices running Junos OS    
forwarding preferences
managing traffic
policies    
basic BoD
BOD
BoD and VPNs
firewall
NAT
provisioning services    
prerequisites
routing preferences
services    1
basic BoD
BoD
BoD and VPNs
firewall
NAT    12
directory server    
deployment with remote SAE
DirX directory server    
deployment with remote SAE
documentation    
comments on
 

E

enterprise    
service parameters
Enterprise Manager Portal    
application protocols, managing
BoD subscriptions
configuration level
deployment settings
firewall exception rules    
stateful firewalls    12
stateless firewalls    12
firewall subscriptions
fixed addresses for outgoing traffic
help
NAT    
IP address    123
rules for traffic
NAT Address Management Portal
NAT rules    12
overview    12
policies
public IP addresses, configuring    
incoming traffic
outgoing traffic
schedules    12
services
Enterprise Service Portal audit plug-in
enterprise service portals    1,  See also Enterprise Manager Portal    
accessing
architecture
configuring directory connections
data, displaying
deploying
improving performance
installing
managers    12
operators, managing    12
overview
performance
planning
prerequisites    12
server description
value substitution
value substitution for policy parameters
enterprise tag library    12
equipment registration    1,  See also sample residential portal    
description
event notification    
DHCP server
IP address manager
PCMM network
RADIUS server
events, IT manager audit
example-simple
 

F

files    
WEB-INF/jboss-web.xml
WEB-INF/portalBehavior.properties
WEB-INF/struts-config.xml    123
WEB-INF/tiles-defs.xml    123
WEB-INF/web.xml
firewall ports for sample SRC-applications
firewall services    
configuring    12
description
managing in Enterprise Manager Portal
policies for
router support
folders for installed software
forwarding preferences    12
 

I

installing    
Web applications
installing software    
enterprise service portals
interfaces    
callback
IP address managers, event notification
IP addresses    
acknowledging release
assigning in NAT Address Management Portal    12
NAT services    123
IP Filter
IP-in-IP tunneling
ISP service in sample residential portal
IT manager    
audit plug-in    
events
operators, managing    1234
 

J

Jakarta Struts Web application framework
Java development environment, Tomcat    12
Javadoc documentation for sample residential portal
JSP tag library.     See enterprise tag library    
JunosE routers    
policies    
basic BoD
BOD
services    
basic BoD
BoD
 

L

listeners, defining
 

M

manuals    
comments on
Monitoring Agent    
acting as pseudo RADIUS server
configuring    
properties
pseudo RADIUS agent    12
installing
intercepting DHCP messages
intercepting RADIUS accounting messages
monitoring    12
overview
stopping
multihop environment
 

N

NAT (Network Address Translation)    1,  See also NAT Address Management Portal    
rules
services for Enterprise Manager Portal
services, IP address    123
types
NAT Address Management Portal    
acknowledging IP address release
assigning IP addresses
deployment settings
Enterprise Manager Portal
overview
Network Address Translation.     See NAT    
NIC (network information collector)    
enterprise service portals. with
notice icons
 

P

packages, Solaris.     See Solaris packages    
parameters    
acquisition path and substitutions
sample enterprise service portal
patches for Solaris
performance    
enterprise service portals
plug-ins    1,  See also Enterprise Service Portal audit plug-in    
listeners
policies    
basic BoD
BoD
BoD and VPNs
NAT
parameters
ports for sample SRC-applications
precedence    
subscriptions
prevention, use of unauthorized resources
privileges    
IT managers
properties for sample residential portal
proxy request management
public wireless LAN applications
 

R

removing    
Solaris packages
Web applications
residential portal    1
developing
overview    12
prerequisites for development
RADIUS authentication for login
security
routing instances
rules, NAT
 

S

SAE (service activation engine)    
identifying
sample applications
sample enterprise service portal    
configuring connection to directory
customizing    1
privileges
data, displaying
managing services
monitoring    
service sessions
subscriptions
networks for departments    123
overview
service parameters    12
sample residential portal    
action classes
behaviors
customizing
developing portal based on the sample    12
development tools
equipment registration    12
installing
login
model components
overview    12
personal digital assistant (PDA)
prerequisites
schedules
service activation
services    
management
schedules
subscriptions
usage    
information
view components
Web application framework
sending traffic to VPNs
service activation
service parameters, enterprise
service schedules    
Enterprise Manager Portal, in
service schedules, sample residential portal
services    1,  See also firewall services    
basic BoD
BoD    123
devices running Junos OS    1
BoD and VPNs
NAT    12
sample enterprise service portal, managing
single-hop environment
Solaris packages    
installing
removing
Solaris patches
source class usage (SCU)
SRC single-hop requirement
subscribers    
billing
subscriptions    
enterprise hierarchy
priority
sample enterprise service portal, creating
substitutions    
parameter acquisition path
use
support, technical     See technical support    
 

T

technical support    
contacting JTAC
text conventions defined
Tomcat, as Java development environment    12
 

U

uninstalling.     See removing    
 

V

value substitution
virtual portal address
virtual private networks.     See VPNs    
VPNs (virtual private networks)    
directory
identifiers
modifying    1
VPN to which router sends traffic
sending traffic
stopping router from sending traffic
 

W

WAR files
Web application server    
application deployment
installing Web applications inside
Web applications    
installing
removing
WEB-INF/jboss-web.xml
WEB-INF/portalBehavior.properties
WEB-INF/struts-config.xml    123
WEB-INF/tiles-defs.xml    123
WEB-INF/web.xml

Redirecting Traffic to a Captive Portal Webpage

A captive portal webpage is a page that receives redirected HTTP requests. You can use a captive portal page as the initial page a subscriber sees after logging in to a subscriber session and as a page used to receive and manage HTTP requests to unauthorized Web resources.

The type of information available from a captive portal page depends on the portal design. The page can provide informational messages or can let subscribers perform actions such as activating a service to which they have a subscription. For example, if a subscriber requests access to a service that the subscriber has not activated, the portal could display a captive portal page that tells the subscriber that the service is not available, or the page could prompt the subscriber to activate the requested service.

Implementing a captive portal requires the following:

  • An instance of the redirect server installed on a host in the same network as a JunosE router. The redirect server redirects HTTP requests received from IP Filter to a captive portal page.
  • When the SRC software is installed on a Solaris platform, the IP Filter tool installed and configured on the same host as the redirect server. This tool redirects incoming HTTP requests to the redirect server.
  • Default policies installed on the JunosE router. The default policies on the JunosE router must include a forwarding or rate-limiting policy that permits access to the portal server and a next-hop rule to intercept the unauthorized access request packets. The target of the next-hop rule is the host on which the redirect server resides.
  • A portal server for serving the captive portal pages.

For a sample captive portal, see the sample residential portal.

For information about configuring the redirect server, see Configuring the Redirect Server (SRC CLI).

Sequence for Redirecting Traffic

The following list describes the sequence of events that occurs when a subscriber tries to access a restricted service:

  1. A subscriber opens a Web browser and attempts to access a restricted server; for example, http://a.com.
  2. 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.

  3. 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.
  4. The captured request is redirected to an address and a port where the redirect server listens.
  5. 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.
  6. The subscriber browser follows the redirect request and opens the captive portal page on the portal server.

Configuring the SRC Software in a Multihop Environment

The captive portal system implemented by the HTTP redirect server requires a single-hop connection; that is, the router accessed by the subscriber cannot be more than one hop away from the redirect server. However, some networking environments will require a multihop connection—through more than one router—to the redirect server.

You can use any of several methods to get around the intermediate, next-hop routers, such as IP-in-IP tunneling, deployment of a NAT device, and dynamic DNS. Contact Juniper Networks Professional Services for assistance with these methods.

Modified: 2016-05-27