netdev - Beyond 64K TCP connections limit per IP-address

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-next>] [day] [month] [year] [list]

Date:	Wed, 4 Jul 2007 09:50:31 +0200
From:	"Robert Iakobashvili" <coroberti@...il.com>
To:	NetDev <netdev@...r.kernel.org>
Subject: Beyond 64K TCP connections limit per IP-address

If I am correct, a TCP server can make up to
64K accepts for a port at a single IP-address.

If one would like to have e.g. 1M TCP connections
to a single IP-address of a powerful server (without load balancer),
how to make such setup?

There is a workaround to arrange several secondary IP-addresses
each serving ~64K connections.
Any other options?

Server places to the outgoing packet source port the port
of the server listening socket. Actually, the ephemeral ports at the
server side are used as the hashing keys.
Could it be played, tricked somehow?

Y comments would be appreciated.

-- 
Sincerely,
Robert Iakobashvili,
coroberti %x40 gmail %x2e com
...........................................................
http://curl-loader.sourceforge.net
A web testing and traffic generation tool.
-
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