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.

IP also supports a facility for hosts <strong>to</strong> masquerade and accept IP packets on behalf<br />

of o<strong>the</strong>r hosts. This is known as Proxy ARP. Proxy ARP is used in situations where<br />

sending hosts are unable <strong>to</strong> determine that IP routing is required. Proxy ARP maps<br />

one or more <strong>network</strong> prefixes <strong>to</strong> a physical E<strong>the</strong>rnet address. This permits <strong>the</strong> host<br />

running Proxy ARP <strong>to</strong> answer all ARP requests made for <strong>the</strong> IP <strong>network</strong> for which it<br />

acts as proxy. Proxy ARP is a limited type of routing and is rarely found in modern<br />

<strong>network</strong>s. Its original intent was <strong>to</strong> assist in situations where host IP<br />

implementations were limited and <strong>to</strong> provide <strong>the</strong> ARP facility for<br />

non-ARP-compatible transport links.<br />

With local datagram delivery, <strong>the</strong> Layer 2 pro<strong>to</strong>col handles most of <strong>the</strong> work. IP and<br />

its supporting pro<strong>to</strong>cols act as address translation mechanisms that assist Layer 2 in<br />

identifying <strong>the</strong> source and destination hosts for <strong>the</strong> delivery of <strong>the</strong> ULP data. The<br />

main function of IP (and all o<strong>the</strong>r Layer 3 pro<strong>to</strong>cols) is <strong>to</strong> provide a common<br />

transmission interface between <strong>the</strong> ULP and <strong>the</strong> Layer 2 transmission medium. This<br />

function is essential in order for hosts <strong>to</strong> have <strong>the</strong> capability <strong>to</strong> exchange data<br />

independent of <strong>the</strong> actual transmission pro<strong>to</strong>col. The utilization of this common<br />

interface makes it possible for <strong>the</strong> exchange of data <strong>to</strong> occur over different<br />

transmission mediums utilizing different addressing, data encoding, and<br />

transmission schemes. In a LAN environment, this is often not a large concern<br />

because one transmission medium is used <strong>to</strong> connect <strong>the</strong> different hosts on <strong>the</strong><br />

<strong>network</strong>. However, when data needs <strong>to</strong> be delivered <strong>to</strong> a host beyond <strong>the</strong> local<br />

<strong>network</strong>, a remote delivery model comes in<strong>to</strong> play. Remote datagram delivery<br />

involves <strong>the</strong> possible use of different Layer 2 transmission pro<strong>to</strong>cols and <strong>the</strong> need<br />

for a mechanism for determining how <strong>to</strong> reach <strong>the</strong> remote host, known as routing.<br />

IP Header<br />

Now that you have an understanding of IP datagram delivery and its interaction with<br />

<strong>the</strong> Layer 2 pro<strong>to</strong>col, let's look at how <strong>the</strong> IP header is structured. An IP header is<br />

appended <strong>to</strong> each actual upper layer pro<strong>to</strong>col message that needs <strong>to</strong> be delivered<br />

across <strong>the</strong> <strong>network</strong>. In most cases, <strong>the</strong> IP header and its various parts have little<br />

effect on your environment beyond delivering your IP data. But, understanding <strong>the</strong><br />

parts of <strong>the</strong> IP header gives you insight in<strong>to</strong> how IP works in general. Figure 2.2<br />

illustrates <strong>the</strong> different data fields that make up <strong>the</strong> IP header, followed by a brief<br />

description of each field's function.

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

Saved successfully!

Ooh no, something went wrong!