> Telling users what to do is fine and sensible, but has a 0% chance of > working. Wouldn't it be better than openvpn checks the state of the > interface right at the beginning and simply refuses to connect if it's > in an unusable state? I'd rather the client went into an infinite loop > of starting, checking, exiting, starting, etc than involve the server > (which affects other users). A 5-10 second delay after such a condition > was detected would help reduce any client impact too of course Hi,
I would file a bug report on this, as it's something we should fix. -- Samuli Seppänen Community Manager OpenVPN Technologies, Inc irc freenode net: mattock
signature.asc
Description: OpenPGP digital signature
------------------------------------------------------------------------------ Dive into the World of Parallel Programming The Go Parallel Website, sponsored by Intel and developed in partnership with Slashdot Media, is your hub for all things parallel software development, from weekly thought leadership blogs to news, videos, case studies, tutorials and more. Take a look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________ Openvpn-users mailing list Openvpn-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/openvpn-users
