[OpenVPN home] [Date Prev] [Date Index] [Date Next]
[OpenVPN mailing lists] [Thread Prev] [Thread Index] [Thread Next]
Web openvpn.net

Re: [Openvpn-users] Re: 2.0 Feature Freeze Discussion

  • Subject: Re: [Openvpn-users] Re: 2.0 Feature Freeze Discussion
  • From: James Yonan <jim@xxxxxxxxx>
  • Date: Thu, 2 Dec 2004 18:05:24 -0700 (MST)

> Instead I'd like to show a couple of informative messages about the 
> connecting process based on the STATE like:
> * Waiting for initial respone from server.
> * Authenticating with server.
> * Downloading configuration from server.
> * Assigning IP address to virtual network interface.
> * Adding routes to system.
> * Connected
> The number of states should be enough for a user to make a basic 
> assumption on why a connection fails without browsing a log. If he still 
> can't find the cause just by seeing on which STATE it fails, he will 
> of cource have to open the real log to get details.

The problem is that if an error occurs in a state, it doesn't necessarily
mean that OpenVPN will remain in that state.  For example routes could
fail to be added, and because such a failure is considered by OpenVPN to
be non-fatal, it would advance to the Connected (with errors) state.


Openvpn-users mailing list