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.

NAT is commonly used in a fashion similar <strong>to</strong> <strong>the</strong> PPP/PAT scenario by small regional<br />

ISPs <strong>to</strong> provide addressing <strong>to</strong> dedicated attachment cus<strong>to</strong>mers. The ISP designates<br />

a small block of routable addresses (instead of a single IP address), which are<br />

shared by <strong>the</strong> cus<strong>to</strong>mers'end-stations <strong>to</strong> establish Internet connections. This is an<br />

attractive approach for ISPs that typically provide mail, Web hosting, DNS, and so<br />

on for small businesses that do not have <strong>the</strong>ir own Information Technology (IT)<br />

staffs. Instead of having <strong>the</strong> ISP dedicate a large address range block from <strong>the</strong>ir<br />

(limited) registered IP address space, a small address range (typically a /28 or /29<br />

address range) is provided for host addressing through NAT. The cus<strong>to</strong>mer <strong>the</strong>n<br />

uses an unregistered Class C or Class B address range <strong>to</strong> provide local host<br />

addressing. These solutions are particularly well suited <strong>to</strong> NAT's functional design,<br />

which is geared <strong>to</strong>ward scenarios where a limited amount of hosts are<br />

communicating outside <strong>the</strong> local <strong>network</strong> at any given time.<br />

NOTE<br />

PAT uses a single public IP address <strong>to</strong> represent all <strong>the</strong> nonpublic hosts. Each<br />

nonpublic transaction originates on a different UDP/TCP port number. Therefore, it<br />

appears that <strong>the</strong> single address is <strong>the</strong> origina<strong>to</strong>r of all <strong>the</strong> requests.<br />

NAT configuration and operation are quite simple. The router is configured with an<br />

outside and inside interface. The outside interface is connected <strong>to</strong> <strong>the</strong> external<br />

Internet or intra<strong>network</strong> using a publicly routable IP address. The inside interface is<br />

connected <strong>to</strong> <strong>the</strong> local <strong>network</strong> that is using an "illegal" or unregistered address<br />

range. NAT translations replace <strong>the</strong> source address of <strong>the</strong> packet sent by an inside<br />

host with an address taken from a pool of externally valid addresses. The router<br />

keeps track of <strong>the</strong>se translations as <strong>the</strong>y occur. When a response is sent back, <strong>the</strong><br />

router replaces <strong>the</strong> incoming packet's destination address with <strong>the</strong> inside address of<br />

<strong>the</strong> host that originated <strong>the</strong> request.<br />

The fact that <strong>the</strong> router rewrites <strong>the</strong> Layer 3 addressing information contained in <strong>the</strong><br />

IP datagrams makes a NAT router distinct from a traditional router. Most routers<br />

only perform Layer 2 readdressing, which is a necessary part of <strong>the</strong> packet<br />

forwarding process.<br />

Configuring NAT<br />

Enabling NAT on a router is a three-step process:<br />

1. Creation of <strong>the</strong> address translation pool or static entries<br />

2. Creation of <strong>the</strong> ACL that specifies which inside addresses <strong>to</strong> translate<br />

3. Enabling NAT on <strong>the</strong> inside and outside interfaces

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

Saved successfully!

Ooh no, something went wrong!