3.11.34. NasType Previous topic Parent topic Child topic Next topic

This optional parameter specifies the vendor type of this Client. It is required if you want Radiator to directly query the NAS to check on simultaneous sessions.
You can specify the maximum number of sessions allowable for a single user with the Simultaneous-Use check item, or for all the users in a Realm with the MaxSessions parameter in <Realm> or <Handler> clauses. In either case, during authentication, Radiator first checks its Session Database to see if the user's session count is exceeded. For more information, see Section 3.15. <SessionDatabase SQL> and Section 3.17. <SessionDatabase DBM>. Since this count can be inaccurate in the face of NAS reboots, lost packets etc. Radiator can also double check the count by interrogating the NAS directly (you enable this by specifying NasType in the Client clause).
If you specify unknown or do not specify any value at all, Radiator will never try to contact the NAS to check the user's sessions, and it will always assume that the sessions it thinks are present are correct. If you specify ignore, Radiator will never try to contact the NAS to check the users sessions, and it will always assume that there are no multiple sessions.
Tip
If Radiator detects problems or time-outs when using finger to verify simultaneous connections, it assumes that the user is still online (i.e. it assumes that the Session Database is correct).
Tip
You can also use NasType as a check item, to confirm that a request came from a client with a specific NasType.
The allowable values for NasType are:

Table 7. Allowable values of NasType, and their NAS query method

NasType Method used to connect to NAS
Livingston SNMP
Portslave Finger
PortslaveLinux Finger. For use with Portslave running on a Linux host, understands Linux finger format.
PortslaveMoxa Finger, requires ctlportslave to be installed as fingerd on the target Linux host. Supports Linux running Portslave and a Moxa multiport.
Cisco SNMP
CiscoVPDN SNMP, detects users terminated on a l2tp, pptp or l2f tunnel.
Colubris SNMP
Ascend Finger
AscendSNMP SNMP
Computone Finger
Cyclades SNMP
Hiper SNMP
NomadixSNMP SNMP
Redback SNMP
Shiva Finger
TotalControl pmwho
TotalControlSNMP SNMP
Bay, Bay5399SNMP, Bay8000SNMP SNMP
Bay4000SNMP SNMP
BayFinger Finger
Tigris, TigrisNew SNMP for new version of the Tigris MIB (i.e. firmware revision 10.1.4.14 or greater)
TigrisOld SNMP for old versions of the Tigris MIB
NortelCVX1800 SNMP
Xyplex Finger
Patton SNMP
Portmaster3 SNMP
Portmaster4 pmwho For use with Portmaster 4’s running ComOS 4.1 or later
Ping Verifies a login by ICMP pinging the Framed-IP-Address of the dialup user. This is not foolproof if the IP address has been reallocated. Requires that Radiator be run with root permissions (on Unix).
ignore Does not contact NAS under any circumstances. Always assumes that there are no multiple logins.
unknown The default value. Does not connect to the NAS under any circumstances. Always assumes the Session Database is correct.
CiscoSessionMIB SNMP, using the Session MIB available in Cisco IOS 12.2.15T and later.
Tip
You can add support for a new or custom NasTypes by adding a suitably named module to the Radius/Nas directory. Your new module should implement the isOnline function. See the existing Radius/Nas/*pm modules for examples. If you do implement your own module, send us a copy so we may include it in future releases.
Radiator uses a number of global parameters to specify how to communicate with the NAS. See Section 3.5.20. SnmpgetProg, Section 3.5.22. FingerProg, Section 3.5.23. PmwhoProg, Section 3.5.24. LivingstonMIB, Section 3.5.25. LivingstonOffs, and Section 3.5.26. LivingstonHole.
# Make Radiator ask the NAS to confirm multiple logins.
# its a Total Control box
NasType TotalControl