Probably want to copy linux-wireless@xxxxxxxxxxxxxxx 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@xxxxxxxxxxxxxxx > 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@xxxxxxxxxxxxx - To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
