From: Jamie Lokier <jamie@shareable.org>
To: John Haxby <john.haxby@oracle.com>
Cc: qemu-devel@nongnu.org, "Richard W.M. Jones" <rjones@redhat.com>,
Avi Kivity <avi@redhat.com>, David Ahern <dsahern@gmail.com>
Subject: Re: [Qemu-devel] PATCH: enabling TCP keepalives - v3
Date: Tue, 5 May 2009 02:35:21 +0100 [thread overview]
Message-ID: <20090505013521.GC12731@shareable.org> (raw)
In-Reply-To: <49FB1F3C.8080805@oracle.com>
John Haxby wrote:
> Connection tracking devices often have a 10 minute timeout for idle
> connections -- the connection will magically evaporate after 600s of
> idle time.
Oh if only. I've seen NATs which expire after about 20 seconds. My
VPN is configured to send NAT-keepalive pings every 15 seconds because
of that.
> For those people that have seriously dodgy VPN connections that no
> amount of keepalive will keep up, they need some alternative. Probably
> starting with a new VPN :-)
Interesting perspective on VPNs. I use a VPN sometimes because it's
more stable than the underlying network and keeps TCP connections
going where the underlying network would not :-)
-- Jamie
next prev parent reply other threads:[~2009-05-05 1:35 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-30 19:40 [Qemu-devel] PATCH: enabling TCP keepalives - v3 David Ahern
2009-05-01 11:32 ` Richard W.M. Jones
2009-05-01 12:23 ` Jamie Lokier
2009-05-01 12:49 ` David Ahern
2009-05-01 15:23 ` Daniel P. Berrange
2009-05-01 15:47 ` David Ahern
2009-05-01 17:21 ` Richard W.M. Jones
2009-05-05 1:31 ` Jamie Lokier
2009-05-05 2:59 ` David Ahern
2009-05-01 15:52 ` Avi Kivity
2009-05-01 16:11 ` John Haxby
2009-05-05 1:35 ` Jamie Lokier [this message]
2009-05-01 14:43 ` Anthony Liguori
2009-05-01 14:47 ` David Ahern
2009-05-01 14:51 ` Anthony Liguori
2009-05-01 15:16 ` Paul Brook
2009-05-01 15:57 ` Anthony Liguori
2009-05-01 16:04 ` Paul Brook
2009-05-01 16:11 ` David Ahern
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20090505013521.GC12731@shareable.org \
--to=jamie@shareable.org \
--cc=avi@redhat.com \
--cc=dsahern@gmail.com \
--cc=john.haxby@oracle.com \
--cc=qemu-devel@nongnu.org \
--cc=rjones@redhat.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).