[1853] in linux-net channel archive
Re: Need help to connect to ISP!
daemon@ATHENA.MIT.EDU (Robert V. Schipper)
Mon Feb 5 10:32:27 1996
Date: Mon, 5 Feb 1996 21:56:39 +0900 (JST)
From: "Robert V. Schipper" <rvs@gol.com>
To: Todd Fries <tfries@umr.edu>
cc: linux-admin@vger.rutgers.edu, linux-net@vger.rutgers.edu
In-Reply-To: <199602042029.OAA06218@dialup-pkr-2-7.network.umr.edu>
On Sun, 4 Feb 1996, Todd Fries wrote:
> > If you have only one IP address, then you have only one machine to send
> > packets to. Ah, you say, but my machines all have different addressses,
> > 192.x.x.x. But this is where the problem is 192 is an address that can't
> > send packets outside. Anyone can construct a 192.x network (including
> > one with exactly the same addresses as you) and connect it safely to the
> > internet anywhere, but only because no gateway/router/brouter on the
> > internet will (should :-) ever transfer 192 packets, so those machines
> > can never communicate outside their network.
>
> What RFC states the use of this address? I thought that 192.168.x.x and
> 110.10.x.x were the 2 reserved networks. I didn't realize that 192.x.x.x
> was open for use...I thought I've connected to 192.x.x.x address over
> internet? Maybe I'm wrong..
All this guesswork seems rather unproductive. Therefore: RFC 1597,
aptly entitled "Address Allocation for Private Internets", states:
quote
The Internet Assigned Numbers Authority (IANA) has reserved the following
three blocks of the IP address space for private networks:
10.0.0.0 - 10.255.255.255
172.16.0.0 - 172.31.255.255
192.168.0.0 - 192.168.255.255
unquote
Much of the rest of this eight page RFC is dedicated to the proper use of
these numbers and I can recommend anyone who intends to apply them to
actually read it :-)
| Robert V. Schipper (rvs@gol.com) | Netherlands Embassy, Tokyo, Japan |
| Tel: (81)-3-37012287 | Tel: (81)-3-54010430 |
| Fax: (81)-3-37012287 | Fax: (81)-3-54010429 |
