Are there applications where the number of network ports is not enough?

In TCP/IP, the port number is specified by a 16-bit field, yielding a total of 65536 port numbers. However, the lower range (don't really know how far it goes) is reserved for the system and cannot be utilized by the application. Assuming that 60,000 port numbers are available, it should be more than plenty for most nework application. However, MMORPG games often have tens of thousand开发者_StackOverflow中文版s of concurrently connected users at a time.

This got me wondering: Are there situations where a network application can run out of ports? How can this limitation be worked around?

---

You don't need one port per connection.

A connection is uniquely identified by a tuple of (host address, host port, remote address, remote port). It's likely your host IP address is the same for each connection, but you can still service 100,000 clients on a single machine with just one port. (In theory: you'll run into problems, unrelated to ports, before that.)

---

The canonical starter resource for this problem is Dan Kegels C10K page from 1999.

The lower range you refer to is probably the range below 1024 on most Unix like systems. This range is reserved for privileged applications. An application running as a normal user can not start listening to ports below 1024.

An upper range is often used by the OS for return ports and NAT when creating connections.

In short, because of how TCP works, ports can run out if a lot of connections are made and then closed. The limitation can be mitigated to some extent by using long-lived connections, one for each client.

In HTTP, this means using HTTP 1.1 and keep-alive.

---

There are 2^16 = 65536 per IP address. In other words, for a computer with one Ip address to run out of ports it should use more than 65536 ports which will never happen naturally!

You have to understand a socket which is (IP+Port) and the end to end device for communication

IPv4 is 32 bit let's say somehow it can address around 2^32 computers publicly (regardless of NATing). so now there are 2^16*2^32 = 2^48 public sockets possible (which is in the order of 10^15) so it will not have a conflict (again regardless of NATing).

However IPv6 is introduced to allow more public IPs