[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index][Old Index]
Re: bin/44032 (pppd: proxyarp is not working)
The following reply was made to PR bin/44032; it has been noted by GNATS.
From: =?ISO-8859-1?Q?Egerv=E1ry_Gergely?= <gergely%egervary.hu@localhost>
To: gnats-bugs%NetBSD.org@localhost, gnats-admin%netbsd.org@localhost,
Subject: Re: bin/44032 (pppd: proxyarp is not working)
Date: Fri, 07 Jun 2013 09:33:26 +0200
> Although this is supposed to work, why don't you just add a route to the
> host/net that you want to access on your default gateway that points to
> the machine which has the ppp link?
Routing only works if you have a remote PPP peer in a different IP
subnet. Then, you do not need proxyarp, but you need routing.
In this scenario, I have a LAN subnet, called 10.0.0.0/8, with the PPP
server address 10.0.0.1. The remote PPP peer dials in via VPN, and picks
up an IP address (10.0.0.192) from the LAN subnet. This one requires
working proxyarp. Without proxyarp, LAN hosts cannot reach the remote
PPP peer, as they have a network route for this subnet on their LAN
interface, and won't go to their default gateway.
In a perfect world all WAN connections should use Layer 3 routing.
Actually, the world is not perfect - I cannot change the topology -
and it used to work this way for more than 15 years.
Main Index |
Thread Index |