>> Does "pppd demand" randomly eat all your existing routes, effectively turing
>> off the ethernet device, or am I seeing things?
>I think you're seeing things cos it works fine for me! I'm using 2.3.35
>of pppd with demand enabled.
OK, here's what happens: at boot time, the loopback and ethernet devices are
ifconfiged and routed. A blanket masq rule is added with ipfwadm. The local
network works. Other local machines can be pinged. Then comes the
"pppd demand defaultroute" (which lots of other options too but those are the
big ones) and pings across the ethernet stop working. The local route is
still in the routing table, but nothing makes it through. killing pppd causes
the local net to start working again.
If I send a ping out to the world to force pppd to dial, it works, and after
the connection is established, the ethernet starts working again. But that's
not helpful because I want the masqueraded boxes to be able to trigger the
It sure looks like pppd eats all routes while it's waiting for a demand dial.
Alan Curry |Declaration of | _../\. ./\.._ ____. ____.
--------------+save some time): | \__/ \__/ \___: \___:
Linux,vim,trn,GPL,zsh,qmail,^H | "Screw you guys, I'm going home" -- Cartman