From: "Kay Sievers" <kay.sievers@vrfy.org>
To: "Carl-Daniel Hailfinger" <c-d.hailfinger.devel.2006@gmx.net>
Cc: "Gabriel C" <nix.or.die@googlemail.com>,
"Sasa Ostrouska" <casaxa@gmail.com>,
"Avuton Olrich" <avuton@gmail.com>,
linux-kernel@vger.kernel.org
Subject: Re: forcedeth ?
Date: Tue, 31 Jul 2007 03:52:45 +0200 [thread overview]
Message-ID: <3ae72650707301852p7289cc42of3e2a0ec2c62a5e1@mail.gmail.com> (raw)
In-Reply-To: <46AE9221.70302@gmx.net>
On 7/31/07, Carl-Daniel Hailfinger <c-d.hailfinger.devel.2006@gmx.net> wrote:
> On 31.07.2007 00:17, Gabriel C wrote:
> > Sasa Ostrouska wrote:
> >
> >> Gabriel, hmm, shouldnt udev be able to autoconfigure that ? But I need
> >> to check that, thx for the tip.
> >
> > Yes udev does this based on the MAC address but AFAIK forcedeth is 'special' for some reason
> > ( which I can really remember now and gets on each boot a new MAC address or alike )
>
> Ah yes, that's a workaround for certain buggy boards to make sure you're
> not left without networking even if the MAC address stored on the board
> is bogus.
>
> Basically, forcedeth checks if the MAC address supplied by your
> mainboard is bogus and autogenerates a random MAC address from a private
> range (prefix 00:00:6c) as workaround. However, it will complain loudly
> if it has to do that.
>
> Quoting from forcedeth.c:
> > if (!is_valid_ether_addr(dev->perm_addr)) {
> > /*
> > * Bad mac address. At least one bios sets the mac address
> > * to 01:23:45:67:89:ab
> > */
> > printk(KERN_ERR "%s: Invalid Mac address detected: %02x:%02x:%02x:%02x:%02x:%02x\n",
> > pci_name(pci_dev),
> > dev->dev_addr[0], dev->dev_addr[1], dev->dev_addr[2],
> > dev->dev_addr[3], dev->dev_addr[4], dev->dev_addr[5]);
> > printk(KERN_ERR "Please complain to your hardware vendor. Switching to a random MAC.\n");
> > dev->dev_addr[0] = 0x00;
> > dev->dev_addr[1] = 0x00;
> > dev->dev_addr[2] = 0x6c;
> > get_random_bytes(&dev->dev_addr[3], 3);
> > }
>
> Sometimes it helps to update the BIOS and/or set the MAC address which
> is printed on the board as MAC address in the BIOS.
In any case, it would be nice if the network core could add something like:
MAC_ORIGIN=device
MAC_ORIGIN=user
MAC_ORIGIN=random
or whatever makes sense here, to the uevent environment. So userspace
can handle according to that, like falling back using the
bus-slot-number to lookup the persistent name, or whatever is
appropriate.
Thanks,
Kay
next prev parent reply other threads:[~2007-07-31 1:52 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-07-30 20:01 Sasa Ostrouska
2007-07-30 20:37 ` Avuton Olrich
2007-07-30 21:26 ` Sasa Ostrouska
2007-07-30 22:03 ` Gabriel C
2007-07-30 22:10 ` Sasa Ostrouska
2007-07-30 22:17 ` Gabriel C
2007-07-31 0:27 ` Krzysztof Halasa
2007-07-31 1:36 ` Carl-Daniel Hailfinger
2007-07-31 1:52 ` Kay Sievers [this message]
2007-08-02 11:33 ` Kay Sievers
2007-08-03 16:04 ` Carl-Daniel Hailfinger
2007-07-30 22:22 ` Kay Sievers
2007-07-30 22:19 ` Gabriel C
2007-07-30 22:40 ` Kay Sievers
2007-07-30 23:10 ` Sasa Ostrouska
2007-07-30 23:36 ` Kay Sievers
2007-07-30 22:24 ` david
2007-07-30 22:32 ` Kay Sievers
2007-07-30 22:00 ` Gabriel C
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=3ae72650707301852p7289cc42of3e2a0ec2c62a5e1@mail.gmail.com \
--to=kay.sievers@vrfy.org \
--cc=avuton@gmail.com \
--cc=c-d.hailfinger.devel.2006@gmx.net \
--cc=casaxa@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=nix.or.die@googlemail.com \
/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
all inboxes | Powered by JetHome®