Networking Fundamentals — A Systematic Learning Path¶
This site teaches networking concepts in dependency order. Each theory chapter first explains the mechanism on its own: what problem it solves, how it works, which tables or headers it uses, and how to verify it. Short Cloud connection notes show where the same idea appears in modern infrastructure without turning the cloud example into the definition of the concept.
After completing the theory sequence, use the Terraform and GKE networking case study to combine the concepts in one production-style microservices architecture.
The Packet Tracer labs remain separate, deliberately small exercises. They make individual mechanisms observable before cloud abstractions and application components are added.
Recommended theory sequence¶
| Stage | Topic | Why it appears here |
|---|---|---|
| 1 | Networking Models | Establish the vocabulary for every later layer. |
| 2 | Packets & IP Addressing | Explain encapsulation, logical addresses, masks, and basic forwarding. |
| 3 | MAC Addresses & ARP | Show how an IP packet reaches a local next hop. |
| 4 | Switches vs Routers | Separate local Layer 2 forwarding from Layer 3 forwarding between networks. |
| 5 | Private IPs, NAT & PAT | Explain private/public boundaries and translation after routing fundamentals. |
| 6 | Subnetting & DHCP | Design address ranges and automate endpoint configuration. |
| 7 | VLANs | Divide shared switching infrastructure into broadcast domains. |
| 8 | Static Routing, OSPF & BGP | Build and exchange paths across multiple networks. |
| 9 | TCP vs UDP | Add end-to-end transport behavior and application ports. |
| 10 | DNS & Ports | Resolve names and identify services after transport is understood. |
| 11 | HTTP/HTTPS & TLS | Apply transport to web requests, encryption, and identity. |
| 12 | ACLs & Network Segmentation | Convert source, destination, protocol, and port requirements into policy. |
| 13 | Firewalls | Extend filtering into stateful enforcement and security boundaries. |
| 14 | VPNs, Proxies & Load Balancers | Combine secure connectivity, intermediaries, and traffic distribution. |
| 15 | Cloud & Hybrid Networking | Map the completed foundations to distributed cloud services and Terraform. |
| 16 | F5 XC Platform Architecture | Understand the SaaS control plane, Regional Edges, and Customer Edges behind the F5 labs. |
| 17 | F5 XC Site Networking on GCP | Design the two-VPC SLO/SLI boundary and the site registration trust model. |
| 18 | F5 XC Origins, Load Balancing & WAF | Trace a request through DNS, edge policy, the site tunnel, and the private origin. |
Stages 16–18 are an extension track: they explain the platform the F5 Distributed Cloud labs exercise, and assume the Stage 15 cloud model as prerequisite.
Applied case study¶
The Terraform and GKE networking case study uses a three-service application to connect the completed theory:
- Terraform provisions VPC ranges, HA VPN and hybrid routes, Cloud NAT, firewall rules, a private GKE cluster, private DNS, an internal HTTPS load balancer, and privately reachable Apigee API management.
- Kubernetes deploys workloads, Services, ingress configuration, health checks, and NetworkPolicy.
- Two diagrams trace the architecture and the separate connection boundaries.
- Each packet-flow stage links back to the relevant theory chapter.
- A verification matrix and failure walkthroughs turn the architecture into a troubleshooting exercise.
The case study is intentionally last. It demonstrates the concepts; it does not define or replace them.
A companion comparison page, Apigee vs F5 Distributed Cloud, sits between the case study and the F5 track: it contrasts the two front-door platforms, maps which is better under which scenario, and shows the combined edge-plus-governance pattern.
How to study¶
- Read a theory chapter and explain the mechanism without referring to a cloud product.
- Use its Cloud connection note to map—not redefine—the concept.
- Complete a focused exercise from the Lab-Aligned Learning Path.
- After Stage 15, trace the complete case study from DNS through application response.
- For any failure, separate four questions:
- Resolution: Did the name resolve to the intended address?
- Routing: Is there a forward path and a return path?
- Policy: Is the required protocol and port allowed?
- Application: Is a healthy process listening and responding?
Consolidate your knowledge¶
After completing the theory sequence, take the Networking Knowledge Check. The scored multiple-choice quiz provides immediate explanations and links back to each topic for review.