Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Configuring Subscriber Access for a Wireless Location


Tasks to use the SAE to manage a wireless access point that participates in a roaming agreement are:

Configuring RADIUS Authentication

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 website at:

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

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 (SRC CLI).

When you configure the plug-in, you can use the following standard attribute values to set values in authentication response packets:

  • setAcctInterimTime

  • setSubstitution

  • setTerminateTime

Examples in the following procedure show how you can use these attribute values.

To configure the plug-in to support a roaming environment:

  1. Configure attributes.

    • Required attributes:

      • An identifier for the wireless location:

        This attribute can be an interface description (ifAlias) or other value that identifies the JunosE interface to which the wireless access point connects.

      • The URL of the start page returned by the RADIUS server of the ISP:

        For example:

        The default configuration sets a session property named startURL.

      • The URL of a page that a subscriber can use to log out of the network:

    • Bandwidth attributes (recommended):

      • The maximum transmission rate in bits per second:

        For example:

      • The maximum receive rate in bits per second:

        For example:

    • Optional attributes:

      • The name of the wireless location:

      • The date and time that the subscriber session is to end:

        For example:

      • The end of the subscriber session at the end of the billing day:

        If the operator of the wireless location does not support daily billing, do not configure this attribute, and remove it if present.

      • A service type for billing:

  2. For each attribute that you configure, configure the packet type to which the attribute applies. Table 1 shows the packet types associated with each attribute.

    Table 1: Packet Types for RADIUS Attributes

    RADIUS Attribute

    Associated RADIUS Packet Definition




















Creating Subscriber Access to an ISP

Configure a service that lets subscribers connect to an ISP through a captive portal, a single webpage to which subscribers connect. The policies associated with the service should specify a Junos OS policing or JunosE rate-limiting policy to set the maximum bandwidth at which:

  • A subscriber can send traffic.

  • A subscriber can receive traffic.

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:

  1. Create the SRC service to use RADIUS authentication.

    See Adding a Normal Service (SRC CLI).

  2. Create a policy group the sets the maximum bandwidth at which a subscriber can send traffic, and the maximum bandwidth at which a subscriber can receive traffic. Use parameters to set these values.

    To configure policies, see:

For example, you can create a policy configuration that includes:

  • A local parameter named max_up_rate that sets the maximum rate at which the subscriber can send data

  • A local parameter named max_down_rate that sets the maximum rate at which the subscriber can receive data

  • A policy group Receive(Downstream) that references max_down_rate

  • A policy group Send(Upstream) that references max_up_rate

Substitutions for these parameters can then be referenced in the RADIUS attributes:

Creating Web Access

When subscribers connect to and log in to a wireless access point, they are directed to a single webpage 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:

  • Start an access service that is configured to be authenticated by the RADIUS server of the ISP.

  • After the access service starts, redirect the subscriber to the page specified by the Redirect-URL RADIUS attribute. This page is the start page for the subscriber's home ISP.

    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:

  • Subscriber.readSubscriber()

  • Subscriber.readSubscription()

For more information about these methods, see the SAE CORBA remote API documentation on the Juniper Networks website at

Setting Idle Timeout Options for the SAE

You can configure the following options to ensure that the timeout values are consistent with the requirements for your environment:

  • Idle timeout—Defines how long a session is idle before the connection is closed.

  • Adjust session time—Adjusts the session time reported in an accounting messaged by subtracting idle time from the time if the session times out.

To configure the timeout settings:

  1. Configure the service activation authentication through a RADIUS server to return an idle timeout. This configuration requires that the RADIUS server returns the idle timeout vendor-specific attribute (VSA).


    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.

  2. Configure the adjust-session-time statement for the SAE to ensure that session time is accurately reported for accounting purposes. For example: