[gentoo-amd64] persistent-net.rules

[gentoo-amd64] persistent-net.rules

[Bernhard Auzinger]

Hi,

does somebody know how to prevent the persistent-net.rules to be saved during 
the shutdown process?

The background is that I have a network interface with a faulty mac adress 
(FF:FF:FF:FF:FF:FF) on a K8N Neo2 (nforce3 ultra). So the kernel applys a 
random mac address to the network interface on every boot. At the shutdown 
process a entry with the randomly generated mac address will be written 
into /etc/udev/rules.d/70-persistent-net.rules. And that's my problem, 
because at the next boot another mac address will be applied to the network 
interface which does not match the one saved to persistent-net.rules and udev 
does not provide an interface eth0.

rgds
Bernhard
-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: persistent-net.rules

[Duncan]

Bernhard Auzinger <e0026053@student.tuwien.ac.at> posted
200703040045.31686.e0026053@student.tuwien.ac.at, excerpted below, on 
Sun, 04 Mar 2007 00:45:31 +0100:

> does somebody know how to prevent the persistent-net.rules to be saved
> during the shutdown process?
> 
> The background is that I have a network interface with a faulty mac
> adress (FF:FF:FF:FF:FF:FF) on a K8N Neo2 (nforce3 ultra). So the kernel
> applys a random mac address to the network interface on every boot. At
> the shutdown process a entry with the randomly generated mac address
> will be written into /etc/udev/rules.d/70-persistent-net.rules. And
> that's my problem, because at the next boot another mac address will be
> applied to the network interface which does not match the one saved to
> persistent-net.rules and udev does not provide an interface eth0.

Interesting.  I have different hardware, but use the macchanger module to 
change my MAC at every eth0 up, and don't have the problem here.  udev 
must see the original MAC address on my hardware before macchanger gets 
to it, and thus set it up correctly.  But if it's rewritten @ shutdown, 
why wouldn't it see the macchanger-randomized one then and thus get it 
wrong?

So... three suggestions.  One, see if emerging macchanger and configuring 
it will cure the problem.  Maybe the system expects it if maccchanger is 
used thus explaining why it works with it here and providing a way to 
make it work there?  Two, consider tweaking the related variables 
(RC_HOTPLUG, RC_COLDPLUG, RC_PLUG_SERVICES) in /etc/conf.d/rc, and see if 
you can udev to play nicely that way.  (Here, I have RC_PLUG_SERVICES="!
nt.eth0", allowing me better control of when it goes up, but it generally 
works without that, I just like and occasionally need the additional 
control.)  Three, you may have to put a manual mknode somewhere in your 
scripts.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: persistent-net.rules

[Bernhard Auzinger]

> Interesting.  I have different hardware, but use the macchanger module to
> change my MAC at every eth0 up, and don't have the problem here.  udev
> must see the original MAC address on my hardware before macchanger gets
> to it, and thus set it up correctly.  But if it's rewritten @ shutdown,
> why wouldn't it see the macchanger-randomized one then and thus get it
> wrong?
>

I've tried macchanger but the thing is that at boottime the address of my 
network interface is always FF:FF:FF:FF:FF:FF and therefore it gets a random 
mac-address from the kernel. And because of the persistent-net.rules that are 
saved at shutdown, my network interface is named something unpredictable. 
Only if I delete the udev rule by plugging it to another computer to be able 
to boot without persistent-net.rules I get a interface eth0. Otherwise it 
increments every boot (eth0, eth1, . . . ).

The funny thing is, that no matter which mac address I apply to the interface 
with macchanger, the mac address which will be written to the udev rules at 
shutdown is always the one randomly generated by the kernel and not the one I 
apply to it.

rgds
Bernhard


-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: persistent-net.rules

[Duncan]

Bernhard Auzinger <e0026053@student.tuwien.ac.at> posted
200703041215.43076.e0026053@student.tuwien.ac.at, excerpted below, on 
Sun, 04 Mar 2007 12:15:42 +0100:

> The funny thing is, that no matter which mac address I apply to the
> interface with macchanger, the mac address which will be written to the
> udev rules at shutdown is always the one randomly generated by the
> kernel and not the one I apply to it.

Well, at least that explains why it isn't affecting me.  If it's ignoring 
the macchanger set MAC, my setup wouldn't be affected.

Hopefully Barry's BIOS suggestion helps.  If not, yet another suggestion 
would be to find what's doing the write at shutdown and either directly 
edit it or create a script that runs after it that rewrites or removes 
the problem file.

Right now, I'm frustrated with you. =8^(  Hope you get it working, 
however you do it!

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: persistent-net.rules

[Bernhard Auzinger]

> Only if I delete the udev rule by plugging it to another
> computer to be able to boot without persistent-net.rules I get a interface
> eth0. Otherwise it increments every boot (eth0, eth1, . . . ).

just for the sake of completeness. I forgot to write "hard disk" in the 
sentence above :).

"by plugging the hard disk to another computer"

rgds
Bernhard

-- 
gentoo-amd64@gentoo.org mailing list

[gentoo-amd64] Re: persistent-net.rules

[Duncan]

Bernhard Auzinger <e0026053@student.tuwien.ac.at> posted
200703041305.04764.e0026053@student.tuwien.ac.at, excerpted below, on 
Sun, 04 Mar 2007 13:05:04 +0100:

>> Only if I delete the udev rule by plugging it to another computer to be
>> able to boot without persistent-net.rules I get a interface eth0.
>> Otherwise it increments every boot (eth0, eth1, . . . ).
> 
> just for the sake of completeness. I forgot to write "hard disk" in the
> sentence above :).
> 
> "by plugging the hard disk to another computer"

=8^)  I noticed that, had to pause and re-parse a bit, but finally 
decided hard drive was about all that made sense in context.

-- 
Duncan - List replies preferred.   No HTML msgs.
"Every nonfree program has a lord, a master --
and if you use the program, he is your master."  Richard Stallman

-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] persistent-net.rules

[Barry Walsh]

Bernhard Auzinger wrote:
> Hi,
>
> does somebody know how to prevent the persistent-net.rules to be saved during 
> the shutdown process?
>
> The background is that I have a network interface with a faulty mac adress 
> (FF:FF:FF:FF:FF:FF) on a K8N Neo2 (nforce3 ultra). So the kernel applys a 
> random mac address to the network interface on every boot. At the shutdown 
> process a entry with the randomly generated mac address will be written 
> into /etc/udev/rules.d/70-persistent-net.rules. And that's my problem, 
> because at the next boot another mac address will be applied to the network 
> interface which does not match the one saved to persistent-net.rules and udev 
> does not provide an interface eth0.
>
> rgds
> Bernhard
>   
Possibly a fix for the MAC address,  on the BIOS screen, press shift+f2 
then alt+f3 which should reveal extra settings, including the option to 
enter your own choice of MAC address for the nVidia adapter. The 
original mac address should be on a sticker above the paralell port. You 
don't mention which K8N neo2, so you may have two onboard NICs, and the 
stickers MAC address will only be for one of them, the other being a 
digit lower.
-- 
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] persistent-net.rules

[Bernhard Auzinger]

> Possibly a fix for the MAC address,  on the BIOS screen, press shift+f2
> then alt+f3 which should reveal extra settings, including the option to
> enter your own choice of MAC address for the nVidia adapter. The
> original mac address should be on a sticker above the paralell port. You
> don't mention which K8N neo2, so you may have two onboard NICs, and the
> stickers MAC address will only be for one of them, the other being a
> digit lower.

You are amazing. I have my mac address back again :). Thank you very much. 
From where do you know these shortcuts to get extra options in the bios menu? 
Is there a specification available? My Mainboard is a K8N Neo2 Platinum 
(MS-7025).

Thank you very much, both of you.

rgds
Bernhard
--
gentoo-amd64@gentoo.org mailing list

Re: [gentoo-amd64] persistent-net.rules

[Barry Walsh]

Bernhard Auzinger wrote:
>> Possibly a fix for the MAC address,  on the BIOS screen, press shift+f2
>> then alt+f3 which should reveal extra settings, including the option to
>> enter your own choice of MAC address for the nVidia adapter. The
>> original mac address should be on a sticker above the paralell port. You
>> don't mention which K8N neo2, so you may have two onboard NICs, and the
>> stickers MAC address will only be for one of them, the other being a
>> digit lower.
>>     
>
> You are amazing. I have my mac address back again :). Thank you very much. 
> From where do you know these shortcuts to get extra options in the bios menu? 
> Is there a specification available? My Mainboard is a K8N Neo2 Platinum 
> (MS-7025).
>
> Thank you very much, both of you.
>
> rgds
> Bernhard
>   
I know this only because the same MAC issue happened to me after a BIOS 
flash.
-- 
gentoo-amd64@gentoo.org mailing list