On 20/12/14 00:47, Jan Just Keijser wrote:
> packets and wait for answer (for a certain period of time). So, if
> your home internet connection drops out for , say, 20 seconds then the
> OpenVPN connection remains intact and so will all TCP-based sessions
> that are running over it.
Don't be so mo
Hi,
On Fri, Dec 19, 2014 at 02:46:23PM +0200, Pavel Bychikhin wrote:
> According to my experience, for OpenVPN UDP isn't better than TCP in
> case of bad connection with excessive packet loss. TCP has more
> sophisticated mechanisms than OpenVPN's --ping and --ping-restart.
> But the ability of
Jan Just,
According to my experience, for OpenVPN UDP isn't better than TCP in
case of bad connection with excessive packet loss. TCP has more
sophisticated mechanisms than OpenVPN's --ping and --ping-restart.
But the ability of OpenVPN to mask out the disconnect is really remarkable.
On 19.12.2
Hi,
On 17/12/14 04:26, Daniel Miller wrote:
> Slightly off-topic - but...
>
> I've noticed that my "normal" or direct ssh connections from my home
> (Windoze) to my office (Linux) can be subject to instability -
> particularly if I simply leave PuTTY connected and idle for a while at
> some point
On Tue, Dec 16, 2014 at 9:26 PM, Daniel Miller wrote:
> Slightly off-topic - but...
>
> I've noticed that my "normal" or direct ssh connections from my home
> (Windoze) to my office (Linux) can be subject to instability -
> particularly if I simply leave PuTTY connected and idle for a while at
> s
Slightly off-topic - but...
I've noticed that my "normal" or direct ssh connections from my home
(Windoze) to my office (Linux) can be subject to instability -
particularly if I simply leave PuTTY connected and idle for a while at
some point it will get disconnected. However...if I activate my
