From: Florian Weimer <fweimer@bfk.de>
To: "Robert Iakobashvili" <coroberti@gmail.com>
Cc: NetDev <netdev@vger.kernel.org>
Subject: Re: Beyond 64K TCP connections limit per IP-address
Date: Wed, 04 Jul 2007 10:19:50 +0200 [thread overview]
Message-ID: <82sl84pom1.fsf@mid.bfk.de> (raw)
In-Reply-To: <7e63f56c0707040050k7d1a9daeq276d7d924ef802e8@mail.gmail.com> (Robert Iakobashvili's message of "Wed, 4 Jul 2007 09:50:31 +0200")
* Robert Iakobashvili:
> If I am correct, a TCP server can make up to
> 64K accepts for a port at a single IP-address.
I don't think such a limit exists. In typical configurations, a
single client IP address can only establish a few tens of thousands of
TCP connections to one server port. But as soon as multiple clients
are involved, there is virtually no protocol-imposed limit.
--
Florian Weimer <fweimer@bfk.de>
BFK edv-consulting GmbH http://www.bfk.de/
Kriegsstraße 100 tel: +49-721-96201-1
D-76133 Karlsruhe fax: +49-721-96201-99
next prev parent reply other threads:[~2007-07-04 8:37 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-04 7:50 Beyond 64K TCP connections limit per IP-address Robert Iakobashvili
2007-07-04 8:19 ` Florian Weimer [this message]
2007-07-04 9:36 ` Evgeniy Polyakov
2007-07-04 9:40 ` Robert Iakobashvili
2007-07-04 10:06 ` Eric Dumazet
2007-07-05 9:28 ` Robert Iakobashvili
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=82sl84pom1.fsf@mid.bfk.de \
--to=fweimer@bfk.de \
--cc=coroberti@gmail.com \
--cc=netdev@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.