Leonard,
Believe it or not it worked. I found out part of the problem is that
linuxconf isn't deleting old routes when I make changes to the LAN/WAN.
Apparently using 192.168.1.25 on the new route gave the three boxes a
distinctive address so the kernel was able to distinguish them from the
old routes which weren't supposed to be there.
In any case, I manually deleted the obsolete routes, changed the
netmasking as follows:
192.168.1.1X 255.255.255.0
10.0.0.0 255.0.0.0
Now all is well (except the Samba server is still down).
BTW, I don't drink, it was a desperate attempt at trying to fix that
which had no apparent cure. {-_o}
Glen
On Fri, 18 Aug 2000, Leonard den Ottolander wrote:
> Hello Glen,
>
>> To give this letter some technical value: if some of you are having
>> trouble with 2 or more nic cards with 1 or more networks not accessible,
>> make sure you have a different netmask for each network your computer is
>> trying to access. I was running 255.255.255.0 for both eth0 and eth1. I
>> couldn't access anything on eth1 until I changed my netmask to
>> 192.168.1.25. Now both my WAN and LAN work great.
>
> ??? Different netmasks? Netmask 192.168.1.25? You must be drunk ;-). Please
>tell us again what you mean.
>
> CUO,
>
> Leonard.
>
>
>
>_______________________________________________
>Redhat-list mailing list
>[EMAIL PROTECTED]
>https://listman.redhat.com/mailman/listinfo/redhat-list
>
_______________________________________________
Redhat-list mailing list
[EMAIL PROTECTED]
https://listman.redhat.com/mailman/listinfo/redhat-list
