Network cards are reversing

[Damase]

With kernel 2.6.23.?-42 my via built in card (is unreliable, I don't use it) is eth0 and d-link is eth1, and I can use my network flawlessly.

With kernel 2.6.24.3-34 my via is eth1 and d-link is eth0, and it will not connect, it thinks there isn't even a cable attached. When I told it to use eth1.bak it complained of an error and wouldn't alter the configuration.

Since I am brand new to Fedora and really have very little experience with linux in general I need to know where to look for these configuration files to begin with and hopefully I can tell the computer manually what eth belongs to what.

TIA

[stevea]

It sounds like the device names (eth0/eth1) got switched around. Read the MAC address off of one of the interfaces (HWAddr: if you type ifconfig -a). so you can tell which is which.

This is controlled in two places. The file
/etc/udev/rules.d/70-persistent-net.rules
should associate a MAC adddess with an interface name (ethN) as the drivers are initialized in the kernel.

When you bring the interface up and configure it the driver loaded is associated in /etc/modprobe.conf,
Also the ifrename command lets you toggle the interface names around too.

Then the ifcfg-ethN files in /etc/sysconfig/networking/devices are names for each interface, but they *may* reference the worng interface/driver.


One of these associations is wrong. Confusing huh ?

[Damase]

Originally Posted by stevea

I
One of these associations is wrong. Confusing huh ?

yup, but I'll take my time and sort thru it. So, I will look for mac address assignments while in kernel 2.6.23.?-42, then match them in all those places after I boot using kernel 2.6.24.3-34. Correct?

[Damase]

I cannot find what is causing the problem. But I can use the GUI network interface to fix the problem but as soon as I reboot, or log off It undoes the fix and goes back to being broken. I'll tell how I fix it and maybe someone knows by that process what is going wrong.

Going into System>>Administration>>Network...type in root password...click on Hardware tab change d-link to eth1 and via to eth0 click File>>Save..Click Ok then click Devices tab highlight "eth1.bak" (that's it's nickname)...click "Activate" and then click File>>Save...Ok and exit. Ta da!! network fixed (temporarily). It has to be done in this order or it will not fix as well.

The problem is it doesn't stay fixed and it's not creating the regular files, and I don't their suffixes and the suffixes were not revealed to me in the files when I boot the other kernel. I used ls to see what was in /etc/sysconfig/networking/devices and in /etc/udev/rules.d/70-persistent-net.rules

The only difference between these was in /etc/sysconfig/networking/devices
kernel 2.6.23.1-42 had ifcfg-eth0 ifcfg-eth0.bak ifcfg-eth1 ifcfg-eth1.bak (this is the one that works)
kernel 2.6.24.3-34 had ifcfg-eth0.bak ifcfg-eth1.bak

All the files had d-link as eth1 and via as eth0; so I am lost as to why it is continuing to try to have them the opposite way

TIA

[PabloTwo]

If you truly don't ever use the built in via ethernet device, you can most likely just go into the bios and disable it there. Once it's been disabled in the bios, the OS won't ever see it and only the D-link card will be recognized and be set to eth0 every time.

Paul

[Damase]

You helped me out, just didn't work the way we would have expected it to. Disabled via ethernet in the BIOS, upon restart it still wanted to use the .bak files. so I deleted those and it still didn't like using eth0. So , I deleted everything reboot then it had just the d-link on eth1, then I was able to create a new device file with just that and reboot again and ta da --it works!! (so what if it wants to be eth1). I should of remembered that was on. When windows was on this machine it would crash at the BIOS level and I would have to go thru and redo my BIOS. There was always something to forget, and that was one of them.

Anyways thank you very much