Branch WAN topology
A branch reaches the internet and headquarters through an edge router and firewall.
Appears in:/networking/site-to-site-vpn
Interactive library
Browse every diagram in the library, then open one to zoom, pan, step through the protocol flow and inspect each device. Diagrams are also embedded in the relevant lessons.
67 diagrams
A branch reaches the internet and headquarters through an edge router and firewall.
Appears in:/networking/site-to-site-vpn
A shared backbone carries every transmission; all stations hear all traffic.
Clients request services; a centralised server holds the data and the logic.
Distribution and core are merged for smaller sites that do not need three tiers.
Every site connects to every other site: maximum resilience at maximum cost.
All branch traffic goes through a central hub; spokes never talk directly.
On-premises systems connect to cloud VPCs over a private interconnect or VPN.
Appears in:/cloud-platforms/aws
Only the links that matter for traffic and resilience are built.
Nodes act as both client and server, sharing resources without a central authority.
The simplest possible network: exactly two endpoints joined by one dedicated link.
Appears in:/networking/tcp-ip
Each node links to two neighbours, forming a closed loop that can survive one break.
Every leaf connects to every spine, giving predictable latency and easy scale-out.
Appears in:/networking/routing
Every device connects to one central switch, which forwards frames between the spokes.
Appears in:/networking/ip-addressing
Core, distribution and access tiers, each with a clear job.
Stations associate with an access point, which bridges them onto the wired LAN.
Appears in:/networking/tcp-ip
Compare the seven-layer OSI reference model with the four-layer TCP/IP model and see how their responsibilities map.
Appears in:/networking/tcp-ip
A host broadcasts an ARP request on its subnet, receives a unicast reply, then addresses its frame to the default gateway for an off-subnet destination.
A client with no address broadcasts DISCOVER, receives OFFER, sends REQUEST and is confirmed with ACK.
Appears in:/networking/dhcp/networking/ip-addressing
A stub resolver asks a recursive resolver, which walks the root, TLD and authoritative servers and then caches the answer.
Appears in:/networking/dns/networking/tcp-ip
One packet travels from a client through a switch, a router and the internet to a server, gaining and losing a header at every hop.
Appears in:/networking/tcp-ip/networking/ethernet
A connection is opened with SYN, SYN-ACK and ACK, then closed with a four-way FIN and ACK exchange.
Appears in:/networking/tcp-ip/networking/firewalls
Two autonomous systems peer with eBGP while each AS distributes the learned prefixes internally with iBGP, and path attributes decide the best path.
A gateway translates many private hosts to a single public address, using unique source ports to keep the sessions apart.
Appears in:/networking/nat/networking/ip-addressing
Three routers in one OSPF area exchange hello, DBD, LSR and LSU messages until they share the same link-state database and agree on the shortest paths.
Appears in:/networking/routing/networking/ip-addressing
A router compares a packet destination against its route table, picks the longest matching prefix and forwards to that route next hop.
Appears in:/networking/routing/networking/ip-addressing
A single switch carries VLAN 10 and VLAN 20, each an isolated broadcast domain, joined only by a router-on-a-stick.
Appears in:/networking/ip-addressing/networking/routing
Two switches joined by an 802.1Q trunk that carries VLAN 10, VLAN 20 and the native VLAN as tagged or untagged frames.
Appears in:/networking/ip-addressing/networking/tcp-ip
Follow CPU and memory allocation from one physical host to several VMs, including the need to leave capacity headroom.
Appears in:/virtualization/virtualization/vm
Trace an image from build and registry to a running container, then follow a published port and persistent volume.
Appears in:/virtualization/virtualization/docker
See how a guest OS uses virtual CPU, memory, disk, and network devices that the hypervisor maps onto a physical host.
Appears in:/virtualization/virtualization/vm
Compare a short-term VM checkpoint with a separate clone and an independently stored backup.
Appears in:/virtualization/virtualization/vm
Switch between a server hypervisor layer on hardware and a desktop hypervisor running as an application on a host OS.
Appears in:/virtualization/virtualization/vm
Compare a VM with its own guest OS and kernel against containers that isolate processes while sharing the host kernel.
Appears in:/virtualization/virtualization/vm/virtualization/docker
Switch between NAT, bridged, host-only, and internal networking to compare which systems can communicate.
Appears in:/virtualization/virtualization/vm
Compare Kubernetes worker nodes backed by VMs with worker nodes running on physical servers.
Appears in:/virtualization/virtualization/kubernetes
Follow an explicitly authorized user through identity checks, a policy enforcement point and an isolated application segment.
Appears in:/networking/site-to-site-vpn
Edit a small local rule set and see which first matching rule handles a documentation-only test flow.
Appears in:/networking/site-to-site-vpn
Switch between a gateway-to-gateway site tunnel and a remote user tunnel; both protect transport but still rely on routing and access policy.
Appears in:/networking/site-to-site-vpn
Trace a typical access path from the provider fiber handoff through an ONT, gateway and switch to a wired endpoint.
Appears in:/networking/tcp-ip
A mobile client moves from one managed access point to another while its network policy and IP subnet remain consistent.
Appears in:/networking/tcp-ip
A row of racks whose top-of-rack switches serve the servers and dual-home to an aggregation pair on two separate power feeds.
Appears in:/networking/routing/networking/ip-addressing
Use a layered diagnostic path to separate client configuration, local reachability, resolver health and upstream name resolution.
Appears in:/networking/dns
How much annual availability each link and the scheduled maintenance windows contributed.
Average bandwidth in Mbps broken down by protocol across eight three-hour segments of a day.
Appears in:/networking/tcp-ip/networking/ip-addressing
Seconds for IPv4 and IPv6 unicast routing to converge after each topology change.
Appears in:/networking/routing/networking/tcp-ip
Monthly east-west traffic between servers compared with north-south traffic entering and leaving the data centre.
Appears in:/networking/routing/networking/tcp-ip
Millisecond timeline of one DHCP lease, from the DISCOVER broadcast to the address conflict probe.
Appears in:/networking/dhcp/networking/ip-addressing
Median name resolution latency for cached, recursive and authoritative lookups.
Appears in:/networking/dns
How many packets matched each firewall rule over a 24-hour window, listed in rule evaluation order.
Appears in:/networking/routing/networking/tcp-ip
Weekly mix of intrusion detection alerts grouped by severity, each week normalised to 100 percent.
Appears in:/monitoring/prometheus/networking/tcp-ip
How long each incident response phase took, from detection through triage, containment, eradication and recovery.
Throughput in Mbps for the same traffic profile with and without IPsec ESP overhead.
Five-number summary of packet delay variation for each QoS traffic class.
Appears in:/networking/qos/networking/troubleshooting
How a 4000-byte payload becomes three IP fragments on a 1500-byte MTU link, and the header overhead added.
Appears in:/networking/ip-addressing/networking/tcp-ip
Share of the NAT translation table in use on an example edge router at the peak hour.
Appears in:/networking/nat
Bytes of header, trailer and payload that each layer adds around a 1,000-byte application payload.
Appears in:/networking/tcp-ip/networking/ethernet
Configured OSPF cost per link and the cost seen after traffic fails over to an alternate path.
Appears in:/networking/routing
Measured packet loss percentage on each segment of a path from an access switch to a remote host.
Appears in:/networking/troubleshooting/networking/wan
Power draw in watts plotted against rack utilisation percentage for compute and storage racks.
Appears in:/monitoring/prometheus/virtualization/vm
Histogram of forty round-trip time samples collected during a single measurement window.
How the prefixes in an example edge router table are learned.
Appears in:/networking/routing
Elapsed milliseconds for each phase of one TCP connection, from the initial SYN to the closing FIN.
Appears in:/networking/tcp-ip
Transport header size and total per-packet overhead on the wire for TCP, UDP and QUIC.
Appears in:/networking/tcp-ip
Inbound and outbound utilisation of an example 1 Gbps WAN uplink, sampled once per hour.
Appears in:/networking/routing
How many usable IPv4 host addresses each prefix length from /24 to /31 provides.
Appears in:/networking/ip-addressing
Normalised signal quality scores for RSSI, SNR, retries, throughput and co-channel interference at each location.
Appears in:/networking/tcp-ip
Airtime utilisation per Wi-Fi channel and radio band, showing which channels are congested.
Appears in:/networking/tcp-ip