What This Port Does
Port 2093 has no standalone IANA assignment, but it isn't idle. It sits at the top of the UDP audio range used by IRLP — the Internet Radio Linking Project — which occupies ports 2074 through 2093 for bidirectional voice traffic.1
When an IRLP node sends or receives audio, it uses a UDP port in this 20-port window. Any of these ports might carry the voice. Port 2093 is simply the ceiling.
What IRLP Is
IRLP is a VoIP system built specifically for amateur radio. It connects radio repeaters — the relay stations ham operators use to extend their range — to each other over the Internet. When two IRLP nodes link, voice picked up by a radio in Vancouver gets encoded, sent over UDP, decoded, and rebroadcast by a radio in Sydney. The people on each end never touch a computer. They key their radios and talk.
Dave Cameron (VE7LTD), a student at the University of British Columbia, installed the first three IRLP nodes in November 1997. After early instability with Windows-based software, he rebuilt the system on Linux in 1998 — and that architecture, built for reliability over a university connection, became the foundation of what IRLP still runs on today.2
The project's motto: "Keeping the Radio in Amateur Radio." IRLP chose UDP because radio voice is real-time audio. A dropped packet is better than a stalled connection. The audio range 2074–2093 gives nodes room to negotiate which port to use for a given connection.
Port Range Context
Port 2093 sits in the registered ports range (1024–49151). These ports aren't reserved like the well-known ports below 1024, but they can be registered with IANA for specific services. IRLP's use of the 2074–2093 window is a practical convention among the amateur radio community rather than a formal IANA assignment for each individual port.
Beyond audio, IRLP also uses TCP ports 15425–15427 for control and update traffic, and port 22 (SSH) for node administration.1
Checking What's on This Port
If you see traffic on port 2093 and you're not running IRLP, check what's listening:
Linux/macOS:
Windows:
If nothing is bound to it but you see inbound traffic, a network scanner or intrusion attempt may be probing the port. Registered ports are common targets for enumeration.
Why Unassigned Ports Matter
The registered range exists precisely for cases like IRLP: protocols that need stable port numbers but don't carry web or email traffic. Without the ability to claim a range, every IRLP node would have to negotiate ports dynamically, and firewalls would have no consistent rule to allow or block them.
Port 2093 being unassigned at the individual level — while functionally occupied by a community convention — is a normal state for thousands of ports in this range. The port space is large enough that informal usage and formal assignment can coexist without collision.
آیا دا پاڼه ګټوره وه؟