Hi, On Fri, Jul 6, 2018 at 3:24 PM, Selva Nair <[email protected]> wrote: > > Hi, > > Copying the devel list as a reminder that "we" have been asking for this > change for a long time :) > > On Fri, Jul 6, 2018 at 2:48 PM, Gert Doering <[email protected]> wrote: >> >> Hi, >> >> On Fri, Jul 06, 2018 at 08:25:02AM -0700, Selva Nair wrote: >> > Can we do something about this in openvpn core, so that the GUI can be >> > report route errors? >> >> Currently when we get CONNECTED,SUCCESS we turn the icon green. If we get >> >> CONENCTED,ERROR we keep it amber and the state as "connecting.." even if >> >> the initialization sequence completes. >> > >> > So route errors can still be treated as non-fatal but we want to get >> > CONNECTED,ERROR in such cases.
+1 to routing errors causing CONNECTED,ERROR (I didn't even know that was possible). This confuses many Tunnelblick users. I'd be happy for routing errors to cause a FATAL error as long as the errors weren't caused by "route already exists" or something like that. But I assume that's too much trouble. Best regards, Jon ------------------------------------------------------------------------------ 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 [email protected] https://lists.sourceforge.net/lists/listinfo/openvpn-devel
