On 01/30/11 04:36, Johannes Berg wrote:
On Sat, 2011-01-29 at 21:38 -0800, Ben Greear wrote:
I tried to set up hostapd to do HT40-, but for whatever reason,
it's not sending any wmm_param options, so the stations will not
associate with HT40- enabled due to the check below.
Is it really *reqired* that wmm_param exist to enable HT mode?
From mlme.c:
if (elems.ht_info_elem&& elems.wmm_param&&
(sdata->local->hw.queues>= 4)&&
!(ifmgd->flags& IEEE80211_STA_DISABLE_11N))
changed |= ieee80211_enable_ht(sdata, elems.ht_info_elem,
cbss->bssid, ap_ht_cap_flags);
802.11n-2009 says it is required.
Having run into this same issue before, I considered adding some
default values for the case that wmm is not configured, but someone
tries to enable 802.11n, I just never decided where the best spot
for that would be. Should this sort of thing be a hostapd default
or somewhere in the cfg80211/mac80211 layer? I was thinking this
should be something that hostapd does.
As I see it, there are a few ways to prevent this problem:
1. Hostapd doesn't allow 802.11n to be enabled without wmm
2. Hostapd does allow 802.11n to be enabled without wmm, but uses
defaults
3. Hostapd doesn't care about this, and the kernel doesn't allow
802.11n without wmm
4. Hostapd doesn't care, but the kernel makes the correnctions
I believe 2 is the cleanest solution. So that the packets passed
from hostapd can make it through unmolested, and new hostapd versions
can work with older kernels. Any other solution I'm not thinking of?
Pat Erley
--
To unsubscribe from this list: send the line "unsubscribe linux-wireless" in
the body of a message to majordomo@xxxxxxxxxxxxxxx
More majordomo info at http://vger.kernel.org/majordomo-info.html
