On Monday 22 March 2010 22:56:44 Larry Finger wrote: > On 03/22/2010 01:28 AM, Calvin Walton wrote: > > I'm curious, how would this firmware-loading scheme deal with having > > multiple cards of this type installed? This seems like an unusual > > situation, but it looks like this patch will cause all of the cards to > > start up with the same MAC address due to the fixed filename. > > I have a workaround for this problem based on the bus address of the > device. > > > Instead of using a firmware file to load in the MAC address, might it be > > possible to move the persistent MAC setting to a simple udev rule which > > generates a persistent MAC address, saves it, then sets it each boot > > using a command like "ip link set wlan0 address XX:XX:XX:XX:XX:XX" ? > > > > This would remove the need to have this "fake" firmware file available > > at boot, provided that the driver can handle leaving the address > > unconfigured until userspace gets around to setting it. As well, it > > could be written to work with multiple cards easily, saving a different > > MAC for each. > > Does anyone have any suggestions on what characteristic could be used to > generate a unique MAC address for a box in a udev rule? Unless someone > proposes a workable solution, I will push V3 of my patch with the bus > address change noted above. Why not use random_ether_addr and only use the digits that you are interested in? -- Florian -- 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
