[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]


Classifying Subscribers with the C-Web Interface

To define subscriber classification scripts:

  1. Click Configure, expand Shared>SAE, and then click Subscriber Classifier.

The Subscriber Classifier pane appears.

  1. From the Create new list, select Rule.
  2. Type a name for the new rule in the dialog box, and click OK.

The rule appears in the side pane and the Rule pane.

  1. Enter a script or a target as described in the Help text in the Main pane, and click OK.
  2. To configure a condition for a target:
  1. Expand the rule in the side pane, and click Condition.

The Condition pane appears.

  1. Type the subscriber classification condition name as described in Subscriber Classification Conditions, and click OK.

The condition appears in the side pane and the Condition pane.

Subscriber Classification Conditions

Subscriber classification conditions define match criteria that are used to find the subscriber profile. Use the fields in this section to define subscriber classification conditions.

dhcp

domainName

ifAlias

ifDesc

interfaceName

For JUNOS routing platforms: interfaceName="fe-0/1/0.0"

For forwarding interface: interfaceName="FORWARDING_INTERFACE"

loginName

The loginName can also be used to identify a subscriber session through the SAE CORBA remote API.

loginType

macAddress

nasPortId

radiusClass

retailerDn

serviceBundle

unauthenticatedUserDn

userName

virtualRouterName

For JUNOS routing platforms: name of the routing instance

Sending DHCP Options to the JUNOSe Router

Subscriber classification scripts support DHCP options conveyed through COPS. When COPS reports an address, the JUNOSe router sends DHCP options received for DHCP requests for that address. The DHCP options are available in the subscriber classification context for selecting the subscriber profile to load.

The fields in Table 5 are in the classification context of subscriber classification scripts.




Table 5: DHCP Options in UserClassificationContext Field 
DHCP Option
UserClassificationContext Field
Comments

giAddr

dhcp.giAddr

Relay agent gateway address

Option 82 data

dhcp.getOption(82)

Content is accessible with getSubOptions()

Client ID

dhcp.getOption(61).getString()

Lease time

dhcp.getOption(51).getInt()

Client requested parameter list

dhcp.getOption(55).getBytes()

Domain name sent to client

dhcp.getOption(12).getString() dhcp.getOption(15).getString()

12 = HostName 15 = DomainName

DNS server address(es) sent to client

dhcp.getOption(6).getIpAddresses()

Subnet mask

dhcp.getOption(1).getIpAddress()

NetBios name server address(es) sent to client

dhcp.getOption(44).getIpAddresses()

NetBios node type

dhcp.getOption(46).getBytes()

Default router address(es) sent to client

dhcp.getOption(3).getIpAddresses()

The DHCP options are accessible to the subscriber classification script with the following syntax:

dhcp.giAddr = "match"

# interpret option 61 as string
dhcp[61].string = "match"

# interpret option 1 (subnet) as dotted decimal IP
dhcp[1].ipAddress = "match" 

# option 82, suboption 1, interpreted as string
dhcp[82].subOptions[1].string = "match"

The received DHCP options are also stored in the UserSession and are available through the portal API (method User.getDhcpOptions).

Subscriber Classification Targets

The target of the subscriber classification script is an LDAP search string. The search string uses a syntax similar to an LDAP URL (see RFC 2255—The LDAP URL Format (December 1997)).The syntax is:

"baseDN [ ? [ attributes ] [ ? [ scope ] [ ? [ filter ] ] ] ]"

With the exception of baseDN all the fields are optional.

The result of the LDAP search must be exactly one directory object. If no object or more than one object is found, the subscriber session is terminated.


[Contents] [Prev] [Next] [Index] [Report an Error] [No Frames]