NIC's do not working on F-7

[Walius]

Hi, i have here a little problem, in my desktop are 3 NIC's 1- internet 2- LAN
when im starting my fedora 7 the network led's is not turned on on both LAN interfaces, but network-config says that those connections are enabled :confused: :confused: and thats not all: my friends on LAN usink windows and the windows network manager says that "the cable is plugged out" but the cable is REALY plugged in. When im starting the windows, after fiew seconds the led's on LAN NIC's turns on, and network is up. On earlier fedora releases ive not experienced this problem...

now using F7 2.22.9 kernel i686

[jrmotr]

I'm having very similar problems myself.

I have 2 NICs (eth0 and eth1) in an F7 box.

I cannot get both cards to be active unless I switch off the Network Manager service.
Then, however, I can't see the LAN - no W2k machine and no Linux/Samba shares on the gateway Fed 7 machine.

I'll follow your post - hopefully you or I get a solution !

[Walius]

OK, it will be nice to solve this problem....

[Brian1]

Maybe posting the nics brand, model, version would be a start.
Output from the following commands. Just post the info pertaingin to the devices.
/sbin/lspci -v
/sbin/ifconfig -a

I am guessing each one is eth0, eth1, and eth2. If so post the contents of matching name files replace x with the interface number. /etc/sysconfig/network-scripts/ifcfg-ethx

Now have you setup ip Masquerading to allow the two lans to get to the Internet nic?
Can you get to the internet from the machine?
Is the cable plugged into the correct nic that will be seen as the one for the Internet nic?
The kernel can handle the PCI assigning a few different ways so you may be thinking one nic is the Internet nic and is actually one of the others.
Assigning can be done two different ways. You may be able to define and alias in /etc/modprobe.conf but if two or more nics are the same brand then it still will rely on PCI assigning.
You can set some udev rules defining the mac address to be this alias. http://www.linuxquestions.org/questions/linux-networking-3/suddenly-nic-names-change-594308/?highlight=KERNEL+eth+SYSFS+address

Brian

[Brian1]

Does the Internet interface work?
Only enable the setup for this nic and get it working then start adding the others.
Do Not set a gateway on the other 2 lan nics if you plan to allow them to have internet access. IP Masquerading handles the routing for you on this.

Brian

[Walius]

As you asked:


[root@m-G5 ~]# /sbin/ifconfig -a
eth0 Link encap:Ethernet HWaddr 00:0E:2E:8C:73:AC
inet addr:192.168.0.1 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::20e:2eff:fe8c:73ac/64 Scope:Link
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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:21 Base address:0x2400

eth1 Link encap:Ethernet HWaddr 00:E0:4C:15:65:A3
inet addr:192.168.0.2 Bcast:192.168.0.255 Mask:255.255.255.0
inet6 addr: fe80::2e0:4cff:fe15:65a3/64 Scope:Link
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:1000
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
Interrupt:22 Base address:0x4000

eth2 Link encap:Ethernet HWaddr 00:19:66:30:01:3F
inet addr:10.250.34.104 Bcast:10.250.35.255 Mask:255.255.252.0
inet6 addr: fe80::219:66ff:fe30:13f/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:1334 errors:0 dropped:0 overruns:0 frame:0
TX packets:1382 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:479056 (467.8 KiB) TX bytes:256625 (250.6 KiB)
Interrupt:16

lo Link encap:Local Loopback
inet addr:127.0.0.1 Mask:255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets:6355 errors:0 dropped:0 overruns:0 frame:0
TX packets:6355 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:0
RX bytes:43940965 (41.9 MiB) TX bytes:43940965 (41.9 MiB)


[root@m-G5 ~]# /sbin/lspci -v

--------//----------

00:0a.0 Ethernet controller: nVidia Corporation Unknown device 054c (rev a2)
Subsystem: ASRock Incorporation Unknown device 054c
Flags: bus master, 66MHz, fast devsel, latency 0, IRQ 216
Memory at fea7c000 (32-bit, non-prefetchable) [size=4K]
I/O ports at d480 [size=8]
Memory at fea7e400 (32-bit, non-prefetchable) [size=256]
Memory at fea7e000 (32-bit, non-prefetchable) [size=16]
Capabilities: [44] Power Management version 2
Capabilities: [50] Message Signalled Interrupts: Mask+ 64bit+ Queue=0/3 Enable+
Capabilities: [6c] HyperTransport: MSI Mapping

---------//-----------------------

01:08.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 32, IRQ 21
I/O ports at e800 [size=256]
Memory at febff400 (32-bit, non-prefetchable) [size=256]
Capabilities: [50] Power Management version 2

01:0a.0 Ethernet controller: Realtek Semiconductor Co., Ltd. RTL-8139/8139C/8139C+ (rev 10)
Subsystem: Realtek Semiconductor Co., Ltd. RT8139
Flags: bus master, medium devsel, latency 32, IRQ 22
I/O ports at e400 [size=256]
Memory at febff000 (32-bit, non-prefetchable) [size=256]
Expansion ROM at 40000000 [disabled] [size=64K]
Capabilities: [50] Power Management version 2





Yes i have internet on eth2 (nVidia) but lan nics (eth0, eth1) seems to be not working on linux, first of all i need to set these interfaces up, then i'll make a bridge with bridge-utils and share internet.

As i sayed, eth0 and eth1 not working on F-7, when im restarting to Win XP it works normally, and the internet is shared.
That where the problem is, why these interfaces not working on linux???

[Walius]

Also ive noticed the message, when linux starts:
"PCI:BIOS BUG: MCFG area at f0000000 is not E820-reserved
PCI: Not using MMCONFIG"

the boot option "pci=nommconf" helps to rid of this message, but no network led on my neibor PC flashes on, when the interface is bringet up...

[Brian1]

So eth2 works and it can get to the internet?
Now I never setup bridging, just simple masquerading as far as get network traffic to get to eth2.

Brian

[jrmotr]

Hi there,

The following is a possible solution for you to try.

1) Install Firestarter firewall - make sure no other firewall is running.
2) Permanently switch off Network Manager / Network Manager Dispatcher services.
(Network Manager sometimes does not co-exist well with multiple NICs)
3) Make sure all NICs are in and connected - re-start your machine.
4) Run the setup wizard in Firestarter and modify the firewall where necessary.

It has taken me a long time to suss this one out but it works a treat.

jrmotr

[Walius]

Network Manager and Network Manager Dispatcher services are not running, and firestarter is installed, it seems that fedora cannot properly bring eth0 and eth1 up... these mentioned services starting after that, when these interfaces must be bringed up :(

bringing up eth0.... [ok]
bringing up eth1... [ok]

but winXP on the oder side of both interfaces keep saying that "cable is unplugged" and the LED of friend PC not flashing....

[Walius]

OK ive noticed, that when im physicaly removing my eth0 then all works fine.... this is very odd, but maybe this will help for someone :)

[Brian1]

Are you connecting machines directly to these nics?
If so you need to use crossover network cables.
If each are connected to hubs or switches then regular cable is correct.

Brian

[Walius]

the cable is correct, i repeating, when i booting winXP on same machine, all works great...

[Brian1]

No idea as to what is needed.

Brian

[jrmotr]

Try the Firestarter method again - this time put just 1 NIC in (say the internet connection) - try getting that up and running.
Then put in the 2nd NIC and configure that - all being well, try the 3rd.

If you're using Firestarter, you don't need anything else (i.e. bridging tools) to get the network running.

BTW - I noticed in your "lspci" output, there was an IRQ of 216 for (I presume) the eth0 card - can you verify that all is well in that department.

[jrmotr]

One more thing to check............

Make sure that the MAC addresses (you'll find this in System/Network Configurator) correspond correctly to each NIC.