2.4. Ports, Protocols, and Traffic Types

💡 First Principle: IP addresses identify devices, but port numbers identify services on those devices. A single server can run web (80), email (25), and DNS (53) services simultaneously because each listens on a different port. The combination of IP + port creates a unique endpoint (socket).

What breaks without port knowledge? Firewalls filter by port. If you don't know HTTPS uses 443 and HTTP uses 80, you can't troubleshoot why secure connections fail while insecure ones work. If you don't know DNS uses 53, you can't diagnose name resolution failures through a firewall.

Think of ports like apartment numbers in a building. The IP address delivers the packet to the building (server); the port number delivers it to the right apartment (service).