Why 65535 Is Not the Real TCP Connection Limit – Understanding Server Capacity

First, the 65535 connections mentioned in the question refer to the limit on client‑side TCP connections.

How a TCP Connection Is Identified

The system uses a four‑tuple {local IP, local port, remote IP, remote port} to uniquely identify a TCP connection.

Maximum Client TCP Connections

When a client initiates a TCP connection, the OS selects an unused local port (unsigned short, 0‑65535). Port 0 is reserved, leaving 65535 usable ports, so a pure client can have at most 65535 simultaneous connections to different servers.

Theoretical Server TCP Connections

A server listens on a fixed local port. Ignoring address reuse, the variable parts of the four‑tuple are the remote IP and remote port. For IPv4 this yields 2³² (IP addresses) × 2¹⁶ (ports) ≈ 2⁴⁸ possible concurrent connections.

Practical Limits

In real environments the number of concurrent TCP connections is limited by memory and the maximum number of file descriptors, not by the port count. By increasing memory and raising the file‑descriptor limit, a single Linux server can handle well over 100 000, even millions, of concurrent connections.

Port Reuse and Socket Basics

Even with a single listening port, many connections can share it because each connection is distinguished by the unique combination of source and destination IP/port (and protocol for TCP/UDP). A socket abstracts this process, allowing multiple connections over the same port.

Four‑Tuple Example

Host IP 1.1.1.1 listening on port 8080 receives a connection from 2.2.2.2:5555, forming the tuple (1.1.1.1,8080,2.2.2.2,5555). A second connection from 2.2.2.2:6666 creates (1.1.1.1,8080,2.2.2.2,6666). A third request from 2.2.2.2:5555 cannot be distinguished and would be rejected.

Five‑Tuple for TCP/UDP

When protocol is considered, the identifier becomes a five‑tuple: source IP, source port, destination IP, destination port, protocol type.

Conclusion

The 65535 figure is simply the number of usable TCP ports on a Linux system; it does not cap the number of concurrent connections a server can handle. Real limits are dictated by hardware resources, memory, and file‑descriptor settings, and with proper tuning a server can support far more than 65 535 connections.