Please Whitelist This Site?

I know everyone hates ads. But please understand that I am providing premium content for free that takes hundreds of hours of time to research and write. I don't want to go to a pay-only model like some sites, but when more and more people block ads, I end up working for free. And I have a family to support, just like you. :)

If you like The TCP/IP Guide, please consider the download version. It's priced very economically and you can read all of it in a convenient format without ads.

If you want to use this site for free, I'd be grateful if you could add the site to the whitelist for Adblock. To do so, just open the Adblock menu and select "Disable on tcpipguide.com". Or go to the Tools menu and select "Adblock Plus Preferences...". Then click "Add Filter..." at the bottom, and add this string: "@@||tcpipguide.com^$document". Then just click OK.

Thanks for your understanding!

Sincerely, Charles Kozierok
Author and Publisher, The TCP/IP Guide


NOTE: Using software to mass-download the site degrades the server and is prohibited.
If you want to read The TCP/IP Guide offline, please consider licensing it. Thank you.

The Book is Here... and Now On Sale!

The whole site in one document for easy reference!
The TCP/IP Guide

Custom Search







Table Of Contents  The TCP/IP Guide
 9  TCP/IP Lower-Layer (Interface, Internet and Transport) Protocols (OSI Layers 2, 3 and 4)
      9  TCP/IP Internet Layer (OSI Network Layer) Protocols
           9  Internet Protocol (IP/IPv4, IPng/IPv6) and IP-Related Protocols (IP NAT, IPSec, Mobile IP)
                9  Internet Protocol Version 4 (IP, IPv4)
                     9  IP Addressing
                          9  IP "Classful" (Conventional) Addressing

Previous Topic/Section
IP Addresses With Special Meanings
Previous Page
Pages in Current Topic/Section
1
2
3
Next Page
IP Multicast Addressing
Next Topic/Section

IP Reserved, Loopback and Private Addresses
(Page 2 of 3)

Private/Unregistered/Non-Routable Addresses

Recall that in the IP address overview I contrasted private and public IP addresses. Every IP address on a IP network must be unique, and in the case of a public IP network, addresses are allocated using a central authority to ensure that there is no overlap. In contrast, if you set up a private network you can use whatever addresses you want; it's your show and nobody else has a say on what you do.

So, if this is the case, why not just pick any random block of class A, B or C addresses for your private network and use that? Well, you could; since you aren't connected to the Internet you could use, say, the class A network 18.x.x.x that is reserved on the Internet to the Massachusetts Institute of Technology (MIT). Since you aren't connected to MIT, what does it matter?

In the past, there were people who did choose to do this—and ended up regretting that decision. As the Internet grew in importance, they would later decide that such private networks needed to connect to the public Internet after all. If that happened and you had used 18.x.x.x addresses, you'd find yourself having to renumber all your devices to avoid getting a big bunch of geeks really angry. (There were in fact cases where companies that had used IP address space belonging to other companies accidentally connected those machines to the Internet, causing a small amount of ruckus in the process.)

From a more mundane standpoint, having internal devices with MIT's IP addresses is a source of confusion. It's just not a great idea to have lots of different companies “borrowing” IP addresses for their private networks.

As an alternative, RFC 1918 (superseding RFC 1597) defines a set of special address blocks that are set aside just for private addresses. These addresses simply don't exist to the public Internet. Anyone can use them with no need to contact any authority for permission. At the same time, they cannot connect to the global Internet, because routers are not programmed with entries to forward traffic with these address ranges outside of local organizations. RFC 1918 was in fact published to encourage the use of these private blocks, in order to cut down on the number of devices on the public Internet that didn't really need to be publicly-accessible. This was in response to the need to conserve the public address space.

In order to connect a network using private addressing to the public Internet, it is necessary to employ additional hardware and/or software. A gateway machine can be used as an interface between the public and private networks. Technologies such as IP Network Address Translation (NAT) are often used in conjunction with private IP addresses to allow these hosts to communicate on the public IP network.

Key Concept: Private address blocks were created to allow private IP internets to be created using addresses that were guaranteed not to conflict with public IP addresses. They are commonly used in internetworks not connected to the global Internet; devices using them can also access the global Internet by using NAT.



Previous Topic/Section
IP Addresses With Special Meanings
Previous Page
Pages in Current Topic/Section
1
2
3
Next Page
IP Multicast Addressing
Next Topic/Section

If you find The TCP/IP Guide useful, please consider making a small Paypal donation to help the site, using one of the buttons below. You can also donate a custom amount using the far right button (not less than $1 please, or PayPal gets most/all of your money!) In lieu of a larger donation, you may wish to consider purchasing a download license of The TCP/IP Guide. Thanks for your support!
Donate $2
Donate $5
Donate $10
Donate $20
Donate $30
Donate: $



Home - Table Of Contents - Contact Us

The TCP/IP Guide (http://www.TCPIPGuide.com)
Version 3.0 - Version Date: September 20, 2005

Copyright 2001-2005 Charles M. Kozierok. All Rights Reserved.
Not responsible for any loss resulting from the use of this site.