From: Chris Friesen <chris.friesen@genband•com>
To: netdev@vger•kernel.org
Subject: how to listen() on single IP address but very many ports?
Date: Fri, 18 Feb 2011 11:55:58 -0600 [thread overview]
Message-ID: <4D5EB2AE.5050703@genband.com> (raw)
I have an application team that needs to listen() for tcp connections on
many ports (and by many I mean pretty much all 64K ports). However, the
connections are short-lived, and the number of active connections at any
given time is small.
Apparently when they tried this before on an older kernel the
performance of the naive "open 60K sockets and call listen()" solution
was not acceptable, so they used NAT with port mapping to direct all the
incoming packets to a single real port. However, they now want to add
support for IPv6 and this solution won't work.
What's the recommended method for efficiently listening on this many
ports? Should I be able to efficiently listen() on that many sockets
using epoll or similar? If there isn't a way to do this, is there an
equivalent IPv6 workaround?
One possible solution that came up was to implement a PORT_ANY which
would match any incoming request that didn't already have an explicit
listener. Even better would be a way to bind a single listening socket
to a range of ports.
Has anyone ever considered something like this?
Chris
--
Chris Friesen
Software Developer
GENBAND
chris.friesen@genband•com
www.genband.com
next reply other threads:[~2011-02-18 17:56 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-02-18 17:55 Chris Friesen [this message]
2011-02-20 19:20 ` how to listen() on single IP address but very many ports? Eric Dumazet
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=4D5EB2AE.5050703@genband.com \
--to=chris.friesen@genband$(echo .)com \
--cc=netdev@vger$(echo .)kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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