[550] in linux-net channel archive
pppd misconfiguration brings down routing?
daemon@ATHENA.MIT.EDU (Ron Tapia)
Wed Jun 21 01:44:35 1995
Date: Tue, 20 Jun 1995 22:38:53 -0600 (MDT)
From: Ron Tapia <tapia@nmia.com>
To: linux-ppp <linux-ppp@vger.rutgers.edu>
cc: linux-net <linux-net@vger.rutgers.edu>
There's a machine on my network that I don't administrate, but that I
`help out with' every once in a while.
The administrator on that Linux machine (linux 1.1.45, named mahler) has
an ethernet at home and a network number (but routing isn't set up yet).
He set up pppd using proxyarp and a remote IP address that is not on
my network. He could connect via PPP and telnet to mahler from
hosts on his LAN. Eventually, though, this would cause mahler to
become unreachable from the outside world (my network and elsewhere).
Mahler would remain ping'able, but telnet connections would just hang.
This problem was solved by simply taking the proxyarp option out
of the pppd command on mahler.
I can see why using proxyarp with a remote IP address that isn't
routed to the directly connected ethernet would be a bad thing (or at
best pointless), but I don't understand why it would (seem) to mess
up routing in general.
To reiterate, this is not a problem anymore, but if someone has a little
time to spare, I could really use an explanation of this behavior. I
found this behavior to be very puzzling.
Thanks for listening,
Ron
--
Hagbard@LambdaMOO % I mean, it's the 90's. You can't just go
Ron@JaysHouseMOO % around trusting every layer you interface
Ron@MediaMOO % with. - tommyd@microsoft.com
<A HREF="http://www.nmia.com/~tapia/">My home page</A>
