Outbound-User

The RADIUS protocol defines this user type as a user on the local network who is using the modems to dial out (Similar to the NETServer’s host device dial out user). However, the RADIUS Outbound-User type is not defined on the NETServer. Do not use Outbound-Users in your RADIUS users file.

For authentication, the NETServer requires that host device dial out users be defined as login users who will be telnetted directly to a modem when they successfully log in. To add these users to RADIUS, define them as login-users.

Making NETServer talk to a RADIUS security server

This section assumes that RADIUS is already up and running on a workstation on your network.

1.Select the primary RADIUS security server:

set authentic <IP address>

2.Optional. Select the alternate RADIUS security server.

If your network has more than one RADIUS server, indicate which one will be considered the alternate server. If for some reason the primary server is unavailable, the NETServer will check with the alternate server.

set alternate <IP address>

3.Set the encryption key or secret.

This is the encryption key that the NETServer uses to encrypt user IDs and passwords and that the RADIUS server uses to decrypt them. The RADIUS server(s) must be set to the same encryption key or secret. The encryption key can be up to 15 characters long.

set secret <encryption key>

4.Save the changes. Use the following command:

save global

F-10 RADIUS

Page 270
Image 270
USRobotics NETServer/8, NETServer/16 manual Making NETServer talk to a Radius security server