Explore a fictional school network, then investigate hardware, IPv4/MAC addresses, IPv6 notation, DNS and application protocols. This is an offline teaching model: no requests, lookups, scans or network settings changes are performed on your computer.
Basic and Advanced
Basic focuses on hardware roles, local versus remote traffic, address formats and protocol purposes. Advanced adds /8–/30 subnet calculations, detailed ports and TTLs, ARP/switch tables and the four-layer TCP/IP model. Subnet arithmetic and detailed layer names extend beyond the GCSE requirements. The activities support parts of OCR J277 1.3 and H446 1.3.3; they do not claim complete specification coverage.
One page, four workspaces
Use controls on the left, a diagram or workbench in the centre and an inspector or journey on the right. Step, play, rewind or jump to the result. Focus Mode hides the site header; Escape exits it. Panels scroll internally on smaller desktop screens; mobile panels stack.
Follow the addresses
IP identifies the logical endpoint and network. MAC addresses serve individual local links. A remote packet keeps its destination IP but its first local frame targets the gateway MAC. ARP requests are LAN broadcasts and contain address information in their payload; they have no IP header. The switch learns source MAC-to-port mappings. Routers replace link frames and decrement IP TTL; WAN link headers are deliberately omitted.
DNS, cache and time
The client asks its recursive resolver, which follows root/TLD/authoritative referrals on its behalf. The root does not know every website IP. A current cached answer can be used while DNS is offline. Expired answers are refreshed; an authoritative change does not immediately erase unexpired copies. Each event advances the model clock by one second, not a real latency. New request carries forward the cache visible at the selected step; ARP and switch learning restart for each teaching run. +60s and Flush also restart the request.
Protocols, encryption and limits
HTTP and HTTPS retrieve web content; HTTPS adds TLS server authentication and encryption in transit. Encryption does not hide IP addresses or guarantee a site is trustworthy. The client application knows its own content; the observed encrypted wire data is shown as opaque bytes. This TLS animation does not perform cryptography. SMTP submits/sends email, IMAP accesses and synchronises server mail, and POP3 retrieves/downloads mail with deletion/retention controlled by client settings. FTP is shown through its control connection only.
The model uses TCP for these application services, UDP 53 for its DNS example and a simplified TCP handshake. It omits DNS-over-TCP fallback, encrypted DNS, negative/resolver caching, DNSSEC, packet loss/retries, NAT, IPv6 routing and the WAN’s internal routers. Names use the reserved .example domain and IP addresses use documentation ranges. The .example DNS hierarchy is fictional. The fixed layout demonstrates client-server and a star LAN; the hardware inspector explains peer-to-peer and connection trade-offs.
For packet switching, routing around faults and retransmission, open PacketLab.
24 PRIMM activities and saving
Check a prediction before tracing or repairing. Work through any challenge independently, reattempt, or modify it in Explore. Help marks a helped completion while retaining a previous independent best. Files and practice are device-local, separate from course XP and student/teacher dashboards. Imported files are validated before replacing the current model.
Teacher reference answers · all 24 activities
1. Find the switchPrediction: MAC addresses. Answer: switch.
Investigate the central switch and its learning table.
2. Cross the boundaryPrediction: Its default gateway. Answer: router.
The school router connects this LAN to the WAN. Switches forward within the LAN.
3. The wireless bridgePrediction: Wireless devices to the LAN. Answer: ap.
The access point bridges the wireless client into the wired LAN; it is not the same job as routing.
4. Keep local work localPrediction: Travel to another IP network. Answer: yes.
The cache avoids the remote DNS lookup. Client → switch → local server stays within the LAN.
5. Repair the centrePrediction: Traffic through the centre. Answer: Turn the switch on..
Turn the Switch control on. This topology relies on the central switch.
6. Restore the WANPrediction: Networks over a wider geographical area. Answer: Set the broken connection to None..
Choose None in Broken connection. The rest of this network is already working.
7. Recognise a local destinationPrediction: Four decimal octets, each 0–255. Answer: yes.
Both are in 192.0.2.0/24. Compare the network portion, not just the last octet.
8. Choose the next-hop IPPrediction: The gateway interface. Answer: 192.0.2.1.
The IP packet is for 198.51.100.20, but the local next hop is gateway 192.0.2.1.
9. Address the first local framePrediction: A link-layer interface. Answer: 02:00:00:00:01:01.
It is the school gateway MAC, not the remote server MAC. Inspect the local-link event.
10. Keep the destination IPPrediction: Changes link MAC addresses but keeps the end-to-end IP endpoints. Answer: 198.51.100.20.
Each link has local MAC addresses. The application packet still targets 198.51.100.20.
11. Expand IPv6Prediction: 128 bits. Answer: 2001:0db8:0000:0000:0000:0000:0000:0001.
:: replaces consecutive zero groups. Each full group has four hexadecimal digits.
12. Find the network portionPrediction: 26 network bits. Answer: 192.0.2.0.
A /26 has blocks of 64 addresses. .10 is in the .0–.63 block. Subnet calculations are an Advanced extension.
13. Ask the resolverPrediction: Its recursive resolver. Answer: 203.0.113.53.
The resolver follows referrals on the client’s behalf. Its address is 203.0.113.53.
14. A cache can keep workingPrediction: Can be reused until it expires. Answer: yes.
The client can use its current cached address and still contact the online application server.
15. Read the TTLPrediction: How long an answer may be reused from cache. Answer: 60.
90 minus 30 is 60. Each trace event advances this teaching clock by one second; it is not real network latency.
16. Restore the missing recordPrediction: The record held for the requested name. Answer: Set the DNS A record to 198.51.100.20..
The chosen server is at 198.51.100.20. A missing name cannot create a positive address cache entry.
17. Flush an old cached answerPrediction: Does not instantly invalidate every unexpired cached copy. Answer: Flush DNS cache, or advance time beyond its expiry..
The cache is used before the resolver is asked. A fresh lookup will return .20 after the old copy is removed or expires.
18. Allow name resolutionPrediction: Policy rules, such as a destination port. Answer: Set the firewall policy to Allow..
This model’s DNS query uses UDP port 53. It deliberately omits DNS-over-TCP fallback.
19. Protect the web contentPrediction: Encryption and server authentication through TLS. Answer: Choose HTTPS..
HTTPS uses TLS before exchanging HTTP data. IP addresses and TCP ports remain visible.
20. Send outgoing mailPrediction: SMTP. Answer: Choose SMTP..
SMTP sends/submits mail. IMAP and POP3 retrieve/access mail.
21. Synchronise the inboxPrediction: Access and synchronise mail held on the server. Answer: Choose IMAP..
POP3 retrieves/downloads messages; deletion or retention of server copies depends on client settings.
22. Rebuild the stackPrediction: Develop and change in separate responsibilities. Answer: Application → Transport → Internet → Link..
The application message enters transport, then IP, then the local link frame. A real operating system builds this stack for you.
23. Place IP in its layerPrediction: IP addressing and forwarding between networks. Answer: internet.
Application handles service data; Transport handles end-to-end delivery; Internet handles IP; Link handles local frames.
24. DNS worked, but the service did notPrediction: That an address was obtained, not that the application is available. Answer: Set the firewall policy to Allow..
A DNS answer and an application connection are separate steps. Allow the selected application port.
OCR GCSE specification · OCR A-level specification · DNS reference