From: Patrick McHardy <kaber@trash.net>
To: WGH <wgh@torlan.ru>
Cc: Jozsef Kadlecsik <kadlec@blackhole.kfki.hu>,
Phil Oester <kernel@linuxace.com>,
netfilter-devel@vger.kernel.org
Subject: Re: conntrack, idle TCP connection and keep-alives
Date: Sun, 27 Oct 2013 19:32:44 +0000 [thread overview]
Message-ID: <20131027193243.GA16338@macbook.localnet> (raw)
In-Reply-To: <526D6825.2090505@torlan.ru>
On Sun, Oct 27, 2013 at 11:23:17PM +0400, WGH wrote:
> On 27.10.2013 23:20, Patrick McHardy wrote:
> > On Sun, Oct 27, 2013 at 08:14:19PM +0100, Jozsef Kadlecsik wrote:
> >> I think a single flag could be sufficient: if the timer in conntrack goes
> >> off and the entry is in the ESTABLISHED state and this flag is not set,
> >> then send a TCP keepalive packet and start the timer with a short timeout.
> >> If we receive the reply packet, then the long ESTABLISHED timeout value
> >> can be restored and the flag cleared.
> > Sure, I think we wouldn't even need that flag, we can just send the keepalive
> > and set a short timeout. If a RST is received, the connection is killed
> > anyway, otherwise it will be refreshed with the ESTABLISHED timeout.
> >
> > But we do need a timestamp value to pass PAWS.
> I believe you forgot the third scenario: neither ACK nor RST is received
> in reply.
Actually no, "... and set a short timeout ...".
next prev parent reply other threads:[~2013-10-27 19:32 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-26 20:14 conntrack, idle TCP connection and keep-alives WGH
2013-10-27 15:34 ` Phil Oester
2013-10-27 18:01 ` Patrick McHardy
2013-10-27 18:38 ` Patrick McHardy
2013-10-27 19:14 ` Jozsef Kadlecsik
2013-10-27 19:20 ` Patrick McHardy
2013-10-27 19:23 ` WGH
2013-10-27 19:32 ` Patrick McHardy [this message]
2013-10-27 19:34 ` Patrick McHardy
2013-10-27 19:50 ` Jozsef Kadlecsik
2013-10-27 20:49 ` Jozsef Kadlecsik
2013-10-28 9:29 ` Patrick McHardy
2013-10-27 18:22 ` WGH
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=20131027193243.GA16338@macbook.localnet \
--to=kaber@trash.net \
--cc=kadlec@blackhole.kfki.hu \
--cc=kernel@linuxace.com \
--cc=netfilter-devel@vger.kernel.org \
--cc=wgh@torlan.ru \
/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).