Can TCP and UDP Bind to the Same Port Simultaneously? A Deep Dive into Port Management

Can TCP and UDP Bind to the Same Port Simultaneously?

Although the interview question is often phrased as “listen”, the correct term is “bind”. UDP does not have a listen() call; both TCP and UDP servers use bind() to associate a socket with a port.

In the transport layer, ports distinguish different applications on the same host. TCP and UDP are implemented as independent kernel modules, each with its own protocol number in the IP header, so the same numeric port can exist in both modules without conflict.

Answer: Yes, TCP and UDP can bind to the same port number.

Multiple TCP Services on the Same Port

If two TCP processes bind to the identical IP address and port, bind() fails with “Address already in use”. However, if the IP addresses differ (e.g., one binds to 0.0.0.0:8888 and the other to 192.168.1.100:8888), the bind succeeds because the address‑port pair is unique.

When a TCP server restarts, lingering connections in TIME_WAIT hold the same IP‑port tuple, causing the same error. Setting the socket option SO_REUSEADDR before bind() allows the new process to reuse the address even if a TIME_WAIT socket exists.

int on = 1;
setsockopt(listenfd, SOL_SOCKET, SO_REUSEADDR, &on, sizeof(on));

Can Client Ports Be Reused?

When a client calls connect(), the kernel picks a source port from the range defined by net.ipv4.ip_local_port_range (default 32768‑61000). The four‑tuple (source IP, source port, destination IP, destination port) uniquely identifies a TCP connection, so the same source port can be reused for connections to different destination addresses or ports.

Binding a client socket manually with bind() works only if the IP‑port pair does not already exist; otherwise, bind() fails with “Address already in use”.

TIME_WAIT Exhaustion on the Client Side

If many client connections to the same server remain in TIME_WAIT, the available source ports may be exhausted, preventing new connections to that server. Connections to different servers are unaffected because the destination differs.

Enabling the kernel parameter net.ipv4.tcp_tw_reuse allows the kernel to reuse a TIME_WAIT socket after a short delay (≈1 s), mitigating port exhaustion:

# sysctl -w net.ipv4.tcp_tw_reuse=1

Summary

TCP and UDP can bind to the same numeric port because they are separate protocol modules.

Two TCP processes can bind to the same port only if their IP addresses differ; otherwise, bind() fails.

Use SO_REUSEADDR on the server side to avoid “Address already in use” after a restart.

Client source ports are chosen from net.ipv4.ip_local_port_range and can be reused for connections to different destinations.

Excessive TIME_WAIT connections to a single server can exhaust ports; enable net.ipv4.tcp_tw_reuse to reuse them.