From: Snow, Tim (timothy.snow@eds.com)
Date: Mon Jun 30 2003 - 02:56:42 GMT-3
Do you have "async default routing" on your line? If you need exact configs
of my setup at home let me know as I also use a POTS simulator with external
modems.
Cheers..
interface Async33
no ip address
encapsulation ppp
dialer in-band
dialer pool-member 2
async default routing
no fair-queue
no cdp enable
interface Dialer1
ip unnumbered Loopback1
encapsulation ppp
dialer pool 2
dialer idle-timeout 300
dialer string 10001
dialer hold-queue 50
dialer-group 1
no peer default ip address
no cdp enable
ppp authentication chap
ppp chap hostname maui-backup
router ospf 1
network 172.22.0.0 0.0.255.255 area 0
network 192.168.10.0 0.0.0.3 area 0
ip classless
no ip http server
dialer-list 1 protocol ip permit
line 33
script dialer mica.*
modem InOut
transport input all
line aux 0
line vty 0 4
login
!
end
-----Original Message-----
From: Kelly Cobean [mailto:kcobean@earthlink.net]
Sent: Sunday, June 29, 2003 9:34 PM
To: lab groupstudy
Subject: Dialer profiles w/ callback???
Hey all,
Been awhile since I've posted, but I'm really stuck on something. I'm
using a pair of POTS lines and dialer profiles for DDR connectivity. I
chose to use dialer profiles because you can't use "ip ospf demand-circuit"
on an async interface (every time the link drops, it's an interface state
change which generates an LSA update, bringing the link back up, whereas a
dialer interfaces spoof's an "up" state.) The problem I'm having is that
I'm trying to configure ppp callback on the dialer interfaces, and so far, I
have not been able to make it work. I occasionally see the error "LCP not
allowed on a dialer profile". Has anyone been able to make callback work
with dialer profiles? It works flawlessly on async interfaces, but I've got
the demand circuit requirement that's forcing me to use dialer profiles.
Any input is greatly appreciated. Thanks.
This archive was generated by hypermail 2.1.4 : Fri Jul 04 2003 - 11:11:14 GMT-3