OSI layers, subnets, DNS, TCP/UDP, firewalls
Practise these as flashcards. One or two lines each; the ones you miss come back first.
Start freeTCP is connection-based, ordered and retransmits lost packets: HTTP, SSH, databases. UDP is fire-and-forget with less overhead: DNS, NTP, video and voice.
The browser resolves the name through DNS, opens a TCP connection, does a TLS handshake for HTTPS, and sends the HTTP request. It usually hits a load balancer, which forwards to a backend server. The response comes back and the browser renders it.
The router a machine sends traffic to when the destination isn't on its own subnet. A wrong gateway means you can reach local machines but nothing beyond.
22 SSH, 53 DNS, 80 HTTP, 443 HTTPS, 3389 RDP, 389/636 LDAP/LDAPS, 445 SMB, 1433 SQL Server, 3306 MySQL, 5432 PostgreSQL, 6443 Kubernetes API.
64 addresses, 62 usable (minus network and broadcast).
Client sends SYN, server answers SYN-ACK, client sends ACK; the connection is established. If the SYN gets no answer, something dropped it (timeout). If it gets a RST, the host was reached but nothing is listening or it was rejected (refused).
Finds the MAC address for an IP on the local subnet so the frame can be delivered. For remote destinations the host ARPs for its default gateway. ip neigh or arp -a shows the cache.
A forward proxy acts for clients going out (corporate web proxy, filtering, caching). A reverse proxy acts for servers, receiving incoming traffic and passing it to backends (Nginx, F5, App Gateway).
A logical network segment on a switch. Devices in different VLANs need a router or Layer 3 switch to talk. Trunk ports carry several VLANs using 802.1Q tags.
Network Address Translation rewrites addresses at the edge. Source NAT lets private hosts reach the internet through one public IP. Destination NAT (port forwarding) sends inbound traffic to an internal server.
The network path is fine. Something is blocking or not listening on that port: a firewall or security group, or the app isn't running or is bound to localhost. Check with nc -zv from the client and ss -tlnp on the server.
The largest packet size, usually 1500 bytes. A mismatch, common over VPNs and tunnels, makes small requests work while large transfers hang. Test with ping -M do -s 1472 host.