Mark Chaikelson wrote:
>
> If I'm interpreting what you said correctly ...
>
> First set up the linux gateway to receive its Internet connection (from campus) on
> eth0. Once you've tested that and ensured that your Internet connection is working
> on the Linux gateway, then set up eth1 to be some virtual ip address. For example,
> in my network, I have eth0 set up as the IP address given to me from a cable modem
> connection, and then eth1 is set to 192.168.0.1
This is good so far...
> The other computers in my network, which get their Internet connection through the
> linux gateway are 192.16.8.0.2 - 102.168.0.5.
Whoa whoa whoa WHOA!
Is there something in the water?
The first address has *5* (count 'em) octets -- that's a completely
illegal address -- and the second one has got to be a typo -- these two
addresses are on different networks.
People, *please* - if you're going to start fiddling with gateways and
masquerading, get a decent book on the fundamentals of TCP/IP first! You
can't administer a gateway server unless you do -- you're just asking
for trouble.
Let's go over it again, just to be sure.
The three private networks are, in order of size:
10.0.0.0 (class A)
172.16.0.0 (class B)
192.168.0.0 (class C (there are actually a set of them))
And yes, before everybody hollers "it was just a typo!" - typos ARE bad
because they completely confuse newbies and just create a lot of misery
for everybody.
I don't like people using anything but Class C addresses for home
networks. You do NOT need a Class A (16 MILLION addresses) network to
run 3 machines on your home LAN! If you do use one you make it much
easier to screw something up and make the whole thing not work.... and
with some people using Class Bs and some using Cs, you get people
writing this:
"Machine A has an IP of 172.168.2.10 and my gateway is 192.168.0.1 -- it
doesn't work! Please help!"
If you don't know what a network class is or what it means, or what the
difference between a network and a node address is, *get a book on
TCP/IP*.
-Stephen-
