>The destination 0.0.0.0 indicates the default route. It does NOT override,
it
>is just used if a specific route is not found. In the example, all traffic
from
>this machine sent to anything but 192.168.1.0 will end up going to eth1.
Good. This was the behaviour I was hoping for. It's nice to find an
intelligent
OS for once. I set this up last night *hoping* it would act this way, and
it
seems to work, so all's well so far... Tonight I finish the config and test
the ip masq from our LAN.
>One thing you do need to be careful about is which card is eth0 and which
is
>eth1. It is not always the way you expect. You can usually tell by looking
>carefully at the output of ifconfig (I think it reports interrupts) or if
in
>doubt, ping something and see which lights flash.
Now this has bothered me. I have to watch the boot sequence or check the
boot
logs to see which one has config info for a PCI card, then I know which
card is which (the other is ISA). Is there some sort of device manager for
Linux that can identify your hardware? If ifconfig does report IRQ and
?port address? settings (IIRC), but I didn't check them before I installed
the cards. They both work, so Linux must have found the correct settings,
but
there has to be a better way to tell which card is which. Does anyone know
how
to do this?
P.S. Justin, here's something for ya, my roommate and I recently threw a
LAN party (kudos to DJ Graham for helping with the LAN config and providing
hardware for a dedicated server...) and we're thinking of possibly throwing
another one soon or making it a monthly event. When we do would you like an
invite?
-----------------------------------------------
Joe Duncan
Systems
Human Resources Development Canada
(613)997-7986
[EMAIL PROTECTED]
-----------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
For daily digest info, email [EMAIL PROTECTED]
