Computer Networks: A Complete Introductory Course for University Students

A full, from-first-principles introduction to computer networks — every layer of the OSI/TCP-IP stack explained with analogies, worked examples, and diagrams,…

A from-first-principles, layer-by-layer journey through how computers talk to each other — built for university and college students, but useful to anyone starting out in networking or preparing for certification exams (CCNA, Network+, etc.).

Introduction & History
Network Models — OSI and TCP/IP
The Physical Layer
The Data Link Layer
The Network Layer
The Transport Layer
The Application Layer
Network Security
Wireless & Mobile Networking
Network Performance & Troubleshooting
Modern Topics: SDN, Cloud & IoT Networking
Glossary of Key Terms
Further Reading & Next Steps

1. Introduction & History

1.1 What Is a Computer Network?

A computer network is a collection of two or more devices (called nodes or hosts) connected together so they can exchange data. That's it at the core — everything else in this course is about how that exchange happens reliably, efficiently, and securely, across distances ranging from a few centimeters (two chips on a board) to thousands of kilometers (a video call between Nairobi and New York).

Analogy: Think of a network like a postal system. Individual letters (data) need addresses (IP addresses), a way to be physically moved (roads/vehicles = cables/radio waves), sorting facilities (routers), and rules everyone agrees to follow (protocols) so a letter written in Nairobi can be correctly delivered and understood in Tokyo.

1.2 Circuit Switching vs. Packet Switching

Before the internet, telephone networks used circuit switching: when you made a call, a dedicated physical/electrical path was reserved for your conversation for its entire duration — even during silence. This is reliable but wasteful of capacity.

The internet instead uses packet switching:

Aspect	Circuit Switching	Packet Switching
Resource use	Dedicated path reserved for the whole session	Bandwidth shared dynamically
Data unit	Continuous stream	Discrete "packets"
Efficiency	Poor (wastes idle capacity)	High (statistical multiplexing)
Failure handling	Call drops if path breaks	Packets can reroute
Example	Traditional telephone (PSTN)	The Internet

In packet switching, a message is broken into small chunks called packets, each carrying a header with source/destination addresses. Packets from many different conversations share the same links, interleaved, and are reassembled at the destination.

1.3 A Brief History of the Internet

1960s — ARPANET, funded by the U.S. Department of Defense, becomes the first operational packet-switched network, designed partly to survive node failures (a resilience goal, not literally "survive nuclear war" as popular myth suggests).
1970s — Vint Cerf and Bob Kahn design TCP/IP, the protocol suite that still underlies the internet today.
1983 — ARPANET formally switches to TCP/IP — often cited as "the birth of the internet" as we know it.
1989–1991 — Tim Berners-Lee invents the World Wide Web (HTTP, HTML, URLs) at CERN — note the Web is an application that runs on top of the internet, not the internet itself.
1990s–2000s — Commercialization, broadband, and the dot-com boom.
2000s–present — Mobile networking, cloud computing, IPv6 adoption, and software-defined networking transform how networks are built and managed.

Key takeaway: The internet is a network of networks, built on packet switching, and its core protocols (TCP/IP) have remained remarkably stable for over 40 years even as the applications running on top of them have completely changed.

1.4 Types of Networks by Scale

Type	Full Name	Typical Range	Example
PAN	Personal Area Network	A few meters	Bluetooth earbuds to phone
LAN	Local Area Network	A building/campus	Office or home Wi-Fi
MAN	Metropolitan Area Network	A city	City-wide ISP backbone
WAN	Wide Area Network	Countries/continents	The Internet itself

2. Network Models — OSI and TCP/IP

Networking is complex, so engineers use layered models to break the problem into manageable, independent pieces. Each layer has a specific job and only needs to know how to talk to the layers directly above and below it — not the internal workings of every other layer.

2.1 The OSI Model (7 Layers)

The Open Systems Interconnection (OSI) model is a conceptual, vendor-neutral reference model created by ISO. It's rarely implemented exactly as-is in real software, but it's the universal language networking professionals use to describe problems ("that's a Layer 2 issue," "check Layer 4").

Layer #	Name	Function	Example Protocols/Devices
7	Application	User-facing services	HTTP, FTP, SMTP, DNS
6	Presentation	Data format, encryption, compression	SSL/TLS, JPEG, ASCII
5	Session	Manages sessions/connections between apps	NetBIOS, RPC
4	Transport	End-to-end delivery, reliability	TCP, UDP
3	Network	Logical addressing & routing	IP, ICMP, routers
2	Data Link	Physical addressing, framing	Ethernet, MAC addresses, switches
1	Physical	Raw bit transmission	Cables, radio waves, hubs

Mnemonic (top to bottom): "All People Seem To Need Data Processing" — Application, Presentation, Session, Transport, Network, Data Link, Physical.

2.2 The TCP/IP Model (4 Layers)

The TCP/IP model is what the real-world internet is actually built on. It condenses OSI's seven layers into four practical ones:

TCP/IP Layer	Roughly Equivalent OSI Layers	Function
Application	Application, Presentation, Session (5–7)	User-facing protocols
Transport	Transport (4)	End-to-end communication
Internet	Network (3)	Addressing & routing
Network Access (Link)	Data Link, Physical (1–2)	Physical transmission

2.3 Encapsulation and Decapsulation

As data travels down the stack on the sending device, each layer wraps ("encapsulates") the data from the layer above with its own header (and sometimes a trailer). This is like nesting envelopes inside envelopes.

Application Data
   └── + TCP Header       → Segment
         └── + IP Header   → Packet
               └── + Ethernet Header/Trailer → Frame
                     └── Bits on the wire

On the receiving device, the process reverses — decapsulation — with each layer stripping off its corresponding header as the data travels back up the stack to the application.

Key Takeaway: Layered models let engineers change one layer (e.g., swap Wi-Fi for fiber) without redesigning everything else. Encapsulation is the mechanism that makes this possible — each layer only understands its own header.

3. The Physical Layer

The Physical Layer is where data becomes physical reality — electrical voltage, light pulses, or radio waves.

3.1 Transmission Media

Guided (wired) media:

Medium	Description	Typical Use	Max Practical Speed
Twisted-pair copper (UTP/STP)	Pairs of copper wires twisted to reduce interference	Ethernet LANs (Cat5e, Cat6, Cat6a)	Up to 10 Gbps
Coaxial cable	Copper core with shielding	Cable internet, older Ethernet	Up to 1+ Gbps
Fiber optic	Glass/plastic strands carrying light pulses	Backbone links, FTTH	Terabits/sec (with multiplexing)

Unguided (wireless) media: radio waves (Wi-Fi, cellular), microwaves (point-to-point links, satellite), and infrared (short-range, line-of-sight).

Analogy: Copper is a garden hose (limited by resistance and interference), fiber is a highway (light barely loses energy over distance), and wireless is shouting across a room (fast to set up, but shared and prone to interference).

3.2 Bandwidth, Throughput, and Signals

Bandwidth — the theoretical maximum data-carrying capacity of a medium (e.g., "a 100 Mbps link").
Throughput — the actual achieved data rate, always ≤ bandwidth due to overhead, congestion, or interference.
Analog vs. Digital signals — analog signals vary continuously (like a dimmer switch); digital signals are discrete on/off states (like a light switch). Modern networks are overwhelmingly digital, though the underlying physical signal (light, radio) is analog in nature and gets digitally encoded.

3.3 Multiplexing

Multiplexing lets multiple signals share one physical medium:

FDM (Frequency Division Multiplexing) — different signals use different frequency bands (like different radio stations).
TDM (Time Division Multiplexing) — different signals take turns using the full bandwidth in tiny time slices.
WDM (Wavelength Division Multiplexing) — used in fiber optics; different colors (wavelengths) of light carry separate data streams simultaneously.

Key Takeaway: The Physical Layer doesn't understand "data" — it only understands voltages, light, and radio waves. Everything meaningful about addressing and reliability is added by the layers above it.

4. The Data Link Layer

The Data Link Layer takes raw bits from the Physical Layer and organizes them into structured frames, adding physical addressing and basic error detection.

4.1 MAC Addresses

Every network interface card (NIC) has a Media Access Control (MAC) address — a 48-bit identifier, usually written as six hex pairs (e.g., 00:1A:2B:3C:4D:5E), burned into the hardware by the manufacturer. Unlike IP addresses (which can change), MAC addresses are (in theory) globally unique and tied to the physical device — this is why Layer 2 is sometimes called the "physical addressing" layer, in contrast to Layer 3's "logical addressing."

4.2 Ethernet

Ethernet is the dominant Data Link Layer technology for wired LANs. It defines how frames are structured, how devices detect collisions (historically, via CSMA/CD on shared media), and how switches forward frames based on MAC addresses.

A simplified Ethernet frame structure:

| Preamble | Dest MAC | Source MAC | EtherType | Payload (Data) | FCS (Checksum) |

4.3 Switches and the MAC Address Table

A switch operates at Layer 2. When a frame arrives, the switch looks up the destination MAC address in its MAC address table and forwards the frame only out the correct port — unlike an old-fashioned hub, which blindly broadcasts every frame out every port (wasteful and insecure). Switches learn MAC addresses dynamically by observing the source address of incoming frames.

4.4 ARP — Address Resolution Protocol

Since applications think in terms of IP addresses but frames need MAC addresses, ARP bridges the gap: a device broadcasts "Who has IP 192.168.1.5? Tell 192.168.1.10," and the owner of that IP replies with its MAC address. The result is cached locally in an ARP table to avoid repeating the lookup for every packet.

4.5 VLANs (Virtual LANs)

A VLAN lets administrators logically segment a single physical switch (or set of switches) into multiple isolated broadcast domains — e.g., separating "Staff," "Guests," and "IoT devices" traffic on the same physical hardware, improving both security and traffic management. VLAN tagging is defined by the IEEE 802.1Q standard.

4.6 Error Detection

The Data Link Layer typically includes a Frame Check Sequence (FCS), computed using Cyclic Redundancy Check (CRC) — a mathematical checksum that lets the receiver detect (but not necessarily correct) transmission errors caused by noise or interference.

Key Takeaway: The Data Link Layer's job is local delivery — getting a frame correctly from one device to the next device on the same physical/logical segment, using MAC addresses. It has no concept of the wider internet; that's the Network Layer's job.

5. The Network Layer

This is where the "inter" in "internet" comes from — the Network Layer is responsible for moving packets across multiple networks, from source to destination, potentially through many intermediate routers.

5.1 IP Addressing — IPv4

An IPv4 address is a 32-bit number, written in "dotted-decimal" notation as four 8-bit octets, e.g., 192.168.1.10. Each octet ranges from 0–255.

IP addresses are split into a network portion and a host portion, determined by a subnet mask, e.g., 255.255.255.0.

IPv4 address classes (historical, now mostly superseded by CIDR):

Class	Range	Default Mask	Typical Use
A	1.0.0.0 – 126.255.255.255	/8	Very large networks
B	128.0.0.0 – 191.255.255.255	/16	Medium networks
C	192.0.0.0 – 223.255.255.255	/24	Small networks

Private (non-routable) address ranges (RFC 1918) — used inside LANs, translated to public addresses via NAT:

10.0.0.0    – 10.255.255.255   (10.0.0.0/8)
172.16.0.0  – 172.31.255.255   (172.16.0.0/12)
192.168.0.0 – 192.168.255.255  (192.168.0.0/16)

5.2 Subnetting and CIDR — Worked Example

CIDR (Classless Inter-Domain Routing) notation expresses the subnet mask as a slash and a number, e.g., /24 meaning the first 24 bits are the network portion.

Worked example: You're given the network 192.168.10.0/24 and need to split it into 4 equal subnets.

/24 gives you 256 addresses total (2⁸). To make 4 subnets, you need 2 extra bits (2² = 4), so borrow 2 bits from the host portion → new mask is /26.
/26 = 255.255.255.192 → each subnet has 2⁶ = 64 addresses (62 usable, since the first is the network address and the last is the broadcast address).
The four resulting subnets:

Subnet	Network Address	Usable Host Range	Broadcast Address
1	192.168.10.0/26	.1 – .62	192.168.10.63
2	192.168.10.64/26	.65 – .126	192.168.10.127
3	192.168.10.128/26	.129 – .190	192.168.10.191
4	192.168.10.192/26	.193 – .254	192.168.10.255

Quick formula to remember:

Number of usable hosts per subnet = 2^(32 − CIDR) − 2
Number of subnets created by borrowing n bits = 2ⁿ

5.3 IPv6

IPv4 has roughly 4.3 billion addresses — long since exhausted given global device growth. IPv6 solves this with 128-bit addresses, written in 8 groups of hexadecimal digits, e.g.:

2001:0db8:85a3:0000:0000:8a2e:0370:7334

This can be abbreviated by omitting leading zeros in each group and replacing one run of consecutive all-zero groups with :::

2001:db8:85a3::8a2e:370:7334

IPv6 also simplifies routing, removes the need for NAT in most cases (thanks to its vast address space), and has built-in support for auto-configuration (SLAAC).

5.4 Routing

Routers operate at the Network Layer, forwarding packets between different networks based on destination IP address, using a routing table.

Routing algorithm families:

Type	How it works	Example Protocols
Distance Vector	Routers share their entire routing table with neighbors periodically; pick the path with fewest "hops"	RIP
Link State	Routers build a full map of the network topology and calculate shortest paths independently	OSPF, IS-IS
Path Vector	Used between large autonomous networks (like ISPs), considers full AS-path, not just hop count	BGP

5.5 NAT — Network Address Translation

NAT allows many devices on a private network (using private IPs) to share a single public IP address when communicating with the internet. Your home router performs NAT constantly — it's why dozens of devices in your house can all use the internet through one ISP-assigned IP address.

5.6 ICMP

ICMP (Internet Control Message Protocol) is used for diagnostics and error reporting rather than carrying application data — it powers tools like ping (echo request/reply) and traceroute (using ICMP or UDP with incrementing TTL values to map the path packets take).

Key Takeaway: The Network Layer's job is global delivery — getting a packet from any host, anywhere, to any other host, anywhere, by hopping through routers. IP addressing (v4 or v6) and routing protocols are the two pillars that make this possible.

6. The Transport Layer

The Transport Layer provides end-to-end communication between applications running on different hosts — as opposed to the Network Layer's host-to-host delivery.

6.1 TCP vs. UDP

Feature	TCP (Transmission Control Protocol)	UDP (User Datagram Protocol)
Connection	Connection-oriented (handshake required)	Connectionless
Reliability	Guaranteed delivery, retransmits lost data	Best-effort, no guarantees
Ordering	Data arrives in order	No ordering guarantee
Speed	Slower (overhead of reliability)	Faster (minimal overhead)
Use cases	Web browsing, email, file transfer	Video streaming, VoIP, DNS, online gaming

Analogy: TCP is a phone call — you confirm the other person can hear you, and you repeat anything they missed. UDP is a postcard — you send it and hope it arrives; if it doesn't, no automatic retry happens.

6.2 The TCP Three-Way Handshake — Worked Example

Before any data flows over TCP, the two sides establish a connection:

Client                         Server
  |------ SYN (seq=x) --------->|
  |<--- SYN-ACK (seq=y,ack=x+1)-|
  |------ ACK (ack=y+1) ------->|
  |         Connection established       |

SYN: Client sends a segment with the SYN flag set and an initial sequence number (x), essentially saying "I'd like to start a conversation, starting at sequence x."
SYN-ACK: Server replies with its own SYN (sequence y) and an ACK acknowledging the client's sequence (x+1).
ACK: Client acknowledges the server's sequence (y+1), and the connection is now fully established (bidirectional).

Closing a connection uses a similar four-step process involving FIN and ACK flags.

6.3 Flow Control and Congestion Control

Flow control prevents a fast sender from overwhelming a slow receiver, using a sliding window mechanism where the receiver advertises how much data it can currently buffer.
Congestion control prevents the sender from overwhelming the network itself (routers, links), using algorithms like TCP slow start (start sending slowly, ramp up) and congestion avoidance (back off when packet loss is detected, since loss is often a sign of a congested router dropping packets).

6.4 Ports and Sockets

A port number (0–65535) identifies a specific application or service on a host. Combined with an IP address, it forms a socket — the true endpoint of network communication (e.g., 192.168.1.10:443 for an HTTPS connection).

Well-known ports:

Port	Protocol	Service
20/21	FTP	File Transfer
22	SSH	Secure Shell
25	SMTP	Email sending
53	DNS	Domain lookups
80	HTTP	Web (unencrypted)
443	HTTPS	Web (encrypted)

Key Takeaway: TCP trades speed for reliability and is right for anything where correctness matters more than latency (loading a webpage). UDP trades reliability for speed and is right for anything where timeliness matters more than perfection (a live video call where a dropped frame is better than a frozen stream).

7. The Application Layer

This is the layer users actually interact with — the protocols behind email, web browsing, and file transfer.

7.1 DNS — The Internet's Phone Book

Humans use domain names (swiftener.com); computers use IP addresses. DNS (Domain Name System) translates between the two.

Simplified DNS resolution process:

1. Browser asks: "What's the IP for swiftener.com?"
2. Recursive resolver (usually your ISP) checks its cache — if empty:
3. Asks a Root DNS server → "Ask the .com TLD server"
4. Asks the .com TLD server → "Ask swiftener.com's authoritative server"
5. Authoritative server replies with the actual IP address
6. Resolver caches the result and returns it to the browser

Common DNS record types: A (IPv4 address), AAAA (IPv6 address), CNAME (alias), MX (mail server), TXT (arbitrary text, often used for verification/SPF records).

7.2 HTTP and HTTPS

HTTP (HyperText Transfer Protocol) is the request-response protocol underlying the Web. A browser sends a request (GET /page HTTP/1.1), and a server responds with a status code (200 OK, 404 Not Found, 500 Internal Server Error, etc.) plus content.

HTTPS is HTTP layered over TLS (Transport Layer Security), encrypting traffic so intermediaries (ISPs, attackers on shared Wi-Fi) can't read or tamper with it. Modern browsers flag plain HTTP sites as "Not Secure."

7.3 FTP, SMTP, and DHCP

FTP (File Transfer Protocol) — transfers files between client and server; largely superseded by HTTPS-based or SSH-based (SFTP) alternatives for security reasons.
SMTP (Simple Mail Transfer Protocol) — used for sending email between mail servers (retrieval uses separate protocols like IMAP or POP3).
DHCP (Dynamic Host Configuration Protocol) — automatically assigns IP addresses, subnet masks, default gateways, and DNS servers to devices joining a network, so you don't have to configure each device by hand.

DHCP process (DORA):

Discover → Offer → Request → Acknowledge
(Client)    (Server)  (Client)   (Server)

Key Takeaway: The Application Layer is where all the lower layers' work finally becomes visible to a human — a webpage loading, an email sending, a domain name resolving. Every one of these depends silently on everything from Layers 1–4 working correctly underneath.

8. Network Security

8.1 Firewalls

A firewall filters traffic based on rules (source/destination IP, port, protocol). Types include:

Packet-filtering firewalls — inspect individual packets against static rules.
Stateful firewalls — track the state of active connections, allowing return traffic for connections initiated from inside.
Next-Generation Firewalls (NGFW) — add deep packet inspection, intrusion prevention, and application awareness.

8.2 VPNs

A Virtual Private Network (VPN) creates an encrypted tunnel across an untrusted network (like the public internet), making remote traffic behave as if it were on a private, secure network — commonly used for secure remote work access or to protect traffic on public Wi-Fi.

8.3 TLS/SSL and Encryption Basics

TLS (Transport Layer Security), the successor to the older SSL, secures data in transit using a combination of:

Asymmetric (public-key) cryptography — used during the initial handshake to securely exchange a shared secret, without ever transmitting a private key.
Symmetric cryptography — used for the actual bulk data encryption after the handshake, since it's much faster.
Digital certificates — issued by trusted Certificate Authorities (CAs), proving a server is who it claims to be, preventing impersonation.

8.4 Common Attacks

Attack	Description
DDoS (Distributed Denial of Service)	Overwhelming a target with traffic from many sources to make it unavailable
Man-in-the-Middle (MITM)	Attacker secretly intercepts/alters communication between two parties
Spoofing	Falsifying source addresses (IP spoofing, MAC spoofing, DNS spoofing) to impersonate a trusted entity
Phishing	Social engineering to trick users into revealing credentials (technically application-layer/social, but a major network-security concern)
Packet Sniffing	Capturing unencrypted traffic on a network to read sensitive data

Key Takeaway: Network security isn't a single layer — it's applied at every layer (VLANs at Layer 2, firewalls at Layer 3/4, TLS at Layer 4/7). Defense in depth, not a single silver bullet, is the guiding principle.

9. Wireless & Mobile Networking

9.1 Wi-Fi Standards (IEEE 802.11)

Standard	Marketing Name	Max Theoretical Speed	Frequency Band
802.11n	Wi-Fi 4	600 Mbps	2.4/5 GHz
802.11ac	Wi-Fi 5	~3.5 Gbps	5 GHz
802.11ax	Wi-Fi 6/6E	~9.6 Gbps	2.4/5/6 GHz

Key wireless concepts: SSID (network name), WPA2/WPA3 (encryption standards — always prefer WPA3 or WPA2 over the obsolete and insecure WEP), and channel/interference management (2.4 GHz has longer range but more interference and fewer non-overlapping channels than 5 GHz).

9.2 Cellular Networking Basics

Generation	Approx. Era	Key Feature
2G	1990s	Digital voice, basic SMS
3G	2000s	Mobile data, basic internet
4G/LTE	2010s	High-speed mobile broadband
5G	2020s	Ultra-low latency, massive device density, network slicing

Cellular networks divide geography into cells, each served by a base station, allowing frequency reuse across non-adjacent cells and seamless handoff as devices move between cells.

Key Takeaway: Wireless networking introduces challenges wired networks don't have — shared, contested airspace, interference, and mobility — solved through channel management, encryption standards, and handoff protocols.

10. Network Performance & Troubleshooting

10.1 Key Performance Metrics

Metric	Definition	Why It Matters
Latency	Time for a packet to travel from source to destination	Critical for gaming, VoIP, video calls
Throughput	Actual achieved data transfer rate	The "real world" speed you experience
Jitter	Variation in latency over time	Causes choppy audio/video if too high
Packet Loss	Percentage of packets that never arrive	Causes retransmissions, degraded quality

10.2 Essential Diagnostic Tools

ping — sends ICMP echo requests to test basic reachability and measure round-trip latency.
traceroute / tracert — maps the path (hop by hop) packets take to a destination, useful for pinpointing where delay or failure occurs.
netstat — displays active network connections, listening ports, and routing tables on a local machine.
nslookup / dig — queries DNS servers directly, useful for diagnosing domain resolution issues.

Example troubleshooting workflow:

1. Can't reach a website?
2. ping the destination — is it reachable at all?
3. If ping fails, ping the default gateway — is local connectivity OK?
4. traceroute to see where packets stop getting further
5. nslookup the domain — is DNS resolving correctly?
6. Check netstat for local port/connection issues

Key Takeaway: Most networking problems can be isolated to a specific layer using a small set of universal tools — always work systematically from the local device outward (physical connectivity → local network → DNS → remote host).

11. Modern Topics: SDN, Cloud & IoT Networking

11.1 Software-Defined Networking (SDN)

Traditional networking hardware bundles the control plane (deciding where traffic should go) and data plane (actually moving traffic) into the same physical device. SDN separates these, centralizing the control plane in software that can programmatically manage many physical switches/routers — enabling more flexible, automated, and centrally-managed network configuration, widely used in large data centers and cloud environments.

11.2 Cloud Networking Basics

Cloud providers (AWS, Azure, GCP) let organizations build virtual networks (e.g., AWS VPC — Virtual Private Cloud) entirely in software, including virtual subnets, route tables, firewalls (security groups), and load balancers — applying the same fundamental concepts from this course, just implemented as configurable cloud resources instead of physical hardware.

11.3 IoT Networking Considerations

Internet of Things (IoT) devices (sensors, smart home devices, industrial equipment) often have unique networking constraints: low power budgets, low bandwidth needs, and huge device counts. This has driven specialized protocols like MQTT (lightweight publish-subscribe messaging) and Zigbee/Z-Wave (low-power mesh networking), alongside security practices like network segmentation (keeping IoT devices on isolated VLANs, as mentioned in Section 4.5) to limit the damage if a device is compromised.

Key Takeaway: Modern networking increasingly separates what the network should do (defined in software, often centrally and dynamically) from the physical hardware moving the bits — a direct evolution of the same layered principles covered in this course.

12. Glossary of Key Terms

Term	Definition
Bandwidth	Maximum theoretical data capacity of a link
Encapsulation	Wrapping data with headers as it moves down the protocol stack
Frame	Data Link Layer protocol data unit
Host	Any device connected to a network
Latency	Time delay for data to travel from source to destination
MAC Address	Hardware-based physical address of a network interface
NAT	Technique for sharing one public IP among many private-IP devices
Packet	Network Layer protocol data unit
Port	Number identifying a specific application/service on a host
Protocol	Agreed-upon rules governing communication
Router	Device that forwards packets between different networks
Segment	Transport Layer protocol data unit
Socket	Combination of IP address + port, identifying a communication endpoint
Subnet	A logically segmented portion of a larger network
Switch	Device that forwards frames within a network based on MAC address
Throughput	Actual achieved data transfer rate

13. Further Reading & Next Steps

RFC 791 (IPv4) and RFC 8200 (IPv6) — the actual internet standards documents, for those who want primary sources.
"Computer Networking: A Top-Down Approach" by Kurose & Ross — the standard university textbook this course loosely mirrors.
Practice: Set up a home lab using free tools like Wireshark (packet capture/analysis), Packet Tracer or GNS3 (network simulation), and a couple of virtual machines to practice subnetting, routing, and firewall rules hands-on.
Certifications to consider after this course: CompTIA Network+, Cisco CCNA.
Next course suggestion: Follow this up with a dedicated course on Network Security & Ethical Hacking, or a deep dive into Routing Protocols (OSPF/BGP) for those heading toward network engineering.

This course is intended as a broad, exam- and career-ready foundation. Each section here could easily expand into its own multi-week module — treat this as your map of the territory, and dive deeper into whichever region interests you most.

#networking #tcpip #osimodel #ipv6 #subnetting #cybersecurity #dns #computerscience #universitycourse #techeducation