Hi! I saw your earlier posting too, maybe the list server was a little slow? Here's what I think might be happening here: Diald normally runs pppd itself, after the connect script exits. Your connect program is 'pppd', and diald is waiting for it to terminate before going ahead with running pppd, changing default routes, running your addroute script etc. You're not getting the default route changed to point at your ppp interface because diald is still waiting for the connect program (pppd in your case) to finish :-) Try this as your connect statement in diald.conf : connect 'chat -v "" ATDT7640360 CONNECT "" ogin: mylogin password: mypassword' When chat finishes, diald should go ahead and start pppd and make a default route to ppp0. You may have to make sure that your static IP local address can be resolved locally by pppd, or you might end up with a catch-22 where pppd is waiting for name resolution of the local ip address, but name resolution keeps timing out because your ppp link isn't up :-( I ended up running named to get around that one here. This isn't a problem when you run pppd manually, as there is no default route to a nameserver and the name resolution fails immediately. Regards, Mark. At 10:54 AM 14/09/98 -0700, you wrote: >First try this morning apparently didn't make it > >Hi, > >I'm configuring system to use diald but m hving what I consider bizarre >problems. My pppd connection works fine. The diald connection will only >ping as far as the terminal server it connects to but not beyond. Since I >have a static IP address on this box, I set up my dild.conf like this: > mode ppp > connect /usr/local/bin/qwk > device /dev/cua0 > speed 115200 > modem > lock > crtscts > local 204.57.170.245 > remote 204.57.170.30 > defaultroute > include /usr/lib/diald/standard.filter > >My /usr/local/binqwk file is an abbreviated version of my ppp connection >file: > pppd connect 'chat -v "" ATDT7640360 CONNECT "" ogin: mylogin assword: > mypassword' > >When I invoke pppd my routing table is like this: > >Kernel IP routing table >Destination Gateway Genmask Flags Metric Ref Use Iface >192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 dummy0 >204.57.170.30 0.0.0.0 255.255.255.255 UH 1 0 0 sl0 >192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 25 eth0 >127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 1 lo >0.0.0.0 0.0.0.0 0.0.0.0 U 1 0 2 sl0 > >A packet headed out beyond the LAN results in diald connecting >sucessfully to the provider and a routing table like this: > >Kernel IP routing table >Destination Gateway Genmask Flags Metric Ref Use Iface >192.168.1.1 0.0.0.0 255.255.255.255 UH 0 0 0 dummy0 >204.57.170.30 0.0.0.0 255.255.255.255 UH 0 0 0 ppp0 >204.57.170.30 0.0.0.0 255.255.255.255 UH 1 0 0 sl0 >192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 26 eth0 >127.0.0.0 0.0.0.0 255.0.0.0 U 0 0 1 lo >0.0.0.0 0.0.0.0 0.0.0.0 U 1 0 3 sl0 > >However, I can only ping to 204.57.170.30 (the terminal server). No ping >replies or connects are successful beyond this point. However, when I >kill diald and simply set up a ppp connection I can ping through and >connect easily beyond 204.57.170.30. > >If I delete the default route throught sl0 and add a manual route to >204.57.170.30 after the ppp link is up, everything works fine (but that >route drops out after the link is dropped) > >I tried an addroute script in the diald.conf file but that doesn't work. > >Anyone have any ideas? > >Craig > > > >- >To unsubscribe from this list: send the line "unsubscribe linux-diald" in >the body of a message to [EMAIL PROTECTED] > - To unsubscribe from this list: send the line "unsubscribe linux-diald" in the body of a message to [EMAIL PROTECTED]
