Port 2592: Netrek — The First Game the Internet Played

Port 2592 is officially registered with IANA for Netrek, assigned on both TCP and UDP. If your port scanner flags it as unassigned, the scanner is wrong.

What Netrek Is

Netrek is a 16-player real-time space combat game, two teams of eight, played entirely over the network. You fly a ship, fight for planets, and coordinate with teammates through live gameplay. It sounds unremarkable now. In 1988, it was astonishing.

There was no World Wide Web. Broadband didn't exist. And yet here was a game where people at universities across the country were piloting spaceships and shooting at each other in real time, over actual network connections, with persistent player accounts and rankings.

Port 2592 is what pickup Netrek servers listen on. It's the standard. If you were connecting to a Netrek server in 1992 or 2002 or today, you pointed your client at port 2592.

The History

Netrek descended from a game called Xtrek, built at UC Berkeley's Experimental Computing Facility in the mid-1980s. Xtrek was tied to X Windows — you needed to be at an X terminal, which meant being physically present at a university workstation.

In 1988-1989, two Berkeley students named Scott Silvey and Kevin Smith changed that. Smith made two architectural decisions that turned a local curiosity into something the Internet could carry:

He split the code into client and server. Instead of the server doing all the rendering, the client handled its own display. This meant network traffic dropped to a manageable trickle — game state, not graphics. Early Internet connections could actually carry it.

He replaced the kill-ratio scoring with something sensible. The previous system rewarded camping. Smith's "Destruction Inflicted" system counted planet taking, bombing runs, and actual strategic contribution. Players stopped playing to pad their stats.

In late 1989, Smith posted the source code to Usenet. No license restrictions, no company, no plan. Just: here's the game, do what you want with it. Servers appeared at universities across the country and then the world. Netrek became what happens when you give the Internet something genuinely fun and get out of the way.

Why It Matters

Netrek was doing things in 1989 that MMO designers would claim to have "invented" a decade later: persistent player accounts, long-term statistics, coordination-dependent team gameplay, client-server separation for bandwidth efficiency.

It also served as a benchmark. Jeff Poskanzer used Netrek traffic patterns when designing early Internet infrastructure. The game was real load — real users, real time, real packets — at a moment when the Internet had almost no real users.

The community that grew around it wrote the book on open-source game development before "open source" was a term anyone used.

What's on Port 2592 Today

Netrek servers still run. The game has a small but committed community that has maintained and updated the codebase for 35+ years. If you connect to an active Netrek server on port 2592, someone might be playing.

The protocol uses a mix of TCP (for reliable game actions) and UDP (for position updates where speed matters more than guaranteed delivery). This hybrid approach — TCP for what must arrive, UDP for what just needs to be fast — became a standard pattern for networked games that followed.

Checking What's on This Port

# See if anything is listening on port 2592 locally
lsof -i :2592

# Or with ss (Linux)
ss -tulpn | grep 2592

# Test a remote host
nc -zv hostname 2592

If you see something on this port locally, it's almost certainly not Netrek — it's more likely custom application software that chose a port that looked unoccupied. That's the practical reality of registered ports: "registered" means IANA noted the assignment, not that anyone enforces exclusivity.

The Registered Port Range

Port 2592 sits in the registered port range (1024–49151). These ports are:

• Above the well-known ports (0–1023), which require root/administrator privileges to bind
• Below the ephemeral/dynamic ports (49152–65535), which the OS assigns automatically for outbound connections
• Available for any application to use without elevated privileges
• Tracked by IANA, but not policed — applications routinely use ports from this range without registering them

When you see an unexpected service on a registered port, the first question isn't "is this a known protocol?" It's "is something local using this for its own purposes?"