[PATCH] wpa_supplicant: Enable HT40 support for AP mode
Mon Jul 9 11:42:44 PDT 2012
On Mon, Jul 09, 2012 at 08:30:23PM +0300, Arik Nemtsov wrote:
> On Mon, Jul 9, 2012 at 8:15 PM, Rajkumar Manoharan
> <rmanohar at qca.qualcomm.com> wrote:
> > On Mon, Jul 09, 2012 at 10:41:39PM +0530, Rajkumar Manoharan wrote:
> >> On Mon, Jul 09, 2012 at 07:33:23PM +0300, Arik Nemtsov wrote:
> >> > On Mon, Jul 9, 2012 at 7:15 PM, Rajkumar Manoharan
> >> > <rmanohar at qca.qualcomm.com> wrote:
> >> > > On Mon, Jul 09, 2012 at 06:50:04PM +0300, Arik Nemtsov wrote:
> >> > >> Can you tell me why HT_CAP_INFO_SUPP_CHANNEL_WIDTH_SET is not enabled
> >> > >> in the capabilities white-list?
> >> > >> (just below this code).
It does not sound like a good idea to enable 40 MHz channels
unconditionally especially for 2.4 GHz band. I guess it could be
considered for 5 GHz, but even there, I would rather have this
configurable or even better, set with p2p_connect/p2p_group_add commands
on the GO.
> A question for Jouni - are you against enabling 2.4Ghz 40mhz support
> for STA (CLI) only as well?
No. I thought we already enabled that (and probably do with some
drivers). Does this get somehow disabled with mac80211-based drivers?
I'm only concerned about unconditionally (or even by default) enabling
40 MHz channels on the AP/GO. The P2P client should follow whatever
parameters the GO has set for the network.
> This will require a different trick because we don't know what we are
> yet. How about enabling the 2Ghz operating classes and disabling the
> HT40 support just before starting the GO (if it's in 2Ghz)?
The GO can switch to 40 MHz channel even after having negotiated group
with the 20 MHz operating class. I don't see why the operating class
table would need to be modified for this to work.
Jouni Malinen PGP id EFC895FA
More information about the Hostap