R2's Routing TableSame Destinations, Different Instructions

R2's Routing TableSame Destinations, Different Instructions

[View full size image]

Like R1, to route the packet, R2 needs to compare the destination IP address of the packet to the list of destinations in the routing table. Also like R1, R2 matches its entry for network 130.4.0.0 because the destination, 130.4.3.3, is part of that network.

The difference between how R1 and R2 behave relates to the fact that unlike R1, R2's matched routing table entry does not list a next-hop router. From Figure 11-12, you can see that R2 does not need to send the packet to another router, but it should instead send the packet directly to the web server. R2 knows that there's not another router because no next-hop router is listed in the matched routing table entry. R2 simply needs to send the packet directly to the web server at IP address 130.4.3.3.