From: Duncan <1i5t5.duncan@cox.net>
To: gentoo-amd64@lists.gentoo.org
Subject: [gentoo-amd64] Re: persistent-net.rules
Date: Sun, 4 Mar 2007 10:04:29 +0000 (UTC) [thread overview]
Message-ID: <pan.2007.03.04.10.04.28@cox.net> (raw)
In-Reply-To: 200703040045.31686.e0026053@student.tuwien.ac.at
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
next prev parent reply other threads:[~2007-03-04 10:11 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-03 23:45 [gentoo-amd64] persistent-net.rules Bernhard Auzinger
2007-03-04 10:04 ` Duncan [this message]
2007-03-04 11:15 ` [gentoo-amd64] persistent-net.rules Bernhard Auzinger
2007-03-04 11:32 ` Duncan
2007-03-04 12:05 ` Bernhard Auzinger
2007-03-04 15:28 ` Duncan
2007-03-04 10:36 ` [gentoo-amd64] persistent-net.rules Barry Walsh
2007-03-04 11:57 ` Bernhard Auzinger
2007-03-04 12:21 ` Barry Walsh
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=pan.2007.03.04.10.04.28@cox.net \
--to=1i5t5.duncan@cox.net \
--cc=gentoo-amd64@lists.gentoo.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox