Very Computer

Has anyone successfully used the pppd "demand" option, or is it considered a
joke and diald the True Way?

Does "pppd demand" randomly eat all your existing routes, effectively turing
off the ethernet device, or am I seeing things?
--
Alan Curry    |Declaration of   | _../\. ./\.._     ____.    ____.

--------------+save some time): |  \__/   \__/     \___:    \___:
 Linux,vim,trn,GPL,zsh,qmail,^H | "Screw you guys, I'm going home" -- Cartman

I think you're seeing things cos it works fine for me! I'm using 2.3.35
of pppd with demand enabled.

Cheers,

--
Steven

Newsletter editor and Webmaster of WACC - Wellington Acorn Computer Club
WACC pages: http://www.paradise.net.nz/~pbrowne/WACC/
Phone: (03) 358-5601 or (025) 908-448
My pages: http://www.paradise.net.nz/~acorn/

... We all live in a yellow subroutine.

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
initial dialing.

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

Are you using private IP addresses (192.168.x.y) for your LAN?  If you're
not, it could cause some weird problems.  I have my three machines set up as
192.168.100.1 (a K6-200 running Linux, ip-masq, and diald), 192.168.100.2 (a
K6-2-300 running Win98 connected by Fast Ethernet), and 192.168.100.3 (an
Apple IIGS connected by PPP to a serial port on the Linux box), and
communication between any of the three works whether the dial-up 56K link is
up or down.  Traffic on your local network shouldn't be affected by the
dial-up link.

  _/_
 / v \
(IIGS(  Scott Alfter (salfter at (bitte keine Spam) delphi dot com)
 \_^_/  http://people.delphi.com/salfter

                                                     ^^^^^
Did you read the original post? I'm trying to use the pppd "demand" option.
This is not diald. I suspect that is what is causing it to*up. Hearing
examples from a diald user is not helping, except to push me toward diald,
but for that to happen I'd like to hear someone say "Yes I had this problem
with pppd demand and switching to diald fixed it."

Quote:>K6-2-300 running Win98 connected by Fast Ethernet), and 192.168.100.3 (an
>Apple IIGS connected by PPP to a serial port on the Linux box), and
>communication between any of the three works whether the dial-up 56K link is
>up or down.  Traffic on your local network shouldn't be affected by the
>dial-up link.

Of course it shouldn't. But it is.

--
Alan Curry    |Declaration of   | _../\. ./\.._     ____.    ____.

--------------+save some time): |  \__/   \__/     \___:    \___:
 Linux,vim,trn,GPL,zsh,qmail,^H | "Screw you guys, I'm going home" -- Cartman