You need "interesting traffic" - i.e.
a dialer-group on your dialer interface pointing to
a dialer-list.
I think you're pretty good otherwise ... here's some
debugs for you:
debug dialer
debug modem
debug chat line 65
debug ppp negotiation
http://www.cisco.com/univercd/cc/td/...fg/advscen.pdf
has a pretty good sample config for you - see pp 4-15, 4-16.
Cheers,
Aaron
---
~ Hi, I'm trying to use the AUX port with a modem connected to dialup to an
~ ISP. I know the connectivity to the modem is fine as I can reverse telnet
~ to it and make it dial numbers with ATDT. I've setup the following config
~ which I thought would kick the dialer into action when I pinged
~ 192.168.200.1 but it doesn't work.
~
~ Can anyone shed any light on this for me please?
~
~ Thanks
~ Paul
~
~
~ chat-script Dialout ABORT ERROR ABORT BUSY "" "AT" OK "ATDT \T" TIMEOUT 45
~ CONNECT \c
~
~ interface Async65
~ no ip address
~ ip nat outside
~ encapsulation ppp
~ dialer in-band
~ dialer pool-member 20
~ async default routing
~ async mode dedicated
~
~ interface Dialer10
~ ip address negotiated
~ ip nat outside
~ encapsulation ppp
~ dialer pool 20
~ dialer idle-timeout 900
~ dialer string <number deleted>
~ ppp chap hostname <deleted>
~ ppp chap password 7 <deleted>
~
~ ip route 192.168.200.1 255.255.255.255 Dialer10
~
~ line aux 0
~ script dialer Dialout
~ modem InOut
~ modem autoconfigure type default
~ transport input all
~ stopbits 1
~ speed 115200
~ flowcontrol hardware
~
Similar Threads
