Filter
Top Products
Telco and ISP Dial Scenarios and Configurations
Small- to Medium-Scale POPs
DNC-308
Cisco IOS Dial Services Configuration Guide: Network Services
line aux 0
login authentication console
line vty 0 4
login authentication vty
transport input telnet rlogin
!
end
Some service providers use a remote TACACS+ or RADIUS security server in this dial-in scenario. The
following example shows a TACACS+ entry that appears in the configuration file of a remote security
server:
user = PCuser1 {
login = cleartext "dialpass1"
chap = cleartext "dialpass1"
service = ppp protocol = ip {
addr-pool = dialin_pool
}
service = exec {
autocmd = "ppp negotiate"
}
}
user = PCuser2 {
login = cleartext "dialpass2"
chap = cleartext "dialpass2"
service = ppp protocol = ip {
addr-pool = dialin_pool
}
service = exec {
autocmd = "ppp negotiate"
}
}
user = PCuser3 {
login = cleartext "dialpass3"
chap = cleartext "dialpass3"
service = ppp protocol = ip {
addr-pool = dialin_pool
}
service = exec {
autocmd = "ppp negotiate"
}
}
Running Configuration for Robbed-Bit Signalling
The following example shows a single Cisco AS5200 access server configured to support remote client
PCs dialing in with analog modems over traditional T1 lines. Digital ISDN calls do not transmit across
these older types of channelized lines. The configuration assumes that the client can dial in and connect
to the router in either terminal emulation mode (text only) or PPP packet mode.
Note The following configuration works only for analog modem calls. It includes no serial
D-channel configuration (Serial 0:23 and Serial 1:23).