On Thu, 17 Aug 2000, Glen Lee Edwards wrote:

> I have eth0 connected to the DSL modem (Cisco 675), 10.0.0.2.  I have eth1
> connected to the LAN, 192.198.1.1x.

Are those the IP addresses of your ethernet cards, or the other machines
on the network?

> 255.255.255.0, but my LAN was inaccessible - the two client machines
> couldn't access the 'net through the Linux box.

Could your "client" machines talk to each other?  Could they ping the
Linux server's IP address?

> eth1 to 192.168.1.25 and now I have full access to the LAN (except my
> Samba server on the Linux box won't run - don't know if this is related).

It probably is related.  A lot of SMB relies on being able to broadcast
packets, and samba will probably reject your netmask since broadcast won't
make any sense.

> only change I made to get this to work was in changing the netmask.

Did you also change the netmask on the clients?  How are they configured
right now.  (IP / Netmask / Gateway)

> noticed in your example that you used the same netmask for both cards,
> which would seem to negate my theory that 2 nics in the same box must have
> different netmasks or one won't work.
> 
> Also I've been told that 192.168.1.25 isn't a legitimate netmask, but
> since the system is working I haven't changed it.

The two network cards should have different network numbers, but usually
the same netmask.  

Netmasks are composed of a number of bits which fill four bytes (32
bits) starting from the most significant bit.  That is, your netmask is a
binary number like :
11111111 11111111 11111111 000000000

This netmask (for example) has 24 bits set to 1, and is ususually referred
to as a twenty four bit netmask.  If you translate each of the bytes to
decimal, you get:
255 255 255 0

192.168.1.25 doesn't make sense as a netmask, since it looks like:
11000000 10101000 00000001 00011001
The bits don't fill from the most significant bit, and don't create a good
"mask".  This netmask will work for a few addresses, like 192.168.1.2 and
192.168.1.4, but wouldn't for 192.168.1.3.  It's just not a good thing :)

MSG




_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list

Reply via email to