read-rfc1918-for-details.iana.net : Importance of

IP addresses

If this isn't exactly what you wanted, please try our Search (there's a LOT of techy and non-techy stuff here about Linux, Unix, Mac OS X and just computers in general!):

Subject: Re: read-rfc1918-for-details.iana.net
Message-ID: <37219a1f.41719016@news.ricochet.net>
References: <debugFAK830.4Jr@netcom.com>

It happens less and less, but I still see systems where people have used public ip addresses for private networks. These systems sometimes even end up behind a NAT firewall and while they "work", problems are out there.

There are several ranges of IP addresses that you SHOULD use for internal, private networks:

• 10.0.0.1 throuugh 10.254.254.254
• 172.16.0.1 through 172.31.254.254
• 192.168.0.1 through 192.168.254.254

This is the subject of RFC-1918, Address Allocation for Private Internets

Let's say you ignore this and just arbitrarily pick some other scheme for your internal network. You have a firewall that happily maps your internal addresses to a real public address, so things do work - until you need to access a site that actually has the address range you incorrectly used for your network. Your packets won't be routed to that site at all, because they are seen by your router as being local.

The opposite side of this (what this newsgroup article references) is that if you do use the reserved private IP addresses, you can't look them up on the internet to resolve host names. You need to resolve those locally, not look to your ISP's DNS server.

Why is THAT important? Well, programs like telnetd will try to do a reverse DNS lookup when your local machines try to connect. This is often a cause for slow telnets on the local network.

From Telnet/FTP is very slow to connect: Slow telnet or ftp connections are often caused by the server wanting to do a reverse DNS lookup to find out who is connecting. If you aren't running DNS, you can fix this just by listing all the machines in /etc/hosts. Note that you don't have to be accurate about the names: I often use the ip adress with "_" substituted for the "."'s, like "host_192_168_2_3" and so on. A simple script:

#!/bin/ksh
x=1
while [ $x -lt 255 ]
do
echo "192.168.2.$x   host_$x"
x=$((x + 1 ))
done >> /etc/hosts
 

Understand that being slow to give up on name resolution is an annoyance on small networks and a Good Thing on large networks. Systems that give up quickly work well on small networks, but don't get the information they should have on larger nets.

See Networking 101.

Macworld Mac Security Superguide $9.99

Jump to Comments

Many of the products and books I review are things I purchased for my own use. Some were given to me specifically for the purpose of reviewing them. I resell or can earn commissions from the sale of some of these items. Links within these pages may be affiliate links that pay me for referring you to them. That's mostly insignificant amounts of money; whenever it is not I have made my relationship plain. I also may own stock in companies mentioned here. If you have any question, please do feel free to contact me.

Specific links that take you to pages that allow you to purchase the item I reviewed are very likely to pay me a commission. Many of the books I review were given to me by the publishers specifically for the purpose of writing a review. These gifts and referral fees do not affect my opinions; I often give bad reviews anyway.

We use Google third-party advertising companies to serve ads when you visit our website. These companies may use information (not including your name, address, email address, or telephone number) about your visits to this and other websites in order to provide advertisements about goods and services of interest to you. If you would like more information about this practice and to know your choices about not having this information used by these companies, click here.