25.02.2013 Views

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

TCP/IP Tutorial and Technical Overview - IBM Redbooks

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The current rules are in RFC 2050, which updates RFC 1466. The reasons for<br />

the rules for the allocation of Class C network numbers will become apparent in<br />

the following sections. The use of Class C network numbers in this way has<br />

averted the exhaustion of the Class B address space, but it is not a permanent<br />

solution to the overall address space constraints that are fundamental to <strong>IP</strong>. We<br />

discuss a long-term solution in Chapter 9, “<strong>IP</strong> version 6” on page 327.<br />

3.1.6 Intranets: Private <strong>IP</strong> addresses<br />

Another approach to conserve the <strong>IP</strong> address space is described in RFC 1918.<br />

This RFC relaxes the rule that <strong>IP</strong> addresses must be globally unique. It reserves<br />

part of the global address space for use in networks that do not require<br />

connectivity to the Internet. Typically these networks are administered by a<br />

single organization. Three ranges of addresses have been reserved for this<br />

purpose:<br />

► 10.0.0.0: A single Class A network<br />

► 172.16.0.0 through 172.31.0.0: 16 contiguous Class B networks<br />

► 192.168.0.0 through 192.168.255.0: 256 contiguous Class C networks<br />

Any organization can use any address in these ranges. However, because these<br />

addresses are not globally unique, they are not defined to any external routers.<br />

Routers in networks not using private addresses, particularly those operated by<br />

Internet service providers, are expected to quietly discard all routing information<br />

regarding these addresses. Routers in an organization using private addresses<br />

are expected to limit all references to private addresses to internal links. They<br />

should neither externally advertise routes to private addresses nor forward <strong>IP</strong><br />

datagrams containing private addresses to external routers.<br />

Hosts having only a private <strong>IP</strong> address do not have direct <strong>IP</strong> layer connectivity to<br />

the Internet. All connectivity to external Internet hosts must be provided with<br />

application gateways (refer to “Application-level gateway (proxy)” on page 798),<br />

SOCKS (refer to 22.5, “SOCKS” on page 846), or Network Address Translation<br />

(NAT), which is discussed in the next section.<br />

3.1.7 Network Address Translation (NAT)<br />

This section explains Traditional Network Address Translation (NAT), Basic<br />

NAT, <strong>and</strong> Network Address Port Translation (NAPT). NAT is also known as <strong>IP</strong><br />

masquerading. It provides a mapping between internal <strong>IP</strong> addresses <strong>and</strong><br />

officially assigned external addresses.<br />

Chapter 3. Internetworking protocols 89

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

Saved successfully!

Ooh no, something went wrong!