Message-ID: <53C28CED.6060501@...1227...> Date: Sun, 13 Jul 2014 15:43:09 +0200 From: Arne Schwabe MIME-Version: 1.0 References: <1405075659-7881-1-git-send-email-arne@...1227...> <1405254527-23833-1-git-send-email-gert@...1296...> In-Reply-To: <1405254527-23833-1-git-send-email-gert@...1296...> Subject: Re: [Openvpn-devel] [PATCH] Fix server routes not working in topology subnet with --server [v3] List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Content-Type: text/plain; charset=windows-1252 Content-Transfer-Encoding: 7bit To: Gert Doering , openvpn-devel@lists.sourceforge.net On 13.07.2014 14:28, Gert Doering wrote: > From: Arne Schwabe > > The IPv4 routing code needs an IPv4 address to point a route to, and > in --topology subnet mode, the *server* did not have one set by default. > > So we now just default --route-gateway to the next address right after > the server address - the specific address doesn't matter, as the correct > next-hop will not be resolved by the host OS but by the OpenVPN daemon. > All that is needed is "it's in the subnet routed to the tun interface". > > Using the server address itself would work on unix, but doesn't work with > the Windows TAP driver (as it does not spoof ARP responses for itself). > > ACK. Arne