What actually happens between tapping a link and the page loading. The whole story in one chapter, before we break it apart.
Networking is about getting data from one device to another. A network consists of devices (phones, laptops, servers), connections (cables, Wi-Fi), and protocols (rules for how they talk). The internet is not one network — it's millions of networks connected together. Your device doesn't know how the packet gets there; it just trusts the layers underneath to figure it out. That's the whole abstraction.
1.1 What Is a Network, Really?
A network is two or more devices that can send data to each other. That's it. Your phone and your Wi-Fi speaker = a network. All the computers in your school = a network. Every connected device on Earth = a network of networks, which is what we call "the internet."
There are three ingredients in every network:
Devices — things that send or receive data (phones, laptops, servers, smart TVs, printers)
Connections — the physical path between them (ethernet cables, fibre optics, Wi-Fi radio, 5G)
Protocols — the rules both sides follow so they can understand each other
All three have to be there. A phone and a speaker that can't physically reach each other aren't a network. Two devices on the same cable that speak different languages aren't a network either.
1.2 Why Networks Exist
This seems obvious, but articulating it helps. Networks exist because sharing is more efficient than duplicating.
Without a network...
With a network...
Every document lives on one computer
Documents are centralised; anyone authorised can access them
Every computer needs its own printer
One printer serves the whole office
Information can only be shared by physical transfer (USB, paper)
Information moves in milliseconds to anyone, anywhere
Remote collaboration is impossible
Teams on different continents work on the same project in real-time
The modern world runs on networks. Your school's attendance system, the Eftpos machine at the shops, Uber, Netflix, your online exam portal, the traffic lights — all networked. When networking breaks, modern life grinds to a halt. This is why security matters so much.
1.3 The Journey of a Click — A Story
Let's follow what actually happens when you open Instagram on your phone at home. This is a high-level tour. Every chapter that follows zooms into one step.
Many milestones. ~300ms total on a decent connection. Each arrow hides layers of protocols, encryption, and routing decisions.
The 12 steps in plain English
Tap. Your phone app decides it needs fresh content from Instagram's servers.
DNS lookup. Your phone needs Instagram's IP address. It asks your Wi-Fi router, which asks your ISP's DNS resolver, which (if nothing is cached) walks the DNS tree to find Instagram's authoritative server. Answer comes back: 157.240.7.174.
TCP handshake. Phone opens a connection to that IP. Three quick packets — SYN, SYN-ACK, ACK — set up a reliable channel.
TLS handshake. Since Instagram uses HTTPS, phone and server negotiate an encryption key. After this, all traffic between them is scrambled.
HTTP request. Phone sends "GET /my-feed" over the encrypted channel.
Wi-Fi hop. The packet travels from your phone's Wi-Fi radio to your router via radio waves.
NAT rewrite. Your router rewrites the source address from your phone's private IP to your public IP, notes the translation in its table, and forwards.
ISP routing. Your ISP's routers forward the packet toward Instagram's network. Each router looks at the destination IP and picks the best next hop.
Global hops. The packet may travel through submarine cables and 10+ routers across continents.
Instagram's server. A web server receives the request, consults databases, builds your feed, and sends back an HTTP response.
Return journey. The response follows essentially the same path in reverse.
Render. Your browser/app parses the HTML, downloads images (each via the same process!), and displays the feed.
This all happens in roughly 300 milliseconds. When it feels slow, something in this chain is slow: DNS, a distant server, a congested network, or your own Wi-Fi.
THIS IS WHAT THE REST OF THE GUIDE EXPLAINS. Every step above gets its own deep dive somewhere. Chapter 4 (OSI/TCP-IP) explains the layered wrapping. Chapter 5 explains the IP addressing. Chapter 6 explains HTTP, DNS, TCP. Chapter 12 explains the TLS handshake. Chapter 7 explains the Wi-Fi step. If you understand the 12 steps above, you understand the backbone of this entire subject.
1.4 The Two Sides of Networking
The course is organised in two halves. The split is important because the same concepts keep coming back from different angles.
Then a third part ties them together: how we defend (Chapters 12–16). The logic is: you can't defend a system you don't understand, and you can't understand what needs defending without knowing how attacks work. That's why the course runs in this order.
THE BIG TAKEAWAY: Security is never an add-on. It's a property that emerges from how the whole system is designed. If you build a house with no locks on any doors, adding an alarm later is pointless. Networks are the same — bolt-on security is weak security. This is called defence in depth and it's a principle you'll see repeated throughout the course.
1.5 Two Recurring Themes
Theme 1: Layering makes networks scale
You don't need to know how Wi-Fi radios work to use Instagram. Instagram's developers don't need to know how undersea cables work. Your ISP doesn't need to know what HTTPS is to forward packets. Every layer trusts the layers below to do their job.
This is how a system built by millions of people, using thousands of different technologies, still works together coherently. Each layer has a defined interface to the layer above and below. As long as the interface is honoured, the internals can change freely.
Theme 2: Every defence has a trade-off
More security usually means more friction, more complexity, more cost, or slower performance. Good design isn't "maximum security." It's right-sized security for the context — enough protection for the actual risk, without crippling the thing you're trying to protect.
Examples you'll meet:
MFA is more secure than a password alone — but slightly slows every login
VPNs protect traffic — but add latency
Network segmentation contains breaches — but complicates configuration
Frequent password rotation was standard advice — but caused users to write passwords on sticky notes. Modern advice is long passphrases + MFA, not rotation.
The point: security isn't a scale from 0 to 100 where you want 100. It's a set of engineering trade-offs where the right answer depends on what you're protecting from what.
1.6 How to Study This Course
Some concrete advice for the year ahead:
Understand, don't memorise. Students who try to memorise the OSI model's 7 layers as a list struggle. Students who understand what each layer does can derive the list any time. The worked examples in this guide are designed for this.
Do the practical bits. Run the ping, tracert, nslookup commands mentioned in the "Try it" boxes. Concepts stick after you see them happen.
Follow the news. Major breaches happen weekly. Every breach is a practical case study. Optus, Medibank, Latitude, the Port of Melbourne — real incidents teach more than textbook examples.
Practice the mark-scoring templates. Chapter 19 walks through them. ATAR exams reward structured answers more than raw knowledge. A good structure turns a B answer into an A.
Use the "Top Traps" on the index page. The traps are recurring student mistakes — if you can recite why each one is wrong, you've avoided the main ways to lose easy marks.
ONE MENTAL HABIT TO BUILD: When you hear about any attack, breach, or piece of technology in the news, pause and ask: "Which layer? Which CIA pillar? What defence would have stopped this?" Chapter 8 gives you the frameworks to answer these questions. By the end of the course, you should do this automatically. That's the skill examiners are testing.
1.7 What's Next
From here:
Chapter 2 covers network types and topologies — LANs, WANs, star vs mesh, client-server vs peer-to-peer
Chapter 3 covers the physical hardware — what routers, switches, access points actually do
Chapter 4 is the big conceptual chapter — the OSI and TCP/IP models, the backbone of networking
After that the course alternates between deeper networking (5-7) and then pivots into security (8 onwards). Take your time with Chapter 4; it's the foundation everything else builds on.