Hi, On Fri, Jun 19, 2015 at 06:09:17PM +0200, Jan Just Keijser wrote: > I don't know what the reasoning was behind making "route failures" > non-fatal, but strictly speaking the tunnel is functioning - it's just > the routing that failed :) > I'd be in favour of adding YetAnotherOption to override the "route > failure" behaviour - but the real solution on e.g. the Windows side is > to alter the GUI to pick up any routing failures and warn the user.
The GUI has no say here... OpenVPN calls route.exe (or /sbin/route) and
just ignores errors (logs, though) - so the GUI would have to parse the log,
or we would have to add special signalling towards the management interface.
Which wouldn't help the "there is no GUI" case...
> As a side note: I've gotten my hands on Windows 8.1 for my laptop. I'll
> install win8.1 (dual boot) on it shortly, so that we can debug the
> routing/ipconfig issues.
Well, for *this* issue, there's not much to debug - it's a conscious
decision in the code to call openvpn_exec_check() with the flags set to
"errors are not fatal"...
OTOH, it seems that Steffan and Heiko might have a testable interactive
service soon - which would solve the permission issue on windows nicely :-)
(Heiko: how does the iservice handle failure to install a route?)
gert
--
USENET is *not* the non-clickable part of WWW!
//www.muc.de/~gert/
Gert Doering - Munich, Germany g...@greenie.muc.de
fax: +49-89-35655025 g...@net.informatik.tu-muenchen.de
pgp5wqXb6578Q.pgp
Description: PGP signature
