09.12.2012 Views

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

Understanding the network.pdf - Back to Home

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

1. The Layer 3 <strong>to</strong> Layer 2 address mapping lookup is complete.<br />

2. The IP datagram is placed in <strong>the</strong> Layer 2 packet.<br />

3. The datagram is forwarded directly <strong>to</strong> <strong>the</strong> destination host.<br />

If <strong>the</strong> datagram's destination is remotely connected:<br />

NOTE<br />

1. The Layer 3 <strong>to</strong> Layer 2 address mapping lookup is complete.<br />

2. The IP datagram is placed in <strong>the</strong> Layer 2 packet.<br />

3. The datagram is sent directly <strong>to</strong> default gateway.<br />

Every time an IP datagram is forwarded, <strong>the</strong> host/router must perform a route<br />

lookup <strong>to</strong> determine <strong>the</strong> next hop. This is done so <strong>the</strong> best route will be used <strong>to</strong><br />

deliver <strong>the</strong> IP datagram. Although this might seem like a waste of time on an<br />

E<strong>the</strong>rnet <strong>network</strong> where each subnet is connected by only one E<strong>the</strong>rnet interface, it<br />

is not a waste of time where <strong>the</strong>re is a choice between sending <strong>the</strong> datagram over<br />

a 56K ISDN dial-up link or a TI dedicated link. Because IP has no knowledge of <strong>the</strong><br />

Layer 2 transport, it handles all datagrams <strong>the</strong> same way.<br />

It is important <strong>to</strong> keep in mind that IP datagram delivery is a Layer 2 and Layer 3<br />

activity. The IP pro<strong>to</strong>col is uninterested in <strong>the</strong> actual physical layer transport. This<br />

gives IP <strong>the</strong> flexibility <strong>to</strong> send datagrams across any physical transport medium,<br />

provided <strong>the</strong>re is a means <strong>to</strong> provide physical transport (OSI Layer 2) <strong>to</strong> <strong>network</strong><br />

(OSI Layer 3) address mapping. The address resolution pro<strong>to</strong>col is <strong>the</strong> most<br />

common example of this service and is used with most Layer 2 LAN pro<strong>to</strong>cols<br />

(E<strong>the</strong>rnet, FDDI, and so on). ARP, as you recall from <strong>the</strong> earlier discussion, provides<br />

<strong>the</strong> mapping service used <strong>to</strong> map <strong>the</strong> Layer 3 addresses <strong>to</strong> Layer 2 addresses.<br />

Mapping is needed because <strong>the</strong> Layer 2 address is only valid for <strong>the</strong> physical<br />

transport segment <strong>to</strong> which <strong>the</strong> source host (and, in <strong>the</strong> case of local delivery, <strong>the</strong><br />

destination host) is attached. In o<strong>the</strong>r words, <strong>the</strong> Layer 2 address associated with<br />

an IP datagram changes each time <strong>the</strong> IP datagram is moved between intermediate<br />

points. The Layer 3 addresses, however, are always valid. They never change,<br />

except in <strong>the</strong> case where a proxy host or NAT service is used.<br />

The dependency on both Layer 2 and Layer 3 addressing for IP datagram delivery<br />

can sometimes be confusing. It's important <strong>to</strong> be clear about <strong>the</strong> IP delivery models<br />

and <strong>the</strong> roles that <strong>the</strong> Layer 2 and Layer 3 addressing play.<br />

• In instances where local delivery is used, <strong>the</strong> source and destination<br />

hosts'Layer 2 and Layer 3 addresses correspond <strong>to</strong> one ano<strong>the</strong>r because <strong>the</strong><br />

delivery is local.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!