|
IP Addressing for Private Networks
If you
are designing an IP addressing scheme for your organization's
internal network, you have some addressing flexibility that you
would not have if you were designing a network that touches the
public Internet. Some special addresses have been made available for
use in private networks.
The
Internet Assigned Numbers Authority (IANA) in RFC 1597 (and more
recently in RFC 1918) set aside specific network addresses for use
in private networks in order to preserve the remaining pool of
public addresses. These are:
- 10.0.0.0 - 10.255.255.255 (1 Class A network
address)
- 172.16.0.0 - 172.31.255.255 (16 Class B network
addresses)
- 192.168.0.0 - 192.168.255.255 (255 Class C network
addresses)
The
above addresses are not used anywhere on the public Internet. You
may use them for your organization's private internal network
without registration or special permission. As long as your network
remains isolated from the public Internet (and from other networks
that use the same addresses), the RFC1918 addresses may be shared by
many organizations. Internet connectivity can still be accomplished
through the use of Network Address Translation (NAT) and other
techniques.
There
are several advantages to using the RFC 1918 addresses on your
private network. An additional measure of security is provided for
your network because TCP/IP data frames containing private addresses
are not forwarded by backbone routers on the public Internet.
Additional subnetting flexibility is available to you because you
have available a much larger number of host and subnet addresses.
You can, for example, dedicate an entire Class A address (or
multiple Class B addresses) to your internal network. It is highly
unlikely that you could procure your own publicly-registered Class A
or B address at this time.
There
are many benefits to designing your internal network using RFC 1918
IP addresses. Give ITS Networking Services a call to see how they
might be used on your network. |