> eth0 irq 3 i/o 0x300 192.168.110.11 Bcast 192.168.110.255 Mask 255.255.255.0
> route 192.168.110.0
>
> eth1 irq 9 i/o 0x260 192.168.110.12 Bcast 192.168.110.255 Mask 255.255.255.0
> route 192.168.110.0
>
> At this point eth1 is in use, eth0 is not working.
Ah, I think the problem is that both NICs are on the same subnet.
It's funny, I had this discussion last Saturday at my local LUG...
Since both NICs are on the same subnet, the kernel cannot know
which one you want to send the pings out on. If you try pinging the IP
address "192.168.110.15", should the kernel send that ping out through
eth0 or should it send it out through eth1? There's no way to tell,
because there is no routing information that identifies which NIC
(interface) to send the packet out on. Did you mean for that ping packet
to come from the IP address 192.168.110.11? Or did you mean for that ping
packet to come from 192.168.110.12? Apparantly, the kernel just
arbitrarily chooses the last one you configured.
If you need multiple IP address on the same subnet, you use
"sub-interfaces" (I am sorry--I do not know what the correct term is, so I
made up the word sub-interfaces). Basically, you configure a single NIC
to have multiple separate IP addresses, as in:
ifconfig eth0:0 192.168.0.1
ifconfig eth0:1 192.168.0.2
ifconfig eth0:2 192.168.0.15
ifconfig eth0:3 192.168.0.249
...etc...
That way your computer can have the IP address 192.168.110.11 AND
192.168.110.12, and will respond to pings to either IP address (since all
pings are coming in to the same NIC).
If you want to use both NICs in your computer, try giving them
separate sub-nets and make sure your routing table lets the two sub-nets
talk to one another. Then you should be able to ping one NIC from the
other.
Good Luck,
Derek Simkowiak
[EMAIL PROTECTED]
