Hi,
On Wed, Dec 10, 2014 at 08:31:27AM +1300, Jason Haar wrote:
> LOL! It took Gert to spot the most obvious scenario ;-)
I'm good at breaking things :-)
> That really
> re-enforces what I think about this needing to be an "openvpn ping" type
> solution: it is irrelevant if the server is up or
On 10/12/14 08:09, Gert Doering wrote:
> In what kind of scenario would an OpenVPN server not be available, if
> the server itself still responds to pings?
> "The server process crashed".
LOL! It took Gert to spot the most obvious scenario ;-) That really
re-enforces what I think about this needin
Hi,
On Tue, Dec 09, 2014 at 10:40:01AM +0200, Samuli Seppänen wrote:
> > I also think it should be done with some "openvpn-ping" instead of icmp
> > ping because it confirms the server is available on the protocol/port
> > combination, whereas icmp doesn't
> In what kind of scenario would an OpenV
Oh! The sheer beauty of it!
Your patch has been applied to the master and release/2.3 branches.
commit e2e9a69c1ecc7142cc17d665076795215b6a8e9a (master)
commit f682c3d022265207377e327358211b0344f7d490 (release/2.3)
Author: David Sommerseth
List-Post: openvpn-devel@lists.sourceforge.net
Date:
On 09/12/14 21:40, Samuli Seppänen wrote:
> Would 3 pings and ping replies adequately measure the overall
> performance of OpenVPN server even for one particular VPN session? What
> if there's a temporary congestion somewhere between the "best" server
> and the client? I think that reliably determi
From: David Sommerseth
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Your patch has been applied to the master and release/2.3 branches.
commit 706283d3765d1ee62dbd913fbfc191855b92528d (master)
commit 333566fd9d1951be97397f5f19d8bc78fb025af9 (release/2.3)
Author: David Sommerseth
List-Post: o
Am 09.12.14 10:52, schrieb David Sommerseth:
> From: David Sommerseth
>
> The assert(0) happening if trying to use --tcp-nodelay in a client
> config is really not helpful at all. When this assert(0) was removed,
> another warning appeared that this could only be used in server
> configs. That
From: David Sommerseth
The assert(0) happening if trying to use --tcp-nodelay in a client
config is really not helpful at all. When this assert(0) was removed,
another warning appeared that this could only be used in server
configs. That itself is also quite silly, as clients can choose to
use
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
>
>
> So I propose openvpn itself could solve this problem - if it had some
> application layer way of "pinging" all available openvpn servers and
> choosing the one that responds "best". I'd suggest it only be supported
> for sites using "tls-aut
