A
CCESS
G
ATEWAY
174
System Administration
The following screen shows a realm routing policy that handles suffix-based usernames
using a tunnel profile.
This differences in this example are that the realm name is “tcisp.com”, “Suffix match
only” is enabled (the delimiter in this case is “@”), and a tunnel profile, “LNSOne”, is
selected instead of a RADIUS service profile.
This means that this realm routing policy will match usernames that are of the format
“[email protected]”. Since this policy references a tunnel profile, no RADIUS access
requests will be sent to any RADIUS server. In this case, the NSE will use the L2TP tunnel
parameters specified in the tunnel profile to establish a tunnel and pass the username/
password input to the tunnel server.
Again, as before, the username passed to the tunnel server will have realm information
stripped since the checkbox for “Strip off routing information when sending to tunnel
server” is checked. This checkbox may be unchecked if it is necessary for usernames to
contain realm information for user authentication.
Summary of Contents for Access Gateway
Page 1: ......
Page 12: ...ACCESS GATEWAY xii ...
Page 51: ...ACCESS GATEWAY Introduction 39 ...
Page 84: ...ACCESS GATEWAY 72 Installing the Access Gateway ...
Page 90: ...ACCESS GATEWAY 78 Installing the Access Gateway ...
Page 95: ...ACCESS GATEWAY System Administration 83 ...
Page 96: ...ACCESS GATEWAY 84 System Administration ...
Page 146: ...ACCESS GATEWAY 134 System Administration ...
Page 161: ...ACCESS GATEWAY System Administration 149 ...
Page 185: ...ACCESS GATEWAY System Administration 173 ...
Page 205: ...ACCESS GATEWAY System Administration 193 The Network Interfaces screen appears ...
Page 310: ...ACCESS GATEWAY 298 The Subscriber Interface ...
Page 376: ...This page intentionally left blank ACCESS GATEWAY 364 Troubleshooting ...
Page 378: ...This page intentionally left blank ACCESS GATEWAY 366 ...