From: Eric Dumazet <dada1@cosmosbay.com>
To: "Robert Iakobashvili" <coroberti@gmail.com>
Cc: "Evgeniy Polyakov" <johnpol@2ka.mipt.ru>,
NetDev <netdev@vger.kernel.org>
Subject: Re: Beyond 64K TCP connections limit per IP-address
Date: Wed, 4 Jul 2007 12:06:52 +0200 [thread overview]
Message-ID: <20070704120652.262380eb.dada1@cosmosbay.com> (raw)
In-Reply-To: <7e63f56c0707040240p4ec962fajd93074909b07ea03@mail.gmail.com>
On Wed, 4 Jul 2007 11:40:48 +0200
"Robert Iakobashvili" <coroberti@gmail.com> wrote:
> On 7/4/07, Evgeniy Polyakov <johnpol@2ka.mipt.ru> wrote:
> > On Wed, Jul 04, 2007 at 09:50:31AM +0200, Robert Iakobashvili (coroberti@gmail.com) wrote:
> > > If I am correct, a TCP server can make up to
> > > 64K accepts for a port at a single IP-address.
> >
> > No, it is essentially unlimited - linux uses local/remote addr/port
> > tuples for hash chains, so there is no per-addr limits.
> > If there is some kind of binds, then yes, only 64k ports per address.
>
> Thanks, it clarified me the issue.
> Probably, I am experiencing some local problem with
> the web-server I am using for tests.
If your setup is :
Server A with one IP address listening to port 80
'Client B' with one IP address, trying to open many sockets to A (port 80)
Then yes you have a 64k limit for this particular client B. Just add 15 more clients (or 16 IP addresses on B) if you really want to stress A ;)
next prev parent reply other threads:[~2007-07-04 10:07 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
2007-07-04 9:36 ` Evgeniy Polyakov
2007-07-04 9:40 ` Robert Iakobashvili
2007-07-04 10:06 ` Eric Dumazet [this message]
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=20070704120652.262380eb.dada1@cosmosbay.com \
--to=dada1@cosmosbay.com \
--cc=coroberti@gmail.com \
--cc=johnpol@2ka.mipt.ru \
--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 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).