[102204] in RedHat Linux List

home help back first fref pref prev next nref lref last post

Re: RH52, Win95/98 TCP/IP Networking Problem

daemon@ATHENA.MIT.EDU (Dave Ihnat)
Tue Dec 1 21:27:00 1998

From: ignatz@homebru.chi.il.us (Dave Ihnat)
To: redhat-list@redhat.com
Date: Tue, 1 Dec 1998 20:19:43 -0600 (CST)
In-Reply-To: <005401be1d48$1d796b60$6401a8c0@home.jdimedia.nl> from "Igmar Palsenberg" at Dec 1, 98 05:31:57 pm
Resent-From: redhat-list@redhat.com
Reply-To: redhat-list@redhat.com

Igmar Palsenberg wrote:

> Don't use these adresses. Use 10.x.x.x instead. 25.* are valid IP's, and can
> not be used internally.

Well, not to get pedantic, but...oh, WTH, yes I will.

It doesn't matter at all what you use internally as long as it doesn't get
_out_ of your internal network.  Use Lucent internal network addresses, if
you wish.  Especially if you use something like ppp and IP Masquerading
to get to the net, there will never be a problem.

BUT.  It's not a _good_ idea.  You never know when you may 'leak'.  Plus, RFC
1918 defines selected ranges of Class 'A', 'B', and 'C'network addresses that
are reserved for private network use.  These, incidentally, can be--and are--
looked for by active network elements to prevent their proliferation on the
'Net.

Another suggestion--why not stay with Class 'C' network addresses?  That's
most commonly what you'll encounter in the "real" world--or at best, Class
'B' addresses--and it'll be more familiar to you WRT netmasks, etc., if you
play in the same sandbox.

$0.02, YMMV.  Have fun.
-- 
	Dave Ihnat
	ignatz@homebru.dminet.com
	312/315.1075 [home office]


-- 
  PLEASE read the Red Hat FAQ, Tips, Errata and the MAILING LIST ARCHIVES!
		http://www.redhat.com http://archive.redhat.com
         To unsubscribe: mail redhat-list-request@redhat.com with 
                       "unsubscribe" as the Subject.


home help back first fref pref prev next nref lref last post