Subject: Re: -current pppd - no local route to local IP address
To: Paul Goyette <firstname.lastname@example.org>
From: David Brownlee <email@example.com>
Date: 01/10/1999 11:39:52
It would definitely seem the right thing to happen.
Have cc-ed this reply to tech-net, which is probably a more
appropriate forum for the question :)
.---- I've been too drunk to love ----.-- I've been too drunk to remember -.
| too drunk to care | the hell of the night before |
| looked like death, felt like hell | I've been drinking myself blind |
`------ been the worse for wear ------'-- and still I'll drink some more --'
On Sun, 10 Jan 1999, Paul Goyette wrote:
> I've noticed something odd with the -current version of pppd:
> When I connect to my ISP, a route gets added to the ISP's end of the ppp
> link via interface ppp0. But no route gets added to point to my local
> end of the link. Therefore, pings to my own IP address end up following
> the default route out to my ISP, and they never come back. (Or, if they
> _do_ come back, NetBSD simply forwards them back out the ppp0 link!)
> I've been able to work around the problem by manually adding a route to
> my end of the link:
> # route add <w.x.y.z> 127.0.0.1
> This mimics the behaviour of my Ethernet connection, which automatically
> seems to get a route for my local address pointing at lo0.
> But is this the correct behaviour? Or should pppd be adding the local
> route automatically?