Skip to content

1. Networking Ports and Protocols

A protocol is an agreed-upon set of rules for how two devices talk. A port number says which conversation on a device a piece of traffic belongs to — the same way an apartment number tells mail which door to go to inside one building.

Ports worth knowing cold

Port Protocol Use
20/21 FTP File transfer
22 SSH Secure remote shell (how we've been reaching the lab servers all along)
23 Telnet Unencrypted remote shell (how your MUD tile connects)
25 SMTP Sending email
53 DNS Translating names like vhslab.online to IP addresses
67/68 DHCP Automatically assigning IP addresses
80 HTTP Unencrypted web traffic
110 POP3 Retrieving email
143 IMAP Retrieving email (keeps mail on the server)
443 HTTPS Encrypted web traffic
3389 RDP Windows remote desktop

TCP vs. UDP

Almost everything above rides on one of two underlying protocols:

  • TCP confirms every piece of data arrived, resending anything lost. Slower, but reliable — used for web pages, file transfers, email.
  • UDP just sends and doesn't check. Faster, but anything lost is gone — used where speed matters more than perfection, like video calls and online games.

Try it

Without looking it up, guess which protocol (TCP or UDP) a MUD telnet connection probably uses, and why losing a packet of game text would be worse than losing a packet of voice-call audio. Then look up which one Telnet actually uses.

Tip

Port numbers below 1024 are "well-known ports," reserved for standard services like the ones above. Anything your own software picks for itself usually comes from a much higher range.

Play it

Try the Ports and Protocols Lab for hands-on practice matching services to their ports.

Next: IP Addressing →