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  G  H  I  L  M  N  P  Q  R  S  T  U  V

 

A

access lines    1
description    12
accesses    
configuring subscriptions    
SRC CLI
accounting    
basic RADIUS accounting plug-in
custom RADIUS accounting plug-ins
flat file accounting plug-ins
flexible RADIUS accounting plug-ins
anonymous subscriber
attributes    
RADIUS accounting
authenticated subscriber
authentication plug-ins    
configuring
types
authorization plug-ins    
configuring
types
 

B

basic RADIUS accounting plug-in    1
configuring    
SRC CLI
basic RADIUS authentication plug-in    1
configuring    
SRC CLI
 

C

captive portal    
preventing access to resources
classification scripts    
conditions    1
glob matching
joining
regular expression matching
configuring    
C-Web interface
descriptions
DHCP classification, C Series Controller    
conditions
configuring, SRC CLI
description
targets
interface classification, C Series Controller    
conditions
configuring, SRC CLI
description
empty policy    12
examples
how it works
targets
structure    
C-Web interface
subscriber classification, C Series Controller    
condition
configuring, SRC CLI
description
DHCP options
enterprise subscriber example
how it works
static IP subscriber example
subscriber group example
targets
target, C Series Controller    
definition
expressions
types
component interactions    
DHCP    
initial login
persistent login
subscriber account login
subscriber logout
enterprise subscribers    
login
remote session activation
PPP    
login
logout
static IP subscribers
subscription activation
subscription deactivation
conventions    
notice icons
text
COPS (Common Open Policy Service)    
DHCP interactions    
initial login
logout
persistent login
subscriber account login
interface startup interactions
PPP interactions    
login
logout
static IP subscriber interactions
subscription activation interactions
subscription deactivation interactions
custom RADIUS accounting plug-ins    1
configuring    
SRC CLI
custom RADIUS authentication plug-ins    1
configuring    
SRC CLI
customer support    1
contacting JTAC
 

D

default retailer authentication plug-ins    
configuring    
SRC CLI
default retailer DHCP authentication plug-ins    
configuring    
SRC CLI
denial-of-service attacks
DHCP (Dynamic Host Configuration Protocol)    
address assignment
classification scripts.     See classification scripts    
options
profiles    
SRC CLI
subscribers    
login process
logout process
documentation    
comments on
 

E

enterprise    
description
enterprise subscribers    1
adding    
SRC CLI
enterprise subscribers, login process
event publishers    
configuring    
SRC CLI
default retailer authentication, configuring    
SRC CLI
default retailer DHCP authentication, configuring    
SRC CLI
description
retailer-specific
service-specific
virtual router-specific
external plug-ins    
configuring    
SRC CLI
 

F

file upload settings for log rotation    
configuring    
SRC CLI
flat file accounting plug-ins    1
configuring    
SRC CLI
configuring headers    
SRC CLI
flexible RADIUS accounting plug-ins    1
attributes, defining    
C-Web interface
configuring
RADIUS packets, defining
flexible RADIUS authentication plug-ins    1
attributes, defining    
C-Web interface
examples
configuring    
SRC CLI
RADIUS packets, defining    
SRC CLI
setting responses    
C-Web interface
FTP server for log rotation    
configuring    
SRC CLI    12
 

G

general properties    
configuring    
SRC CLI
 

H

HTTP proxy    12
HTTPS traffic
 

I

interface classification scripts.     See classification scripts    
interim accounting, configuring on SAE
internal plug-ins    
configuring    
SRC CLI
 

L

LDAP authentication plug-in    1
configuring    
SRC CLI
limiting subscribers plug-in    1
configuring    
SRC CLI
log rotation    
overview    
SRC CLI
logging    
redirect server
login events, description
login process    
enterprise
residential    12,  See also logout process, residential    
DHCP
PPP
summary
login registration    
configuring    
SRC CLI
logout process, residential    
DHCP
 

M

managers    
configuring    
SRC CLI
control over all retailers
management privileges
subscribers and subscriptions
manuals    
comments on
 

N

NAT (Network Address Translation)    
VPNs
notice icons
 

P

plug-ins    
activating service sessions
authentication    
configuring
authorization    
configuring
basic RADIUS accounting    1
configuring, SRC CLI
basic RADIUS authentication    1
configuring, SRC CLI
creating subscriber sessions
custom RADIUS accounting    1
configuring, SRC CLI
custom RADIUS authentication    1
configuring, SRC CLI
defining RADIUS packets    
SRC CLI
DHCP address assignment
event publishers.     See event publishers    
external    
configuring, SRC CLI
flat file accounting    1
configuring, SRC CLI
flexible RADIUS accounting    1
configuring
flexible RADIUS authentication    1
configuring, SRC CLI
internal    1
authorization
configuring RADIUS peers, SRC CLI
configuring, SRC CLI
customizing RADIUS packets
how they work
pool
RADIUS attributes, C-Web interface
tracking
LDAP authentication    1
configuring, SRC CLI
limiting subscribers    1
configuring, SRC CLI
state synchronization    
configuring, SRC CLI
tracking    
configuring, C-Web interface
service sessions
subscriber sessions
policy groups    
empty    12
policy management    
external policy system    12
PPP subscribers    
login process
Web login
prevention, use of unauthorized resources
protocols    
routing
proxy HTTP    12
proxy request management
public addresses, VPNs
 

Q

QoS tracking plug-in
 

R

RADIUS accounting    
attributes
description
RADIUS attributes    
defining in RADIUS plug-ins    
C-Web interface
examples, defining in RADIUS plug-ins    
C-Web interface
RADIUS client library, custom RADIUS plug-ins
RADIUS packets, customizing in plug-ins
RADIUS peers    
configuring in plug-ins    
SRC CLI
RADIUS plug-ins    1,  See also plug-ins    
authentication
UDP port
redirect server    
assessing load    
C-Web interface
configuration statements    
SRC CLI
configuring    
SRC CLI
configuring DNS server for    
SRC CLI
configuring HTTP proxy support    
SRC CLI
configuring redundant    
SRC CLI
directory connection    
SRC CLI
failover
file extensions    
SRC CLI
logging
number of requests    
SRC CLI
protection against denial-of-service attacks
redundancy    123
static route to router
traffic definition    
SRC CLI
verifying    
SRC CLI
redundancy    
redirect server
residential subscribers    1
adding    
SRC CLI
login process.     See login process    
retailers    
subscribers    1
adding, SRC CLI
router subscribers    1
adding    
SRC CLI
routing instances    
VPNs
routing scheme
 

S

SAE (service activation engine)    
classification scripts.     See classification scripts    
login events
login process.     See login process    
SAE (service activation engine), configuring    
interim accounting    
SRC CLI
login registration    
SRC CLI
multiple logins from same IP address    
SRC CLI
reduce reported session time    
SRC CLI
session reactivation timers    
SRC CLI
time for MAC address in cache    
SRC CLI
unauthenticated user DN    
SRC CLI
service activation engine.     See SAE    
service sessions    
activate-on-login    12
activating and tracking
activating with Web application
enterprise, remote activation
sites    123
subscriber    1
adding, SRC CLI
state synchronization plug-in interface    
configuring    
SRC CLI
static IP subscribers, login process
static routing
subscriber classification scripts.     See classification scripts    
subscriber folders    1
adding    
SRC CLI
subscriber sessions    
activating with Web application
creating and tracking
enterprise, creating and activating
subscribers    
3gpp attributes (Gx router driver)    
configuring, SRC CLI
adding    
SRC CLI
enterprise    1
adding, SRC CLI
inheriting properties
inheriting subscriptions
residential    1
adding, SRC CLI
retailer    1
adding, SRC CLI
router    1
adding, SRC CLI
sessions
sites    1
adding, SRC CLI
types
subscriptions    1
access, configuring    
SRC CLI
an orderly deactivation, activation order, specifying    
SRC CLI
configuring    
SRC CLI
multiple per subscriber
support, technical     See technical support    
 

T

targets.     See classification scripts    
technical support    
contacting JTAC
text conventions defined
tracking plug-ins    1
configuring    
C-Web interface
 

U

UDP ports    
RADIUS plug-ins
User Datagram Protocol.     See UDP    
 

V

validating    
VPNs
virtual private networks.     See VPNs    
VPNs (virtual private networks)    
adding    
SRC CLI
configuration requirements
configuration statements
extranet clients, modifying    
SRC CLI
invalid subscriptions
modifying
routing schemes
using NAT
validating

Traffic Redirection Overview

The redirect server is part of a captive portal system that redirects subscribers’ Web requests to a captive portal page. 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 or HTTPS requests to unauthorized Web resources.

Proxy Request Management

The redirect server examines requested paths and detects proxy HTTP requests by the proxy prefix “<scheme>:” followed by the address of the requested host. If the requested URL is served by the captive portal server:

  1. The redirect server opens a TCP connection to the captive portal and forwards the request for the URL. The redirect server adds to the request an X-Forwarded-For header that specifies the IP address of the client.
  2. The captive portal server inspects the incoming request for the X-Forwarded-For header for the IP address. The captive portal server uses this address instead of the source IP address to determine the originator of the request.
  3. If the captive portal authorizes the client and activates a service that enables a direct connection between the client and the proxy, the redirect server then sends the returned data to the subscriber’s Web browser.

    or

    If the requested URL is not served by the captive portal server, the redirect server opens a TCP port and sends the type of response configured to a subscriber’s browser in response to a captured request:

    • HTTP 200 OK response with an HTML document that includes the <HTTP-Equiv="Refresh"> header (default)
    • HTTP 302 Found response to a subscriber’s browser in response to a captured request

      The subscriber browser follows the redirect request, and the proxied request is served by the redirect server again, which opens a connection to the captive portal.

Support for HTTP proxy requests requires the following:

  • A local HTTP proxy server that can handle the traffic from all clients configured with a proxy.
  • A location for the local HTTP proxy server that is one IP hop from each access router.
  • A proxy service that the captive portal server can activate to send proxy requests to the local HTTP proxy server when the portal server authorizes proxy clients.
  • A proxy service activation policy that includes a next-hop policy that points to the local HTTP proxy server, and a classifier that matches the client’s IP address and the address of the proxy server configured on the client.

Services that the client accesses through the proxy server, such as HTTP and FTP, cannot be activated based on destination address.

You must redirect all ports to the redirect server because you cannot know which ports are configured on the client for the proxy. Consequently, the redirect server receives non-HTTP requests as well as HTTP requests. The non-HTTP requests generate error log entries. To reduce overhead, HTTP error messages are logged as system log debug messages.

HTTP Proxy and DNS

Make sure that your network includes a domain name service (DNS) server to resolve unknown names to a fixed IP address. A DNS server is required because proxy servers can be configured with DNS names in private domains that are not valid in the public environment. You can use the DNS server included with the redirect server, or another DNS server on your network.

The DNS server can be configured on a client with DHCP. Alternatively, the service provider can set up a transparent DNS proxy by configuring a next-hop policy on the JunosE router for UDP and TCP port 53 traffic. The policy redirects traffic on these two ports to the redirect server’s DNS server.

Because proxy addresses must be resolved even if general access to the Internet is enabled, the DNS server must continue to resolve all client requests for proxy clients. Nonproxy clients can use their regular DNS server after the initial service has been activated.

The redirect server’s DNS server either forwards the request to a set of configured DNS servers or resolves the request by using the root domain name server. If a request for an IPv4 or IPv6 address cannot be resolved and the request results in an NXDOMAIN error, the DNS server returns a configurable IP address. The redirect server returns an error message to the clients for any other type of request that cannot be resolved.

HTTPS Traffic Redirection Support

The SRC software supports to redirect HTTPS traffic by using the redirect server. The redirect server redirects HTTPS traffic to a configured destination web server. The redirect server requires a Secure Sockets Layer (SSL) certificate.

Note: Whenever you open up an HTTPS page, you get a security warning in the browser for the mismatch between common name of the certificate with the domain name of the URL until you add an exception for the certificate in the browser.

Protection Against Denial-of-Service Attacks

The redirect server incorporates a number of properties to protect against denial-of-service attacks. The following list shows the default values set for these properties:

  • The redirect server can serve no more than 12,000 requests per minute, with a burst of 18,000 requests.
  • The redirect server can serve no more than 25 requests per client per minute, with a burst of 50 requests.
  • Incoming requests can be no larger than 4 KB.
  • Incoming requests have a time limit of 2 seconds.

You can change the values for any of these properties.

Related Documentation

Modified: 2016-05-27