1. List UDP sockets
ss -uan lists UDP sockets (-u) with numeric addresses (-n) in all states (-a).
ss -uanTyporithm · medium
Step 1 of 8 · intro card
L4 — Transport Layer
UDP is connectionless — no handshake, acknowledgements, or ordering — so it is lightweight and low-latency. It underpins DNS, DHCP, QUIC/HTTP3, and real-time media. Ports (0–65535) identify the service on a host, with well-known ports below 1024. ss -uan lists UDP sockets.
UDP trades reliability for speed. There is no handshake, no acknowledgements, and no ordering guarantee — a datagram is sent and may arrive, arrive out of order, or be lost. That minimalism makes it lightweight and very low-latency.
Because it is so cheap, UDP underpins services where a tiny round trip matters: DNS lookups, DHCP, QUIC and HTTP/3, and real-time audio and video. Applications that need reliability build it on top of UDP themselves, as QUIC does.
Ports identify which service on a host a packet is for. The 16-bit port space runs 0–65535, with well-known ports below 1024 (such as 53 for DNS) reserved for standard services. ss -uan lists the UDP sockets currently bound on the machine.
UDP is connectionless: no handshake, no ACK, no ordering.
It powers DNS, DHCP, QUIC/HTTP3, and real-time media.
Ports run 0–65535; well-known ports are below 1024.
ss -uan
nc -u -v 8.8.8.8 53
# UDP: connectionless, no ACK, no ordering
dig @8.8.8.8 example.com
iperf3 -u -c hostConnect each part of the code to the concept before you type.
ss -uan lists UDP sockets (-u) with numeric addresses (-n) in all states (-a).
ss -uannc -u sends UDP datagrams; here to port 53, the DNS port, with no handshake first.
nc -u -v 8.8.8.8 53UDP sends datagrams with no connection, no acknowledgements, and no guaranteed ordering.
# UDP: connectionless, no ACK, no orderingdig queries a DNS server (port 53), the classic UDP-based service.
dig @8.8.8.8 example.comiperf3 -u runs a UDP throughput test, useful for measuring loss and jitter on a path.
iperf3 -u -c hostRead the concept map and follow the code breakdown.
Type the implementation, repair mistakes and work through every recall exercise.
Use the final check without hints; revisit weak concepts in short practice sessions.