From: Bill Fink <billfink@mindspring.com>
To: David Miller <davem@davemloft.net>
Cc: opurdila@ixiacom.com, rick.jones2@hp.com, netdev@vger.kernel.org
Subject: Re: TCP timewait recycle/reuse for IPv6?
Date: Tue, 18 Mar 2008 01:27:39 -0400 [thread overview]
Message-ID: <20080318012739.6a5c8602.billfink@mindspring.com> (raw)
In-Reply-To: <20080317.121006.206760103.davem@davemloft.net>
On Mon, 17 Mar 2008, David Miller wrote:
> From: Octavian Purdila <opurdila@ixiacom.com>
> Date: Mon, 17 Mar 2008 20:04:33 +0200
>
> > While running the same traffic with IPv4, the timewait recyle/reuse
> > features kicks in and keeps the number of TIMEWAIT sockets to under
> > a 1000.
>
> Timewait recycling should not be enabled if any of your connections
> could even potentially be going through a firewall or NAT box.
> In such cases, the invariants which are necessary for timewait
> recycling to be valid are not present and thus you could risk
> connection or data corruption.
>
> Timewait recycling depends upon end systems really being end
> systems on a connection level. With NAT, that is no longer
> true, as the NAT box will reuse the same port for different
> end nodes in subsequent connections.
I have this hope that as IPv6/IPSEC becomes more commonplace, perhaps
it can help get back to the original TCP/IP direct end system to
end system model of communication, and reduce the current need for
such unfortunately necessary kludges as NAT boxes.
-Bill
prev parent reply other threads:[~2008-03-18 5:27 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-17 16:18 TCP timewait recycle/reuse for IPv6? Octavian Purdila
2008-03-17 17:43 ` Rick Jones
2008-03-17 18:04 ` Octavian Purdila
2008-03-17 18:15 ` Rick Jones
2008-03-17 19:11 ` David Miller
2008-03-17 19:10 ` David Miller
2008-03-18 5:27 ` Bill Fink [this message]
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=20080318012739.6a5c8602.billfink@mindspring.com \
--to=billfink@mindspring.com \
--cc=davem@davemloft.net \
--cc=netdev@vger.kernel.org \
--cc=opurdila@ixiacom.com \
--cc=rick.jones2@hp.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).