Considerations For Using The Llid; Table 5: Radius Ietf Attributes In Preauthentication Request - Juniper JUNOSE SOFTWARE 11.0.X - BROADBAND ACCESS CONFIGURATION GUIDE 4-1-2010 Configuration Manual

For e series broadband services routers - broadband access configuration
Hide thumbs Also See for JUNOSE SOFTWARE 11.0.X - BROADBAND ACCESS CONFIGURATION GUIDE 4-1-2010:
Table of Contents

Advertisement

JUNOSe 11.0.x Broadband Access Configuration Guide

Table 5: RADIUS IETF Attributes in Preauthentication Request

The use of radius commands such as radius calling-station-format or radius
override calling-station-id to control or change the inclusion of these attributes in
the preauthentication request has no effect.
For more information about these attributes, see "RADIUS IETF Attributes" on
page 253.

Considerations for Using the LLID

The following considerations apply when you configure the router for subscriber
preauthentication:
78
Using the AAA Logical Line Identifier to Track Subscribers
Attribute
Number
Attribute Name
[1]
User-Name
[2]
User-Password
[4]
NAS-IP-Address
[5]
NAS-Port
[6]
Service-Type
[61]
NAS-Port-Type
[77]
Connect-Info
[87]
NAS-Port-Id
Only PPP subscribers authenticating through RADIUS can use the AAA LLID
feature on the router. PPP subscribers tunneled through domain maps cannot
take advantage of this feature.
The Calling-Station-Id [31] attribute is typically sent in RADIUS Access-Request
messages, not in Access-Accept messages as is the case for this feature. As a
result, your RADIUS server might require special configuration procedures to
enable the Calling-Station-Id attribute to be returned in Access-Accept messages.
See the documentation that came with your RADIUS server for information.
Description
Name of the user associated with the LLID, in the format:
NAS-Port:<NAS-IP-Address>:<Nas-Port-Id>
For example, nas-port:172.28.30.117:atm 4/1.104:2.104
Password of the user to be authenticated; always set to "
juniper"
IP address of the network access server (NAS) that is
requesting authentication of the user; for example,
172.28.30.117
Physical port number of the NAS that is authenticating the
user; this is always interpreted as a bit field
Type of service the user has requested or the type of service
to be provided; for example, framed
Type of physical port the NAS is using to authenticate the
user
Actual user name; for example, jdoe@xyzcorp.east.com
Text string that identifies the physical interface of the NAS
that is authenticating the user; for example,
atm 4/1.104:2.104

Advertisement

Table of Contents
loading

This manual is also suitable for:

Junose 11.0.x

Table of Contents