From: "John W. Linville" <linville@tuxdriver.com>
To: Alan Jenkins <alan-jenkins@tuffmail.co.uk>
Cc: linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
flamingice@sourmilk.net
Subject: Re: rtl8187: Invalid hwaddr! Using randomly generated MAC address
Date: Fri, 17 Aug 2007 13:25:22 -0400 [thread overview]
Message-ID: <20070817172522.GD6090@tuxdriver.com> (raw)
In-Reply-To: <46C5C5E5.3040503@tuffmail.co.uk>
Probably want to copy linux-wireless@vger.kernel.org on
wireless-related posts. Adding Michael Wu to the CC: as well...
John
On Fri, Aug 17, 2007 at 04:59:33PM +0100, Alan Jenkins wrote:
> I've just acquired this buggy piece of hardware otherwise known as a
> NetGear WG111v2. I googled and eventually found an explanation in the
> form of source code here:
>
> <http://www.gelato.unsw.edu.au/lxr/source/include/linux/etherdevice.h#L93>.
>
>
> It seems linux rejects the hardware MAC address because it is either all
> zero or a multicast address (ie the first byte has 0x01 set.
>
> On the side of this buggy piece of hardware is written:
>
> MAC 001B2F7604E6
>
> which AFAICS is valid; it's definitely not all zeros and the first byte
> has no bits set at all.
>
>
> Q. Udev can't access the invalid mac address. Does that mean there is
> no persistent identifier for the device? I know I could identify a
> device as a NetGear WG111v2, but I do have two of them. It would be
> nice if I could fix them by adding udev rules to identify individual
> devices, and set their MAC address to what it's "supposed" to be.
>
> /me scrabbles around for a Windows installation to find out whether the
> MAC address is somehow set correctly on the Other OS.
> -
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at http://www.tux.org/lkml/
--
John W. Linville
linville@tuxdriver.com
parent reply other threads:[~2007-08-17 17:44 UTC|newest]
Thread overview: expand[flat|nested] mbox.gz Atom feed
[parent not found: <46C5C5E5.3040503@tuffmail.co.uk>]
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=20070817172522.GD6090@tuxdriver.com \
--to=linville@tuxdriver.com \
--cc=alan-jenkins@tuffmail.co.uk \
--cc=flamingice@sourmilk.net \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@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).