background image
The IP Routing Process
257
21.
The payload is handed to ICMP, which understands that this is an
echo request. ICMP responds to this by immediately discarding the
packet and generating a new payload as an echo reply.
22.
A packet is then created including the source and destination address,
protocol field, and payload. The destination device is now Host A.
23.
ARP then checks to see whether the destination IP address is a device on
the local LAN or on a remote network. Since the destination device is on
a remote network, the packet needs to be sent to the default gateway.
24.
The default gateway address is found in the Registry of the Windows
device, and the ARP cache is checked to see if the hardware address
has already been resolved from an IP address.
25.
Once the hardware address of the default gateway is found, the packet
and destination hardware address are handed down to the Data Link
layer for framing.
26.
The Data Link layer frames the packet of information and includes the
following in the header:
The destination and source hardware address
Ether-Type field with IP in it
FCS field with the CRC answer in tow
27.
The frame is now handed down to the Physical layer to be sent out
over the network medium one bit at a time.
28.
The router's Ethernet 1 interface receives the bits and build a
frame. The CRC is run, and the FCS field is checked to make sure
the answers match.
29.
One the CRC is found to be OK, the hardware destination address is
checked. Since the router's interface is a match, the packet is pulled
from the frame and the Ether-Type field is checked to see what proto-
col at the Network layer the packet should be delivered to.
30.
The protocol is determined to be IP, so it gets the packet. IP runs a
CRC check on the IP header first, and then checks the destination IP
address. (Note: IP does not run a complete CRC like the Data Link
layer--it only checks the header for errors.) Since the IP destination
address doesn't match any of the router's interfaces, the routing table
is checked to see whether it has a route to 172.16.10.0. If it doesn't
Copyright ©2002 SYBEX, Inc., Alameda, CA
www.sybex.com