From: Lubomir Rintel <lkundrak@v3.sk>
To: linux-hotplug@vger.kernel.org
Subject: [PATCH] Whitelist NICs that violate MAC assignement scheme
Date: Sat, 02 May 2009 16:03:05 +0000 [thread overview]
Message-ID: <1241280185.2641.2.camel@localhost.localdomain> (raw)
According to list of assigned ethernet codes [1] referred to by
IANA [2] certain global addresses do not follow the assignement
scheme and use numbers reserved for local use. Several such adapters
are quite widely used, generate rules for them.
[1] http://www.cavebear.com/archive/cavebear/Ethernet/vendor.html
[2] http://www.iana.org/assignments/ethernet-numbers
---
.../75-persistent-net-generator.rules | 29 ++++++++++++++++++++
1 files changed, 29 insertions(+), 0 deletions(-)
diff --git a/extras/rule_generator/75-persistent-net-generator.rules b/extras/rule_generator/75-persistent-net-generator.rules
index 5c2f100..79fe01b 100644
--- a/extras/rule_generator/75-persistent-net-generator.rules
+++ b/extras/rule_generator/75-persistent-net-generator.rules
@@ -29,9 +29,38 @@ ENV{MATCHADDR}="$attr{address}"
# match interface type
ENV{MATCHIFTYPE}="$attr{type}"
+# These are known to violate the local MAS address assignment scheme
+# http://www.cavebear.com/archive/cavebear/Ethernet/vendor.html
+# Interlan [now Racal-InterLAN] DEC (UNIBUS or QBUS), Apollo, Cisco, Racal-Datacom
+ENV{MATCHADDR}="02:07:01:*", GOTO="globally_administered_whitelist"
+# 3Com
+ENV{MATCHADDR}="02:60:60:*", GOTO="globally_administered_whitelist"
+# 3Com IBM PC; Imagen; Valid; Cisco; Macintosh
+ENV{MATCHADDR}="02:60:8c:*", GOTO="globally_administered_whitelist"
+# Intel
+ENV{MATCHADDR}="02:a0:c9:*", GOTO="globally_administered_whitelist"
+# Olivetti
+ENV{MATCHADDR}="02:aa:3c:*", GOTO="globally_administered_whitelist"
+# CMC Masscomp; Silicon Graphics; Prime EXL
+ENV{MATCHADDR}="02:cf:1f:*", GOTO="globally_administered_whitelist"
+# Prominet Corporation Gigabit Ethernet Switch
+ENV{MATCHADDR}="02:e0:3b:*", GOTO="globally_administered_whitelist"
+# BTI (Bus-Tech, Inc.) IBM Mainframes
+ENV{MATCHADDR}="02:e6:d3:*", GOTO="globally_administered_whitelist"
+# Realtek (UpTech? also reported)
+ENV{MATCHADDR}="52:54:00:*", GOTO="globally_administered_whitelist"
+# Novell 2000
+ENV{MATCHADDR}="52:54:4c:*", GOTO="globally_administered_whitelist"
+# REALTEK (a Realtek 8029 based PCI Card)
+ENV{MATCHADDR}="52:54:ab:*", GOTO="globally_administered_whitelist"
+# Kingston Technologies
+ENV{MATCHADDR}="e2:0c:0f:*", GOTO="globally_administered_whitelist"
+
# do not use "locally administered" MAC address
ENV{MATCHADDR}="?[2367abef]:*", ENV{MATCHADDR}=""
+LABEL="globally_administered_whitelist"
+
# do not use empty address
ENV{MATCHADDR}="00:00:00:00:00:00", ENV{MATCHADDR}=""
--
"Excuse all the blood" -- Dead
next reply other threads:[~2009-05-02 16:03 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-05-02 16:03 Lubomir Rintel [this message]
2009-05-03 13:39 ` [PATCH] Whitelist NICs that violate MAC assignement scheme Kay Sievers
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=1241280185.2641.2.camel@localhost.localdomain \
--to=lkundrak@v3.sk \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.