What is a ROUTER? // FREE CCNA // EP 2
Based on NetworkChuck's video on YouTube. If you like this content, support the original creators by watching, liking and subscribing to their content.
Switches forward frames within the same IP subnet using MAC addresses, so they can’t connect different IP networks by themselves.
Briefing
Routers are the missing link that lets devices on one IP network reach devices on another network—switches can only move traffic within the same IP subnet. In the lab setup, “Johnny” can successfully ping “Mark” because both sit in the same address range (10.1.1.0/24). But when Johnny tries to reach the coffee server on a different subnet (23.227.38.0/24), the switch can’t help; no amount of layer-2 forwarding will bridge different IP networks.
The episode walks through what happens at the frame level to make that distinction concrete. On the local network, Johnny pings Mark’s IP (10.1.1.2). Because the switch understands only layer 2 (MAC addresses), Johnny first uses ARP (Address Resolution Protocol) to discover Mark’s MAC address. The ARP request is broadcast (destination MAC ffffffff), the device with the matching IP responds, and the switch learns where to send the subsequent ping frame—now the destination MAC is Mark’s, and delivery works.
When Johnny pings the coffee server (23.227.38.65), the behavior changes immediately. Johnny still sends an ARP broadcast, but he does not try to resolve the coffee server’s MAC address directly. Instead, he targets the gateway IP (10.1.1.1), because his configuration tells him that 10.1.1.0–10.1.1.255 is “local,” while 23.227.38.0/24 is “remote.” With no host on the local subnet answering for 23.227.38.65, Johnny relies on the router as the next hop.
Once the router is back in the path, the process becomes a two-step handoff between layer 2 and layer 3. Johnny sends a frame to the router’s MAC address, carrying an IP packet whose destination is the coffee server’s IP. The router receives the frame on its interface, then consults its layer-3 routing logic to determine where the packet should go next. To forward the packet, the router must again resolve the next-hop MAC address on the outbound network—using ARP to find the coffee server’s MAC on the 23.227.38.0/24 side. After that, the switch can deliver the frame to the coffee server, and the reply follows the same logic back through the router.
The episode then connects this to real web browsing. Typing networkchuck.coffee requires DNS, not just pinging an IP. Johnny queries a DNS server (configured at 10.1.1.50), learns the web server’s IP address, and only then sends the HTTP GET request toward that IP. The router’s job remains consistent: connect separate IP networks using its “map” of routes.
Finally, the episode previews why routing scales: a router’s routing table and protocols (demonstrated via show bgp) can contain routes to many networks across the internet. The takeaway is straightforward but foundational for CCNA: switches move frames inside a subnet; routers move packets between subnets using IP routing, gateway configuration, ARP for next-hop MACs, and supporting services like DNS for name-to-IP resolution.
Cornell Notes
Routers connect different IP networks, while switches mainly forward within a single IP subnet using MAC addresses. On the same network, a host uses ARP to map an IP (like 10.1.1.2) to a MAC address so the switch can deliver frames. When the destination is outside the local subnet, the host sends traffic to its configured gateway (default gateway, here 10.1.1.1) instead of trying to resolve the remote host’s MAC directly. The router then forwards the packet by resolving the next-hop MAC on the destination network. For web access, DNS translates names like networkchuck.coffee into an IP address before HTTP traffic is sent through the router.
Why does pinging Mark work without a router, but pinging the coffee server doesn’t?
What role does ARP play on the local network?
What changes when Johnny tries to reach an IP outside his subnet?
How does a router forward traffic between networks when it receives a frame?
Why does visiting networkchuck.coffee require DNS before HTTP?
What does show ip route / show bgp illustrate about routing at scale?
Review Questions
- In the lab, what IP range determines whether a destination is treated as “local” versus “remote,” and how does that affect ARP behavior?
- Trace the addressing steps (layer 2 and layer 3) for Johnny reaching the coffee server: which MAC addresses are used at each hop?
- Why must DNS resolve networkchuck.coffee to an IP address before the router can forward the web request?
Key Points
- 1
Switches forward frames within the same IP subnet using MAC addresses, so they can’t connect different IP networks by themselves.
- 2
Hosts use ARP to map a local destination IP to a MAC address; ARP requests are broadcast to ffffffff.
- 3
When the destination IP is outside the local subnet, the host sends traffic to the default gateway (router) instead of resolving the remote host’s MAC directly.
- 4
Routers operate at layer 3: they read the destination IP, consult their routing table, and then resolve the next-hop MAC on the outbound network.
- 5
Web browsing requires DNS to convert names like networkchuck.coffee into IP addresses before HTTP traffic is sent.
- 6
A router’s routing table (and protocols like BGP) is what enables connectivity across many networks on the internet.