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 
  
[+] Expand All
[-] Collapse All

Configuring the radius.ini File for WiMAX

The [Configuration] section of the radius.ini file contains parameters that control the basic behavior of Steel-Belted Radius Carrier. For WiMAX, you must edit the parameter listed in Table 65.

Table 65: radius.ini [Configuration] Section WiMAX-specific Parameter

Parameter

Function

SendOnlyOneClassAttribute

When a user’s identity information is encrypted during authentication, Steel-Belted Radius Carrier uses a special class attribute to pass the user’s encrypted identity to an accounting server. Because this typically requires more than one class attribute to be included in the accept response, and because some access points do not support echoing more than one class attribute, you can use the SendOnlyOneClassAttribute parameter to specify how you want Steel-Belted Radius Carrier to forward encrypted user identity information.

For WiMAX, set to 1 so Steel-Belted Radius Carrier creates a class attribute containing a class attribute flag, a server identifier, and a transaction identifier. The user identification data that normally is stored in the class attributes is stored in the current sessions table.

AckOnCookieFailure

SBR Carrier does not acknowledge accounting requests for WiMAX when the session does not exist in the current sessions table (CST). To work around this problem, set the AckOnCookieFailure parameter to yes, and SBR Carrier sends an acknowledgement back for every accounting request it receives.

EnableWiMAXUniqueSessionIdFromNAI

This parameter was introduced in Release 7.2.3 of SBR Carrier. It provides improvements to WiMAX performance and scalability. The improvements include different logic for assigning primary keys to WiMAX tables and for generating the Class attribute in the Access-Accept response.

  • If set to 1, the EnableWiMAXUniqueSessionIdFromNAI parameter is enabled.
  • If set to 0, the EnableWiMAXUniqueSessionIdFromNAI parameter is disabled.

Note: When the EnableWiMAXUniqueSessionIdFromNAI parameter is enabled, new session records in the database and the Class attribute in Access-Accept messages are incompatible with the WiMAX logic in previous releases of SBR Carrier. For compatibility with SBR Carrier 7.2.1 and earlier, set EnableWiMAXUniqueSessionIdFromNAI = 0.

By default this parameter is enabled.

For details on migrating from existing SBRC WiMAX installations and new installations using WiMAX, see the section on Migration and New Installations of SBR Carrier with WiMAX in the Migrating from Previous SBR Releases section of the SBR Carrier Installation Guide.

Configuring Support for Authorize-Only Requests

Authorize-Only requests are supported for WiMAX sessions. You can use Authorize-Only requests to support control of prepaid services. For example, where subscriber usage is metered by time or traffic volume. When subscribers exhaust their prepaid service quota, they can be redirected in mid-session to a prepaid web portal where they can purchase more time or data for their account.

To accept Authorize-Only requests, all of the following conditions must be true:

  • The AuthorizeOnly parameter in the [Configuration] section of radius.ini must=1.
  • The AcceptsAuthorizeOnly parameter in the [Bootstrap] section of the authentication plug-in you are using (either SQL, LDAP or other) must=1.
  • The Access-Request must contain the Service-Type attribute with a value=Authorize-Only.
  • The Message-Authenticator must be present and valid in the request.
  • A session must already exists in SBR Carrier for the requested AAA session ID (WiMAX).

Note: Care must be taken to ensure the .aut file used for authentications is separate from the .aut file used for Authorize-Only requests, even though the two files may be using the same database table. Also the AuthorizeOnly .aut file should not be able to handle or pass any authentications.

For complete details on the radius.ini file and its parameter settings, see the SBR Carrier Reference Guide.

Enabling the WiMAX Module and Configuring What Request Types Are Supported

This section describes the basic parameters for enabling the WiMAX module and for enabling processing of Access-Requests from the ASN-GW, DHCP server and home agent. For complete details, see the section on WiMAX Mobility Module Configuration File in the SBR Carrier Reference Guide.

The wimax.ini configuration file contains parameters that control basic behavior of the WiMAX mobility module of Steel-Belted Radius Carrier. Depending on your WiMAX deployment and the client types, you can enable which Accept-Requests you want Steel-Belted Radius Carrier to process. Table 66 describes the basic parameters for enabling WiMAX and configuring the requests you want the server to process.

Table 66: wimax.ini Parameters

[Section]

Parameter

Function

[Settings]

Enable

Specifies whether the WiMAX mobility module is enabled.

Set to 1 to enable WiMAX. This setting is required to use WiMAX.

Default value is 0.

[Settings]

Add-Keys-To-Access-Accept

Specifies whether to add the WiMAX-MSK to the Access-Accept.

  • If set to 1, WiMAX-MSK is added to the Access-Accept.
  • If set to 0, WiMAX-MSK is not added to the Access-Accept.

The default value is 0.

[ASNGW-
Requests]

Accept-ASNGW-Requests

Specifies whether ASN-GW request processing is enabled.

  • If set to 0, ASN-GW request processing is disabled. If an Access-Request is received from an ASN-GW, the request is rejected.
  • If set to 1, ASN-GW request processing is enabled. If an Access-Request is received from an ASN-GW, the request is processed.

Default value is 0.

[Home-Agent-
Requests]

Accept-Home-Agent-
Requests

Specifies whether home agent Access-Request processing is enabled.

  • If set to 0, home agent request processing is disabled. If an Access-Request is received from a home agent, the request is rejected.
  • If set to 1, home agent request processing is enabled. If an Access-Request is received from a home agent, the request is processed.

Default value is 0.

[DHCP-Server-
Requests]

Accept-DHCP-Server-
Requests

Specifies whether DHCP server request processing is enabled.

  • If set to 0, any DHCP server request is rejected.
  • If set to 1, DHCP server request processing is enabled.

Default value is 0.

 

Modified: 2017-03-07