From: Adam <""4thwormcastfromthemolehill\"{at}the field.near
the bridge">

This could apply to the redhat family as well (Novell/Suse, Red Hat etc).

I will post this to the relevant people in Mandriva.

A motherboard went south taking an old Athlon 1.6 with it.

Found a sempron board which could take old std ddr ram & had 2 ide slots
& installed.

Quite staggering that linux took to a very different system with only one
minor flaw. Video, devices etc just worked. Very cool.

However...


Discovered I had eth4 & eth5 in place of eth0 & eth1. Bit of a
problem with the firewall which used eth devices as part of it's filtering.

Took one of the cards out to "clear the system", rebooted, still
with eth5 but correctly eth4 had disappeared. Put card back in & eth4
reappeared.


No biggie...crank up the network manager gui thingy &....

No way to set the eth name (i.e. set eth4 to eth0, eth5 to eth1 etc.

Found then that there was some secret recipe for attaching a eth device
name to all the relevant details (inc the mac address).

/etc/udev/rules.d/62-net.rules

# udev persistent rules for net subsystem
# Generated by Mandriva udev rules
# See /etc/udev/rules.d/62-create_persistent.rules

SUBSYSTEM=="net", ACTION=="add",
ENV{INTERFACE}!="*.*",
SYSFS{address}=="00:0e:2e:b8:c3:ce", NAME="eth0",
ENV{MDV_CONFIGURED}="yes" SUBSYSTEM=="net",
ACTION=="add", ENV{INTERFACE}!="*.*",
SYSFS{address}=="00:18:f3:68:d1:37", NAME="eth1",
ENV{MDV_CONFIGURED}="yes"


The 00:0e:2e:b8:c3:ce number in
SYSFS{address}=="00:0e:2e:b8:c3:ce" is the mac address.

Set the NAME="eth0" to the required value (in this case "eth0").

Remove all old cruft (if you've had a number of nic'es then each one is
left at present).

Oh but there's more. With the above the networking might still crash due to
modprobe settings:

In: /etc/modprobe.conf

Check the relevant eth alias points to the right device:

alias eth1 via-rhine
alias eth0 8139too

Next....

in /etc/sysconfig/network-scripts/

Check to make sure there is no excess of:

ifcfg-ethx files (e.g. you might have an excess ifcfg-eth4 file ).

That excess device may show up in the boot process anyway (it will fail upon if-up)

Make sure the settings for the eth devices you will be using are set correctly.

If Mandriva is to use these layers upon layers then fine so long as the gui
works & allows something as simple as setting a eth name against a
piece of hw.

Because you may have something as simple as :

NETWORKING=yes
GATEWAY=192.168.1.100
GATEWAYDEV=eth1
HOSTNAME=www.softfab.co.uk

Note the GATEWAYDEV=eth1

& expect to poke the traffic through a given (named) piece of h/w.

Adam

--- BBBS/NT v4.01 Flag-5