netdev - Re: TCP timewait recycle/reuse for IPv6?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <20080317.121006.206760103.davem@davemloft.net>
Date:	Mon, 17 Mar 2008 12:10:06 -0700 (PDT)
From:	David Miller <davem@...emloft.net>
To:	opurdila@...acom.com
Cc:	rick.jones2@...com, netdev@...r.kernel.org
Subject: Re: TCP timewait recycle/reuse for IPv6?

From: Octavian Purdila <opurdila@...acom.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.
--
To unsubscribe from this list: send the line "unsubscribe netdev" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html