Chapter 9 — Session 2: The IP Routing Process

This section answers one big question:

What exactly happens when Host_A sends data to Host_B on a different network?

The book walks through this in 36 individual steps, but you do not need to memorize 36 steps individually. You need to understand the pattern behind them.

1. Host_A Creates the Packet

The example starts with Host_A pinging Host_B.

Because this is a ping:

ICMP creates an Echo Request.

ICMP then hands the data to IP, which creates the packet.

At minimum, the IP packet contains:

Source IP:       Host_A
Destination IP:  Host_B
Protocol:        ICMP

The Protocol field tells the receiving computer which protocol should eventually receive the payload. In this example, that is ICMP.

🧠 Memory

Ping → ICMP → IP packet

2. Is the Destination Local or Remote?

Now Host_A looks at Host_B's destination IP and determines:

Is this destination on my network or another network?

There are two possibilities:

Destination
     │
     ├── Same network → Send directly to host
     │
     └── Different network → Send to DEFAULT GATEWAY

In the chapter's example, Host_B is on another network.

Therefore:

Host_A must send the traffic to its default gateway.

🧠 Know this cold

Local destination → send directly

Remote destination → send to default gateway

3. Host_A Needs the Default Gateway's MAC Address

This is where ARP comes back.

Host_A knows the default gateway's IP address, but Ethernet needs a MAC address to build the frame.

Example:

Host_A
IP: 172.16.10.2

Default Gateway
IP: 172.16.10.1

Host_A needs to determine:

172.16.10.1
      ↓
What MAC address belongs to this IP?

So Host_A checks its ARP cache.

On a Windows computer:

arp -a

might show:

172.16.10.1 → 00-15-05-06-31-b0

If the gateway's MAC address is already there:

Use it.

If it isn't there:

Send an ARP broadcast.

The router responds with its interface's MAC address, and Host_A stores it in the ARP cache.

🧠 Memory

ARP = IP → MAC

4. Host_A Builds the Ethernet Frame

Now we get to one of the most important concepts in Chapter 9.

Suppose:

Host_A
IP: 172.16.10.2
MAC: AA-AA-AA

Router
IP: 172.16.10.1
MAC: RR-RR-RR

Host_B
IP: 172.16.20.2
MAC: BB-BB-BB

Host_A is trying to communicate with Host_B.

The IP packet says:

Source IP:
172.16.10.2

Destination IP:
172.16.20.2

But the Ethernet frame says:

Source MAC:
AA-AA-AA

Destination MAC:
RR-RR-RR

Why isn't the destination MAC Host_B?

Because Host_B is on a different LAN.

Host_A can't send an Ethernet frame directly across a router to Host_B.

Instead:

Host_A sends the frame to the next local device responsible for routing the packet — its default gateway.

The chapter explicitly emphasizes that the frame contains Host_A's MAC and the default gateway's MAC, not the remote host's MAC.

⭐ The Big Rule

Memorize this:

REMOTE DESTINATION

Destination IP
      ↓
Remote Host

Destination MAC
      ↓
Default Gateway

Or:

IP = where the packet ultimately needs to go.

MAC = where the frame needs to go NEXT on the local network.

This distinction is extremely important

It means this:

When your computer sends data to a device outside your local network, the IP address and MAC address are pointing to different things.

Imagine:

Your PC → Router → Internet → Google

If you’re trying to reach Google:

• Destination IP = Google’s IP address

• Destination MAC = your router/default gateway’s MAC address

Why? Because your computer knows:

“Google is the final destination, but I can’t send a frame directly to Google. I need to give it to my router first.”

So think of it like:

IP = FINAL destination
MAC = NEXT stop

Example

Your computer:
192.168.1.10

Your router:
192.168.1.1

Google:
142.250.x.x

Your computer creates something roughly like:

Destination IP:

142.250.x.x   ← Google

Destination MAC:

AA:BB:CC:DD:EE:FF   ← Your router

The router receives it, removes the Ethernet frame, and creates a new frame for the next hop.

So the MAC address can change every hop, while the destination IP continues pointing toward the remote computer.

One important exception: if you’re communicating with another device on your same LAN, then the destination MAC is that device’s MAC—not the default gateway.

Memory trick:

IP = Where am I ultimately going?
MAC = Who am I handing this to next?

5. The Frame Goes onto the Network

Once the Ethernet frame has been created, it is handed down to the Physical layer.

The Physical layer sends it across the physical medium:

Frame
  ↓
Physical Layer
  ↓
Bits
  ↓
Network medium

In the chapter's example, the medium is twisted-pair cabling.

6. The Router Receives the Frame

The router receives the bits and reconstructs the Ethernet frame.

It then performs checks.

One important check involves:

FCS — Frame Check Sequence

The FCS contains the result of a CRC calculation.

The receiving device performs its own CRC calculation.

If they don't match:

❌ Frame is discarded.

If they match:

✅ Continue processing.

Then the router checks the destination MAC address.

Because the destination MAC belongs to the router's interface, the router accepts the frame.

🧠 Memory

FCS/CRC = "Did this frame arrive intact?"

7. The Router Removes the Frame

This is another major concept.

The router doesn't just forward the exact Ethernet frame it received.

Instead:

Received Frame
      ↓
Remove Layer 2 frame
      ↓
IP Packet
      ↓
Examine destination IP

The old Ethernet frame is discarded.

The router now processes the IP packet.

8. Router Checks the Destination IP

The router looks at:

Destination IP:
172.16.20.2

Then it checks its routing table.

Remember:

show ip route

The router isn't primarily searching for:

172.16.20.2

as an individual host.

It's looking for the destination network containing that host:

172.16.20.0/24

9. What If There Is No Route?

Suppose the router checks its routing table and cannot find a route to the destination network.

The chapter says the packet is discarded and an ICMP Destination Unreachable message is sent back toward the originating device.

So:

Packet arrives
      ↓
Check destination IP
      ↓
Check routing table
      ↓
Route found?
   ↙       ↘
 YES       NO
  ↓         ↓
Forward    DROP
            +
       ICMP Destination
         Unreachable

🧠 Memory

No route = nowhere to send it.

10. Router Finds the Route

In the chapter example, the router does know the destination network.

Its routing table contains:

C 172.16.10.0
C 172.16.20.0

Remember:

C = Connected

Therefore the router knows:

172.16.20.0

is directly connected to one of its interfaces.

The packet is switched toward that exit interface.

11. Router Now Needs Host_B's MAC

The packet has reached the router.

The router now needs to send it onto Host_B's local LAN.

At this point, the router needs:

Host_B's MAC address.

So the router checks its own ARP cache.

If Host_B's mapping is already there:

172.16.20.2
      ↓
BB-BB-BB

use it.

If not:

Router sends an ARP request onto Host_B's LAN.

Host_B responds with its MAC address.

12. Router Builds a NEW Frame

This is huge.

The router discarded the original frame.

Now it creates a new Ethernet frame.

Originally:

HOST_A → ROUTER

Source MAC:
Host_A

Destination MAC:
Router

After routing:

ROUTER → HOST_B

Source MAC:
Router's outgoing interface

Destination MAC:
Host_B

But the packet is still traveling toward Host_B.

Conceptually:

IP PACKET

Source IP: Host_A
Destination IP: Host_B

The chapter's exam essentials summarize the intended lesson as:

The frame changes at each hop.

⭐ PACKET vs. FRAME

This is probably the most important thing from this section.

Imagine:

HOST A -------- ROUTER -------- HOST B

First LAN

FRAME

Source MAC:
Host_A

Destination MAC:
Router

Inside that frame:

PACKET

Source IP:
Host_A

Destination IP:
Host_B

Second LAN

Router removes the old frame and builds another:

FRAME

Source MAC:
Router

Destination MAC:
Host_B

Inside:

PACKET

Source IP:
Host_A

Destination IP:
Host_B

So the important distinction is:

MAC addresses

Change as the packet moves between LANs.

IP addresses

For the basic routing process being taught here, think of them as identifying the original source and final destination throughout the trip.

13. Host_B Receives the Frame

Host_B receives the new Ethernet frame.

It checks:

1. FCS / CRC

Did the frame arrive intact?

2. Destination MAC

Is this frame actually for me?

3. Ether-Type

Which Network-layer protocol should receive the packet?

In this example:

IPv4

Then IP checks:

Destination IP

and sees:

That's my IP address.

The packet has reached its destination.

14. ICMP Receives the Ping

Remember what started everything?

ping Host_B

That created an:

ICMP Echo Request

Host_B's IP layer sees that the packet's Protocol field indicates ICMP.

So the payload is handed to ICMP.

ICMP recognizes:

Echo Request.

Host_B then creates:

ICMP Echo Reply

15. Now Everything Happens in Reverse

Host_B becomes the source.

It wants to send the Echo Reply back to Host_A.

Host_A is on a different network.

Therefore:

Host_B
   ↓
Destination remote?
YES
   ↓
Send toward default gateway
   ↓
Need gateway MAC
   ↓
Check ARP
   ↓
Build frame
   ↓
Router
   ↓
Check routing table
   ↓
Forward toward Host_A

The same routing process happens in reverse.

⚠ Return Route Matters

This is a very useful troubleshooting concept from the chapter.

Traffic can successfully reach the destination but still fail on the return trip.

Example:

Host_A
   ↓
Router 1
   ↓
Router 2
   ↓
Host_B

Host_B receives the ping.

But Router 2 doesn't know how to get back to Host_A's network.

Then:

Host_A → Host_B
        SUCCESS

Host_B → Host_A
        ❌ FAIL

The user just sees:

Request Timed Out

So a failed ping does not necessarily mean the original packet never reached the destination. The chapter specifically warns that a router on the return path may lack a route back to the originating network.

🧠 Memory

Routing must work BOTH ways.

16. MAC Addresses Are LOCAL

This is one of the chapter's biggest exam points.

MAC addresses are always local to the LAN.

They do not travel through routers.

Example:

Host_A
MAC: AAAA
      │
      ▼
Router
MAC: BBBB
      │
      ▼
Host_B
MAC: CCCC

Host_A does not need to know:

Host_B MAC = CCCC

to send traffic to Host_B on another network.

Host_A only needs the MAC of its:

Default gateway

17. Switches Are NOT the Default Gateway

This becomes important in the examples immediately after the routing walkthrough.

Imagine:

Host_A
   │
 Switch
   │
 Router
   │
 Switch
   │
Server

Host_A needs to reach the server on another network.

The destination MAC in Host_A's first frame is:

❌ Switch MAC

❌ Server MAC

✅ Router interface MAC

The chapter explicitly warns against choosing the switch as the default-gateway destination.

18. Layer Addresses During Routing

Suppose Host_A accesses an HTTPS server on another network.

You could see:

Layer 2 — Frame

Destination MAC:
Default Gateway

Layer 3 — Packet

Destination IP:
HTTPS Server

Layer 4 — Segment

Destination Port:
443

So remember:

L2 → NEXT local device
L3 → FINAL destination
L4 → APPLICATION/service

For HTTPS:

MAC → Router
IP  → Server
Port → 443

The chapter uses HTTP/HTTPS examples to reinforce exactly this distinction.

🧠 The Routing Process You Should Memorize

Instead of memorizing all 36 book steps, memorize this flow:

1. Create packet
       ↓
2. Local or remote?
       ↓
3. Remote → Default Gateway
       ↓
4. ARP for gateway MAC
       ↓
5. Build frame
       ↓
6. Send frame to router
       ↓
7. Router removes frame
       ↓
8. Router checks destination IP
       ↓
9. Router checks routing table
       ↓
10. Select exit interface
       ↓
11. ARP for next local destination if needed
       ↓
12. Build NEW frame
       ↓
13. Send toward destination
       ↓
14. Destination receives packet

Then the reply follows the same process in reverse.

🔥 Know These Cold for Network+

🧠 Best memory trick

IP = WHERE I'm ultimately going.

MAC = WHO I'm handing it to NEXT.

And:

Packet travels the route. Frames carry the packet one local hop at a time.

That is the core of the IP Routing Process section.