war eth0 v/s eth1

[agresor]

i have suse 7.0 Kernel 2.2.16
2 nic cards:
etho 90.0.0.25
eth1 90.0.0.30
for testing etho and ath1 are conected to a same switch

in the server:
ping -I 90.0.0.25 90.0.0.1 WORKS OK
ping -I 90.0.0.30 90.0.0.1 WORKS OK

on another pc in the lan:

ping 90.0.0.25 OK
ping 90.0.0.30 OK

BUT!!!!!!!!!!!

all the time eth0 make all the work, send ping as .25 and .30 an reply ping as .25 .30
the ligth of eth1 never flash!!!!!!!

??????????????????????????????????????:(

[jorey]

Just thinking out loud:
Both networkcards are in the same address range, so you don't use routing between both interfaces.
Both cards connected to the same switch?? What do you see on the switch port where eth1 is connected to?
I'm no Linux expert at all but is there a chance that Linux supports something like spanning tree? Does your switch support spanning tree btw?
Greetz
JR

[Stef]

Give us an ouput of route, and also an output of ifconfig -a. My guess is that you might have a configuration error.

Stef

[MCK-Kappeln]

hi, in my opinion its a bad idea to use the same adress range for both cards.

And its a bad idea to use a 90. adress because its no private network adress.

use 192.168.0.1 for the first card
and 192.168.10.1 for the second card
(you can only test the cards with another computer because 192.168.0.1 cannot reach 192.168.10.1 (different subnet)

but remember to use 192.168.xx.xx adresses for class C PRIVATE network
and 10.xx.xx.xx for class B Private network.

if you not use PRIVAT adresses there is a danger of you intranet traffic is routet to the outside (internet)

hope it helped, tell me if im wrong

[Stef]

That sounds about right, usually, the Linux kernel will prevent you from configuring two ethernet cards within the same network range.

If he was too change his IP's to those you stated he would be able to ping them both from the localhost :D

Stef