On Wed, 2018-09-19 at 13:47 -0700, Ben Greear wrote: > > For one, the driver has no concept of the original vif, since monitor > > vifs aren't added to it. > > ath10k does create a monitor vif, but maybe it is not mapped directly > to mac80211. It's actually created by mac80211, but only once, and not directly mapped to each vif seen by userspace - it's an internal construction. > > Secondly, the old hostapd code before nl80211 injects frames that way, > > and they need to go there. > > Ok, I agree we should not break backwards compat then. I'll poke some more > to see if I can get it working. We might get away with doing this only for cooked monitor mode, which it used there ... However, thinking about it, that also breaks userspace in other ways - for example if you do injection this way you actually get encryption and other nice things if you use the local address that matches an existing interface. Perhaps you should just use a different address, and then nothing of the sort would happen? johannes
