From: "Alexander E. Patrakov" <patrakov@gmail.com>
To: linux-hotplug@vger.kernel.org
Subject: locally-administered MAC addresses create stupid rules
Date: Mon, 19 Nov 2007 04:45:30 +0000 [thread overview]
Message-ID: <fhr4de$lfb$1@ger.gmane.org> (raw)
Hello,
the default persistent network rules generator in udev-117 creates this stupid
rule for a network card with a locally-administered MAC address:
SUBSYSTEM="net", ACTION="add", ATTR{type}="1", NAME="eth0"
(to reproduce: kvm -net nic,macaddr#:45:67:89:ab:cd -hda hda.dsk)
This generated rule is stupid, because it matches every ethernet card. The logic
that strips out locally-administered MAC addresses from the match should be
revised, but I don't know how to do it properly. If we just remove the generated
rule, we'll possibly end up with a random name (e.g., eth0) for this network
card and a eth0_rename name for a conflicting interface that should really be
eth0 according to the other rules.
--
Alexander E. Patrakov
-------------------------------------------------------------------------
This SF.net email is sponsored by: Microsoft
Defy all challenges. Microsoft(R) Visual Studio 2005.
http://clk.atdmt.com/MRT/go/vse0120000070mrt/direct/01/
_______________________________________________
Linux-hotplug-devel mailing list http://linux-hotplug.sourceforge.net
Linux-hotplug-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linux-hotplug-devel
next reply other threads:[~2007-11-19 4:45 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-19 4:45 Alexander E. Patrakov [this message]
2007-11-19 11:06 ` locally-administered MAC addresses create stupid rules Kay Sievers
2007-11-19 11:31 ` Alexander E. Patrakov
2007-11-19 11:55 ` Kay Sievers
2007-11-19 12:04 ` Alexander E. Patrakov
2007-11-19 12:18 ` Kay Sievers
2007-11-19 12:53 ` Alexander E. Patrakov
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='fhr4de$lfb$1@ger.gmane.org' \
--to=patrakov@gmail.com \
--cc=linux-hotplug@vger.kernel.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;
as well as URLs for NNTP newsgroup(s).