How to disable /b and /a/g rates?
Tue Mar 10 13:05:30 PDT 2015
On Tue, 2015-03-10 at 12:52 -0700, Ben Greear wrote:
> On 03/10/2015 12:44 PM, Johannes Berg wrote:
> > On Tue, 2015-03-10 at 12:27 -0700, Ben Greear wrote:
> >> Regardless of how good of an idea this is for real-world deployment,
> >> would it actually be OK per the wifi spec to disable all basic rates?
> > You seem to be confusing a few things. You cannot "disable all basic
> > rates", as the AP determines which rates are basic rates. Certainly, if
> > the AP doesn't advertise a rate, then it can also not be marked as a
> > basic rate.
> I guess I mean that I would want only the HT rates to be the
> basic rates..none of the /b/g/a rates...
Oh, so you want to basically support the legacy rates, but not mark them
as basic rates? That might even work. But then you'd still not 'pure
Btw, HT had something called "greenfield" though I think VHT ignored
> Also, in this case, I am interested in doing this on the AP.
> I basically want to have an /n/AC AP only..no legacy stuff
> at all.
That's different from just not having those rates as basic rates though,
that means you're saying you don't want to support those rates at all,
which I believe to not be compliant.
> For grins, I tried setting the supported_rates=360 480 540
> In this case, it seems hostapd at least thinks it has started,
> but ath10k will not beacon as far as I can tell.
> That could easily be bugs in ath10k driver or firmware...I'll
> go poke around there next.
Not really surprising, usually you *want* the beacons at a lower rate to
have other devices around find them. This, btw, includes legacy devices
even if they're not allowed to connect to you - they still have to
interoperate with you on the same channel.
More information about the Hostap