If you run "netstat -nr", then you will see which route gives you the access to the 193.200.100.X/24 net. And it's a device, not a gateway, it's eth0, so when you send a packet to eth1 (193.200.100.21), and the kernel "answer" your packet, it will use the route that let's it "reach" the 193.200.100.X/24 net, so it will use eth0. When I have to assign two or more addresses to one linux box, I use aliasing, so the same net will ever use the same eth dev. - Nestor On Tue, 11 Apr 2000, Paul wrote:
Good afternoon,
Trying to configure three network cards in SuSE 6.2
It looks like when we ping another machine on the network it works fine when the CAT 5 cable is plugged into ether0 using ping -I193.200.100.20 (ether0 IP address) other machine name.
When we try the same test with the cable plugged into the second NIC ether1 (193.200.100.21), it fails. However, when we look at the LED's on the NIC's when performing the second test, the LED's on NIC ether0 are the lights blinking.
It looks like the Linux machine does not understand the MAC to IP address. Also RARP is not supported with this kernel S.u.S.E. 6.2
Does SuSE 6.2 support multiple NIC's? If so any help would be appreciated.
Paul Frankfurter
-- To unsubscribe send e-mail to suse-linux-e-unsubscribe@suse.com For additional commands send e-mail to suse-linux-e-help@suse.com Also check the FAQ at http://www.suse.com/Support/Doku/FAQ/