Networking Fundamentals
You’ll follow a real web request from laptop to server. You’ll learn not just terms, but what each device and protocol layer does.
Start with the ScenarioBefore you start
Who is this for?
For beginners with no networking experience and anyone who wants to understand individual concepts as a connected flow.
Prerequisites
- You can operate a browser.
- You don't need command line or math skills.
What you'll be able to do
- Distinguish switches, access points, and routers by their function
- Explain how a web request travels through the network
- Use OSI and TCP/IP models for troubleshooting
- Correctly assign MAC, IP, and port addresses
Practical outcome
You can draw a simple network path and, when troubleshooting, justify whether to check wireless/wired links, local addressing, routing, DNS, or the web service first.
1. What is a network?
Section titled “1. What is a network?”A network forms when devices exchange data over a shared medium and agreed-upon rules. The medium can be an Ethernet cable, fiber optics, or wireless. These rules are called protocols.
A small home network, for example, includes a laptop, smartphone, printer, and router. The printer provides a service; the laptop and smartphone can use it together. The router connects this local network to other networks—usually the internet.
Term: An IP network is a group of IP addresses with the same network portion. Devices in the same network can reach each other directly. Between different IP networks, a router must forward traffic.
Mini-exercise
Section titled “Mini-exercise”Your laptop and printer are on the same Wi-Fi network and use appropriate IP addresses. Does a print job to the local network absolutely require the internet? No. The access point and local network are sufficient; the internet connection can fail without making local printing impossible.
2. What do devices do?
Section titled “2. What do devices do?”| Device | Simple Function | Technical View |
|---|---|---|
| Access Point | connects Wi-Fi devices to the local network | bridges 802.11 wireless and typically Ethernet at Layer 2 |
| Switch | delivers local frames to the correct port | learns MAC addresses per port and VLAN |
| Router | connects different IP networks | selects the next hop using a routing table |
| Firewall | controls allowed connections | filters by addresses, ports, protocols, and state |
| Modem/ONT | adapts the connection to the provider | converts signals appropriate for the access type |
A typical home router combines several of these roles: Wi-Fi access point, small switch, IP router, firewall, DHCP server, and often NAT.
Common Misconception: A switch doesn’t “know about the internet.” It transports local Ethernet frames. Only the router decides on a path to another IP network.
3. The Central Scenario: You Open a Webpage
Section titled “3. The Central Scenario: You Open a Webpage”Your laptop has 192.168.1.20/24, with the default gateway at 192.168.1.1. You open https://example.com.
Step 1: Name Resolution
Section titled “Step 1: Name Resolution”People remember example.com; IP routing, however, uses IP addresses. Therefore, the laptop queries a DNS resolver for the IP address. Without working DNS, a known IP might be reachable, even though the name doesn’t work in the browser.
Step 2: Local or Remote?
Section titled “Step 2: Local or Remote?”The laptop compares the destination IP with its own IP using the /24 mask. The web server is not in the local network 192.168.1.0/24. Therefore, the laptop sends the packet to its default gateway at 192.168.1.1.
Step 3: The Local Frame is Created
Section titled “Step 3: The Local Frame is Created”For Wi-Fi or Ethernet, the laptop needs the local hardware address of the next hop. For IPv4, it queries via ARP for the gateway’s MAC address. After that, the local frame contains, simplified:
- Destination MAC: Gateway’s MAC
- Source MAC: Laptop’s MAC
- Destination IP: Web server’s IP
- Source IP: Laptop’s private IP
- Destination Port: Typically TCP 443 for classic HTTPS
The MAC destination and IP destination are intentionally different: The MAC only carries the frame to the next local hop; the IP describes the ultimate destination.
Step 4: Routers Forward
Section titled “Step 4: Routers Forward”The router removes the local frame header, examines the destination IP, and looks up the best entry in its routing table. In a home network, it often additionally translates the private source address via NAT/PAT into a public address. Additional routers repeat the path decision.
Step 5: Connection and Encrypted Request
Section titled “Step 5: Connection and Encrypted Request”For classic HTTPS, TCP establishes a reliable connection. TLS authenticates the server and encrypts the application data. Only then does the browser send the HTTP request. The web server responds, and the data travels back through appropriate paths to the laptop.
What Does the User See?
Section titled “What Does the User See?”Mostly brief status messages like “Resolving host”, “Establishing connection”, or a loading spinner. However, behind a page load, DNS, ARP or IPv6 Neighbor Discovery, Wi-Fi/Ethernet, IP, routing, TCP or QUIC, TLS, and HTTP all work together.
Ordering exercise
Order the simplified web request sequence
Arrange the steps so that each later step builds upon the previous one.
4. Why do we have layer models?
Section titled “4. Why do we have layer models?”Without a model, “The internet isn’t working” would be too vague. Layers separate concerns and help ask questions in a meaningful order.
| OSI Layer | Typical Function | Scenario Example | Troubleshooting Question |
|---|---|---|---|
| 7 Application | Services for applications | HTTP, DNS | Is the service responding correctly? |
| 6 Presentation | Formatting, encoding, encryption | TLS, UTF-8 | Is the certificate or format failing? |
| 5 Session | Managing sessions/dialogues | Session state | Is the session repeatedly breaking? |
| 4 Transport | Connecting applications via ports | TCP, UDP | Is port 443 reachable? |
| 3 Network | Logical addressing and routing | IPv4/IPv6 | Do we have an address, gateway, and route? |
| 2 Data Link | Delivery on the local link | Ethernet, Wi-Fi, MAC | Does the VLAN/SSID match, and does ARP work? |
| 1 Physical | Signals over the medium | Wireless, copper, fiber | Is the link or wireless signal present? |
The practical TCP/IP model groups these functions more broadly: Application, Transport, Internet, and Network Access. It doesn’t contradict the OSI model; it just groups functions differently.
Important: The OSI model is not a flow where a packet must pass through seven physical devices. It’s a thinking and description tool.
5. Encapsulation without jargon fog
Section titled “5. Encapsulation without jargon fog”An application generates payload data. Each lower layer adds control information:
- HTTP formulates the request.
- TCP adds, among other things, source and destination ports.
- IP adds source and destination IP addresses.
- Ethernet or Wi-Fi adds local source and destination addresses plus error checking.
- The medium transmits bits as electrical, optical, or wireless signals.
At the receiver, this information is processed in reverse order. Routers replace the Layer 2 frame on each Ethernet segment, but the IP packet generally remains directed to its final destination.
6. Network types and topologies
Section titled “6. Network types and topologies”A LAN covers a limited area like a home or office. A WAN connects networks over greater distances. Wi-Fi refers to a wireless LAN, while a VLAN represents a logical Layer 2 separation and a VPN creates a secure tunnel over another network.
Modern LANs typically use a star topology: End devices connect to central switches or access points. Tree-like extensions connect multiple switch layers. Redundant connections increase availability but require loop protection at Layer 2.
Client, server, and service
Section titled “Client, server, and service”Client and server are roles, not fixed device types. A browser acts as a client to a web server, while a laptop can simultaneously act as a client querying DNS and as a server providing a local file. The server process listens at an address and port for requests. A physical server can offer multiple services, and a service can be distributed across many systems.
Bandwidth, throughput, latency, and packet loss
Section titled “Bandwidth, throughput, latency, and packet loss”These metrics describe different characteristics of a path:
- Bandwidth is the theoretical or agreed-upon transmission capacity, such as 1 Gbit/s.
- Throughput is the actual amount of data transferred per unit of time. Protocol overhead, wireless conditions, and competing traffic reduce it.
- Latency is the delay between sending and receiving. Interactive applications react to high latency, even with abundant bandwidth available.
- Packet loss refers to discarded packets. TCP retransmits lost data, while real-time applications may experience glitches.
Therefore, more bandwidth doesn’t automatically fix high latency or packet loss. Good troubleshooting measures the metric that matches the symptom.
7. How to isolate a problem
Section titled “7. How to isolate a problem”When a webpage fails to load, don’t test everything at once:
- Layer 1/2: Is Wi-Fi connected, or is the Ethernet link active?
- Local configuration: Does the device have a plausible IP address, mask, and gateway?
- Local path: Is the gateway reachable?
- Routing: Can you reach an external destination by IP?
- DNS: Can the name be resolved?
- Transport/service: Is the required port reachable, and does HTTPS respond correctly?
This uses the layer model practically: each successful test narrows the failure range.
Common mistakes
Section titled “Common mistakes”- Treating switches and routers as the same, even though they decide based on different addresses and boundaries.
- Confusing a successful Wi-Fi connection with a working internet connection.
- Treating bandwidth as actually guaranteed throughput.
- Testing DNS even though the client lacks a usable IP configuration.
- Treating a blocked ICMP response as proof that every application service is down.
Map a web request
Objective: Draw the path of one HTTPS request and assign each decision to the correct device and layer.
Scenario: A laptop at 192.168.1.20/24 uses gateway 192.168.1.1 and opens https://example.com.
- Draw laptop, access point, switch/router, DNS resolver, and web server.
- Mark where a name becomes an IP address and where ARP supplies a local MAC address.
- Label the IP destination and local MAC destination before the first router.
- Add one likely symptom for a DNS fault, gateway fault, and HTTPS service fault.
- Verify that your first diagnostic test matches the lowest plausible failing layer.
Expected result and hints
The remote server remains the IP destination while the gateway is the local Layer-2 destination. A DNS fault affects names, a gateway fault affects remote IP destinations, and a service fault can leave basic IP reachability intact.What you should be able to do now
Section titled “What you should be able to do now”- Describe the path of a web request in your own words;
- Distinguish access points, switches, routers, and firewalls;
- Explain why a remote destination is sent to the gateway;
- Assign MAC addresses, IP addresses, and ports to the correct function;
- Use OSI/TCP-IP as a tool for systematic troubleshooting.
Final quiz
Section titled “Final quiz”Multiple Choice