Tasks to use the SAE to manage a wireless access point that participates in a roaming agreement are:
You configure RADIUS authentication for users who connect from a wireless location, and set up RADIUS authentication to support a roaming environment between wireless Internet service providers. You can use the Flexible RADIUS Authentication plug-in that is provided with the SRC software, or you can create a custom RADIUS authentication plug-in.
Configuring a Custom RADIUS Authentication Plug-In
If you create a custom plug-in, be sure that it supports the same RADIUS attributes as those configured for the flexible RADIUS authentication plug-in. See Configuring the Flexible RADIUS Authentication Plug-In .
For information about creating a custom plug-in, see SAE CORBA Plug-In Service Provider Interface (SPI) on the Juniper Networks Web site at: http://www.juniper.net/techpubs/software/management/src/api-index.html
Configuring the Flexible RADIUS Authentication Plug-In
The default flexible RADIUS authentication plug-in, flexRadiusAuth, provides support for RADIUS vendor-specific attributes for WISPr, which are listed in the following procedure. These attributes use the IANA private enterprise number 14122 assigned to the Wi-FI Alliance. For more information about these attributes, see http://www.wi-fialliance.org/opensection/wispr.asp
You should be familiar with the general procedure for configuring the flexible RADIUS authentication plug-in before configuring it to include the WISPr attributes. For information about configuring the flexible RADIUS authentication plug-in, see Configuring Tracking Plug-Ins.
When you configure the plug-in, you can use the following standard attribute values to set values in authentication response packets:
Examples in the following procedure show how you can use these attribute values.
To configure the plug-in to support a roaming environment:
This attribute can be an interface description (ifAlias) or other value that identifies the JUNOSe interface to which the wireless access point connects.
For example:
The default configuration sets a session property named startURL.
For example:
For example:
For example:
If the operator of the wireless location does not support daily billing, do not configure this attribute, and remove it if present.
Table 5: Packet Types for RADIUS Attributes
Configure a service that lets subscribers connect to an ISP through a captive portal, a single Web page to which subscribers connect. The policies associated with the service should specify a JUNOS policing or JUNOSe rate-limiting policy to set the maximum bandwidth at which:
When you configure the policies, define the bandwidth values as parameters so that the policies can be applied across a number of subscribers.
To configure a service to access the ISP:
To configure policies , see:
For example, you can create a policy configuration that includes:
Substitutions for these parameters can then be referenced in the RADIUS attributes:
- vendor-specific.WISPr.Bandwidth-Max-Up=setSubstitution(“
max_up_rate=%s” % ATTR)
- vendor-specific.WISPr.Bandwidth-Max-Down=setSubstitution(“
max_down_rate=%s” % ATTR)
When subscribers connect to and log in to a wireless access point, they are directed to a single Web page that is referred to as a captive portal page. This page is part of a service selection portal. A captive portal page receives and manages redirected Web requests. The SRC Application Library provides an unsupported, demonstration application for a residential service selection portal.
When creating a captive portal page for a wireless roaming environment, configure the page to:
You can retrieve the URL of the start page from the service session property startURL. Note that startURL is the default name used for the flexible RADIUS authentication plug-in; you can assign a different name to this property.
You can use the Subscriber.readSubscription() method in the Common Object Request Broker Architecture (CORBA) remote application programming interface (API) to retrieve the redirect URL.
Note that when you develop the portal, you can use the following methods in the SAE CORBA remote API to retrieve session data after the access service starts:
For more information about these methods, see the SAE CORBA remote API documentation on the Juniper Networks Web site at
http://www.juniper.net/techpubs/software/management/src/api-index.html.
You can configure the following options to ensure that the timeout values are consistent with the requirements for your environment:
To configure the timeout settings:
or
Configure the idle timeout in the SRC service definition. For example:
Although an interval up to 5 minutes is typically recommended, for the SRC software, we recommend a minimum of 15 minutes.
http://www.juniper.net/techpubs/software/erx/junose82/bookpdfs/swconfig-broadband.pdf