Hi,
I got a linux fw/rtr (knoppix3.2 debian) with 3 realtek nic.
Altough it seems that linux recognizes all 3 nic on hardware and software level, it seems that 1 nic is not working, the led indicating a cnx is not giving any sign of life.
I tested the cables and the pc settings and they all seem ok to me.

lieven@Berta:~$ lspci
0000:00:00.0 Host bridge: VIA Technologies, Inc. VT82C598 [Apollo MVP3] (rev 04)
0000:00:01.0 PCI bridge: VIA Technologies, Inc. VT82C598/694x [Apollo MVP3/Pro133x AGP]
0000:00:07.0 ISA bridge: VIA Technologies, Inc. VT82C586/A/B PCI-to-ISA [Apollo VP] (rev 41)
0000:00:07.1 IDE interface: VIA Technologies, Inc. VT82C586A/B/VT82C686/A/B/VT823x/A/C PIPC Bus Master IDE (rev 06)
0000:00:07.2 USB Controller: VIA Technologies, Inc. VT82xxxxx UHCI USB 1.1 Controller (rev 02)
0000:00:07.3 Bridge: VIA Technologies, Inc. VT82C586B ACPI (rev 10)
0000:00:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
0000:00:09.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
0000:00:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
0000:01:00.0 VGA compatible controller: nVidia Corporation NV5M64 [RIVA TNT2 Model 64/Model 64 Pro] (rev 15)

lieven@Berta:~$ ifconfig
eth0 Link encap:Ethernet HWaddr 00:50:BF:97:CB:FA
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:91 errors:0 dropped:0 overruns:0 frame:0
TX packets:111 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:9605 (9.3 KiB) TX bytes:19546 (19.0 KiB)
Interrupt:11 Base address:0x6000

eth1 Link encap:Ethernet HWaddr 00:50:FC:70:25:0B
inet addr:81.83.168.149 Bcast:255.255.255.255 Mask:255.255.240.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:14028 errors:0 dropped:0 overruns:0 frame:0
TX packets:34 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:856747 (836.6 KiB) TX bytes:4071 (3.9 KiB)
Interrupt:12 Base address:0x8000

eth2 Link encap:Ethernet HWaddr 00:50:FC:A2:84:C7
inet addr:192.168.0.3 Bcast:192.168.0.255 Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:5 Base address:0xa000

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:12 errors:0 dropped:0 overruns:0 frame:0
TX packets:12 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:600 (600.0 b) TX bytes:600 (600.0 b)

Even when I put the eth2 in another network it don't work.
I think that the card is ok because I can see it in lspci and also, I can actually ping the ip 192.168.0.3 from that machine:
lieven@Berta:~$ ping -c 5 192.168.0.3
PING 192.168.0.3 (192.168.0.3): 56 data bytes
64 bytes from 192.168.0.3: icmp_seq=0 ttl=64 time=0.7 ms
64 bytes from 192.168.0.3: icmp_seq=1 ttl=64 time=0.2 ms
64 bytes from 192.168.0.3: icmp_seq=2 ttl=64 time=0.2 ms
64 bytes from 192.168.0.3: icmp_seq=3 ttl=64 time=0.2 ms
64 bytes from 192.168.0.3: icmp_seq=4 ttl=64 time=0.2 ms

I also flushed all iptables because I have a fw script but it stays dead.
iptables script
=>Then I tried changing the INTIF to eth2 but it didn't help.

Anybody sees what I'm missing? Any advice would be apreciated.
thanks,
Lieven

Hi.

Everything looks OK (although the fact that eth2 hasn't sent a single byte is a bit odd). It's a long shot, but according to PC mythology, networks cards don't play nicely with AGP cards. If one of your NICs is in the slot next to your AGP slot, try moving it.

As I said, it's a long shot. It's more likely to be a broken card or patch cable. Try removing all three cards and trying each on its own, just to make sure it's not a hardware problem

Dave

The cables are ok. I only have 3 pci slots and the slot just under the agp was already in use by the nic that connectes to my provider's cable modem. This one is working ok for some time. The middle slot was free and just below is a working nic.
I think that the new nic I inserted is faulty in some way because when I place a working nic in the middle slot, it works fine.
Now I don't understand what's wrong with it because I can actually see it with lspci and I even can give it an ip with ifconfig.
=> I'll replace it with a new one and see what happens.
thanks.

I changed the nic with a brand new one and the problem seems to be resolved. However, I had to make a lot of changes to my iptables script but I hope it's still secure. :-)

Setup:
nic1: cable modem ISP. => nat on this nic.
nic2: the new one: 192.168.1.1/24
nic3: 192.168.0.1/24

It only works when I put both nic in a different network. In the same network, it doesn't work. Anybody who knows why?

This is the current fwscript .

Is there anybody else who has a setup with three nics in one rtr/fw and who can advice on this? I would like to have both nic in the same network.

thanks in advance.
rgds,
Lieven