Why Networking Fundamentals Matter

A handful of courses on this site have quietly assumed something no course ever actually taught: that you already know what an IP address, a port, or a routing table is. This chapter names that gap directly — and previews the journey the rest of this course is going to explain, piece by piece.

The Gap This Course Fills

A few concrete examples, not a vague complaint:

• ssh1's own "How SSH Works" chapter talks about connecting to a "host" over a "port" without ever explaining what a port actually is, or how a connection gets established in the first place.
• https1 walks through the TLS handshake in detail, but that handshake rides on top of a plainer, older handshake — TCP's own — that's never explained anywhere on this site.
• vpn1 talks about routing traffic through a tunnel, assuming the reader already knows what routing does under normal, non-VPN conditions.
• host1 covers managing DNS records at a registrar and at Cloudflare, without ever explaining what actually happens, step by step, when a browser resolves a domain name into an address.
• cloud1-5's own Networking Fundamentals chapter covers VPCs, subnets, and security groups, assuming subnetting and routing were already understood coming in.

None of those courses were wrong to skip this — they each had their own scope. This course exists specifically to retroactively supply the foundation every one of them quietly assumed.

A First Preview — What Actually Happens When You Load a Webpage

A short, deliberately light preview — every term here gets its own full chapter later, so don't worry about fully understanding any of it yet. Typing a URL and hitting enter sets off: a DNS lookup (turning a name into an address), routing across a chain of networks your computer has never directly touched, a TCP handshake (a short back-and-forth that establishes a reliable connection), and finally an actual HTTP request and response carrying the page itself.

Chapters 2 through 10 unpack every one of those terms in full. The capstone, net1-11, walks through this exact same journey again — this time with nothing left unexplained.

The Two Models You'll See Everywhere — OSI and TCP/IP

Networking is almost always explained in "layers" — a way of separating concerns so a web developer never has to think about electrical signals on a cable, and an electrical engineer never has to think about HTTP headers. Two models describe those layers: OSI, a seven-layer conceptual reference model still used as shared vocabulary, and TCP/IP, the leaner four-or-five-layer model that describes what's actually running on real networks. net1-2 covers OSI; net1-3 covers TCP/IP and maps the two together.

Why "It Just Works" Usually Hides Real Complexity

This isn't just academic. When something breaks — a site won't load, an SSH connection times out, a VPN refuses to connect — knowing which layer the problem most likely lives in (DNS? routing? the application itself?) is what separates a systematic diagnosis from random guessing. net1-10's own diagnostic tools, and cloud2-2's own connectivity-diagnosis material, both lean directly on the foundation this course builds.

Hands-On Exercises