On Wed, 2017-10-18 at 13:51 -0700, Ben Greear wrote: > " > I guess you could implement this part? I.e. iterating the clients and > checking that they all support the rate that is set. However, then you > also need to implement that this gets reset when a new client that > doesn't support this rate connects. > " > > The first part seems OK, but the second seems like a pain. Maybe just > keep a new client from being able to connect at all if it doesn't support > any available rates? I suppose if you reject the NEW_STATION command, then hostapd will reject the association though, so it's probably not hard to do. However, I'm not really sure why you'd want that? If you do want that then basically you're just implemented a very roundabout way of adding this rate to the basic rates, so you might as well just add it and work with the current basic rates check? We'll need to be a little careful what happens with client-mode interfaces, which is where we actually observed hitting the WARN_ON() about not having any rates at all, but I think I already put a reset of the rates there anyway if they're not compatible with the AP. At least that's easier because there's only one client. johannes
