What This Port Range Means
Port 10349 lives in the registered ports range (1024-49151). This range is where IANA (Internet Assigned Numbers Authority) allocates port numbers to applications and services that request them formally. When RFC 6335 was written, only about 9% of this vast range was assigned. Port 10349 is in the silence—not officially claimed, not reserved, just waiting.
The port ranges break down like this:
- System Ports (0-1023): Well-known services—SSH, HTTP, HTTPS, DNS, SMTP. These are sacred ground.
- Registered Ports (1024-49151): Applications get here when they ask IANA for their own port. Thousands exist, but thousands remain unassigned.
- Dynamic/Private Ports (49152-65535): Ephemeral. Temporary. Assigned on demand by the operating system.
Port 10349 is officially unassigned. IANA has no record of it. The registry doesn't list it. In the strictest sense, nobody owns it.
What Actually Uses It
vMix Call, a live video and audio broadcasting application, uses port 10349 for TURN/STUN services.1 TURN (Traversal Using Relays around NAT) and STUN (Session Traversal Utilities for NAT) are protocols that help applications punch through firewalls and NATs—the invisible walls that separate networks. When your firewall blocks direct communication, these protocols relay the traffic. They need a port to work. vMix picked 10349.
This is typical. Applications don't wait for formal IANA assignment if they need something. They claim a port in the registered range and document it. Some become conventions. Some become standards. Most exist in a kind of murky middle ground—widely used within their domain, completely unknown elsewhere.
The Honesty About Unassigned Ports
Port 10349 is unassigned, yet something is listening. This is not a bug. This is how the system actually works.
The registered port range is so vast (48,128 ports) and the demand for new ports so modest (perhaps one or two percent ever claimed formally) that most numbers just sit there. Applications assign themselves. Corporations assign themselves. Whoever needs a port and picks a number in the 1024-49151 range—if they document it and stick with it—will probably never have a collision. The odds are too good.
The formal process still exists: you can file an application with IANA, request a port through "Expert Review" or "IESG Approval," and get your official slot in the registry. Some projects do this. Many don't. Why wait?
How to Check What's Listening
If port 10349 is open on your machine and you want to know what owns it:
On Linux or macOS:
This lists all processes using port 10349.
Also on Linux:
The ss command (successor to deprecated netstat) shows TCP/UDP listeners.
On Windows PowerShell:
If nothing is listening, the port is available for whatever needs it next.
Why Unassigned Ports Matter
The unassigned space is where agility lives. Large technology assumes it can grab a port and document it internally, and that's usually true. This decentralized approach allowed the port system to scale beyond what rigid central allocation could do.
But it also means the port landscape is a hybrid—part official structure, part practical chaos. Port 10349 proves it. No RFC defines it. No standards body claims it. Yet it carries real traffic, solving real problems for real applications.
The port table is not a rulebook. It is a historical record of what applications decided they needed and could grab without burning the whole house down.
Esta página foi útil?