All of lore.kernel.org
 help / color / mirror / Atom feed
From: WGH <wgh@torlan.ru>
To: netfilter-devel@vger.kernel.org
Subject: conntrack, idle TCP connection and keep-alives
Date: Sun, 27 Oct 2013 00:14:48 +0400	[thread overview]
Message-ID: <526C22B8.5030102@torlan.ru> (raw)

Hello!

It seems that, when masquerading, conntrack silently drops idle
connection after nf_conntrack_tcp_timeout_established seconds. This's
pretty terrible, as application inside the network, if it never sends
anything, will never know that connection was dropped.

RFC 5382 gives us a solution to this:
> A NAT can check if an endpoint for a session has crashed by sending a
> TCP keep-alive packet and receiving a TCP RST packet in response.

However, it I couldn't find such feature in netfilter. It would be
pretty nice to have.

It would be much more effective than enabling keep-alives system-wide
(which is not even possible in practice). It makes sense that NAT has to
manage such things, as only NAT knows the timeouts of itself. If there's
a NAT along the route, it will send keep-alives (overhead, but
inevitable). If there's no NATs, there will be no keep-alives. Simple.

AFAIK, Cisco implements this under name Dead Connection Detection.

             reply	other threads:[~2013-10-26 20:22 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-10-26 20:14 WGH [this message]
2013-10-27 15:34 ` conntrack, idle TCP connection and keep-alives 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
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=526C22B8.5030102@torlan.ru \
    --to=wgh@torlan.ru \
    --cc=netfilter-devel@vger.kernel.org \
    /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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.