Labs / Protocols
Road 2 of 33
Protocols
The languages machines speak: TCP, UDP and DNS, the web, shells, time, files and mail.
Start this roadPorts, TCP & UDP
The right program, and what a lost packet costs.
- 01 Ports and sockets: one address, many programs One machine, one address, many programs: find out how each request reaches the right one.
- 02 TCP: how a file survives a bad line A radio line loses one packet in five, and the file still arrives whole.
- 03 UDP: why late is worse than lost TCP vs UDP on a bad link: see why losing pictures beats freezing.
Names & errors
DNS names and ICMP errors.
- 01 ICMP: what the network says when delivery fails Read the messages routers send back: unreachable, time exceeded and too big.
- 02 DNS: how a name finds its address, and why changes take time Follow a name down the DNS hierarchy, then watch two resolvers disagree after a move.
- 03 DNS servers: run the zone that answers for your names Edit a zone, run a DNS zone transfer, then forward, filter and encrypt the questions.
The web & remote shells
HTTP, TLS and SSH.
- 01 HTTP: read the requests behind every web page Read HTTP requests line by line, then find the order a redirect lost.
- 02 HTTPS and TLS: lock a site and prove who it is Move a site to HTTPS, read its TLS certificates, and see what still shows.
- 03 WebSockets: keep a connection open for live updates Replace a screen that keeps asking with one the server talks to.
- 04 SSH: log in to a far machine and prove who's who Log in with keys, read a host key warning, and jump through an SSH bastion.
Files, mail & time
FTP, mail and NTP.
- 01 File transfer: why the login works and the list hangs See FTP active/passive modes on the wire, then move files by SFTP and TFTP.
- 02 Email: where a message goes after you press Send See how email works by hand: MX records, SMTP, relays, IMAP and the queue.
- 03 NTP: keep every clock on the network honest See how NTP sets a clock from four timestamps and catches a server that lies.