On Sun, Nov 5, 2017 at 12:11 PM, Gert Doering <g...@greenie.muc.de> wrote:

> Hi,
>
> On Mon, Jul 17, 2017 at 02:22:55PM +0200, Jan Just Keijser wrote:
> > On 17/07/17 14:14, Gert Doering wrote:
> > > Hi,
> > >
> > > On Mon, Jul 17, 2017 at 02:10:11PM +0200, Jan Just Keijser wrote:
> > >> this problem is NOT present in OpenVPN 2.3.17; the same warning
> appears (route gateway is ambiguous) but the route is added
> > >> anyway. This seems to be a regression in 2.4.
> > > Can we have a log, please?
> > attached: config and log (with hostnames anonymized)
>
> This indeed is a regression, or a "non-handled special case in the
> iservice"
> (waking up Selva and Heiko).


> 2.3 is calling route.exe, which seems to just handle this case fine
> ("the given gateway address is present on two different interfaces",
> which I find ambiguous myself :-) ).
>

When this was reported I had made a patch to handle this, somehow forgot to
send it in. Or could be that I was not totally happy with it (or not
tested). Anyway,
the next email has the patch as I have it -- will do any cleanup if needed
provided
it looks sensible.

Selva
------------------------------------------------------------------------------
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
_______________________________________________
Openvpn-devel mailing list
Openvpn-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/openvpn-devel

Reply via email to