[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: ppp on demand trouble

Sigmund Svertingsson wrote:

Thanks for all the suggestions so far.

Here is a bit more detail:
Machine "Return" (it lives in my air conditioning return ducting at the end of the hallway) is my gateway to the outside world (via my dial-up ISP). My ISP gives me a dynamic IP address.
I'm pretty sure my statically configured LAN is fine, as I have to ssh into the headless Return machine to do anything.
I uncommented "demand" and "persist" in /etc/ppp/peers/provider and told the machine to "pppd call provider." 

The results of "ifconfig ppp0" and "ifconfig eth0" are:

ppp0      Link encap:Point-to-Point Protocol
         inet addr:10.64.64.64  P-t-P:10.112.112.112  Mask:255.255.255.255
         UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1500  Metric:1
         RX packets:0 errors:0 dropped:0 overruns:0 frame:0
         TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:3
         RX bytes:0 (0.0 b)  TX bytes:0 (0.0 b)

eth0      Link encap:Ethernet  HWaddr 00:02:E3:0F:83:A6
         inet addr:192.168.1.5  Bcast:192.168.1.255  Mask:255.255.255.0
         UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
         RX packets:56791 errors:0 dropped:0 overruns:0 frame:0
         TX packets:51685 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:100
         RX bytes:15205639 (14.5 MiB)  TX bytes:38855816 (37.0 MiB)
         Interrupt:9 Base address:0x1f00
But it doesn't dial when it (as I understand it) it should. I have tried firing up Mozilla on the masq'ed machine I'm typeng on now, as well as trying Lynx on the Return machine and pointing it at Google. Nothing provoked any kind of reaction from my spiffy USRobotics external modem.
Then, I commented out "demand" and "persist," killed pppd, and restarted it again. Beep, beep goes the modem, up comes the connection, and here is the ifconfig ppp0 output: 

ppp0      Link encap:Point-to-Point Protocol
         inet addr:66.81.203.95  P-t-P:66.81.235.139  Mask:255.255.255.255
         UP POINTOPOINT RUNNING NOARP MULTICAST  MTU:1524  Metric:1
         RX packets:3 errors:0 dropped:0 overruns:0 frame:0
         TX packets:4 errors:0 dropped:0 overruns:0 carrier:0
         collisions:0 txqueuelen:3
         RX bytes:66 (66.0 b)  TX bytes:87 (87.0 b)

What do I do now?

Siggy
First, my appologies for any confusion I may have generated on my previous post. Setting up for demand dialing and controling when you kick it off (bootup or manually via PON) are two different things.
The above info looks OK to me... similar to what I recall having here for those commands.
Could you take a look at your routing in the different configs you have posted? IIRC, the "defaultroute" or "gateway" on RETURN should be pointed at the ppp0 interface in the "demand" mode. I had some problems with this at first because I had set up a "gateway" entry for my eth0 interface on my equivalent of your "RETURN", and it just wouldn't dial out. I had to remove the "gateway" entry for that interface in /etc/network/interfaces file, and things would work OK. The pppd "defaultroute" option just wouldn't overwrite an existing one for the ethernet card(s). I only had to do this on my "gateway" computer...all the rest on my LAN pointed to that computer as their "gateway".
The strange thing in your situation is that manually starting pppd in the non-demand mode works. That doesn't jive with the above suggestion, but it is worth a look anyway. The "demand" funtion of pppd does work... I used it for several years until I got my Cable Modem connection. 

Cheers,
-Don Spoon-
Reply to: