From: James Morris <jmorris@intercode.com.au>
To: Cesar Eduardo Barros <cesarb@nitnet.com.br>
Cc: David Schwartz <davids@webmaster.com>, <linux-kernel@vger.kernel.org>
Subject: Re: TCP keepalive seems to send to only one port
Date: Sun, 24 Dec 2000 12:52:12 +1100 (EST) [thread overview]
Message-ID: <Pine.LNX.4.31.0012241243440.17066-100000@blackbird.intercode.com.au> (raw)
In-Reply-To: <20001223223814.A2281@flower.cesarb>
On Sat, 23 Dec 2000, Cesar Eduardo Barros wrote:
> Then what do you do when you are behind a NAT? And how do you expire entries in
> ESTABLISHED state that could stay lingering forever without some sort of
> keepalive? (The FINs might have been lost due to a conectivity transient, so
> you can have another perfectly valid and alive connection with the same host,
> and application-level timeouts are useless for some applications
> (*cough*nc*cough*))
Typically, you choose a practical value for timing out inactive but
otherwise seemingly established TCP connections. The 2.4 connection
tracking code (used for NAT) uses a value of five days for this.
- James
--
James Morris
<jmorris@intercode.com.au>
-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
Please read the FAQ at http://www.tux.org/lkml/
next prev parent reply other threads:[~2000-12-24 2:23 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2000-12-23 23:31 Cesar Eduardo Barros
2000-12-24 0:19 ` David Schwartz
2000-12-24 0:38 ` Cesar Eduardo Barros
2000-12-24 1:52 ` James Morris [this message]
2000-12-24 2:20 ` Cesar Eduardo Barros
2000-12-25 15:27 ` Igmar Palsenberg
2000-12-25 14:58 ` Cesar Eduardo Barros
2000-12-26 0:33 ` David Schwartz
2000-12-26 0:46 ` Cesar Eduardo Barros
2000-12-26 0:59 ` David Schwartz
2000-12-24 9:14 ` Andi Kleen
2000-12-24 14:12 ` Cesar Eduardo Barros
2000-12-27 2:00 Bernd Eckenfels
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=Pine.LNX.4.31.0012241243440.17066-100000@blackbird.intercode.com.au \
--to=jmorris@intercode.com.au \
--cc=cesarb@nitnet.com.br \
--cc=davids@webmaster.com \
--cc=linux-kernel@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®