On Tue, 2019-08-20 at 15:53 -0400, James Prestwood wrote: > > I thought so, but I had another thought later. It might be possible > > to > > set LIVE_ADDR_CHANGE, but then block it in mac80211 when the > > interface > > is already connected (or beaconing, or whatever, using the MAC > > address > > in some way - even while scanning, remain-on-channel is active, etc.) > > Yeah that makes sense. > > > I still think you'd have to bake it into the mac80211<->driver API > > somehow, because we normally "add_interface()" with the MAC address, > > and > > nothing says that the driver cannot ignore the MAC address from that > > point on. The fact that iwlwifi just copies it into every new > > MAC_CTXT > > command and the firmware actually accepts the update seems rather > > accidental and therefore fragile to rely on. > > I havent looked into the actual drivers WRT add_interface so I'll take > a look. But I think I see the separation now and why it may not work > for all drivers/firmwares the way I did it. > > So are you thinking we need another driver method: > "change_mac/set_mac"? Perhaps. Let's continue that in the other sub-thread, where I replied in more detail to Denis. johannes
