On 28 May 2014 19:19, Janusz Dziedzic wrote: > On 28 May 2014 17:25, Vu Hai NGUYEN wrote: >>> This is set base on what driver/mac80211/cfg80211 report - function >>> wpa_driver_nl80211_capa(). >>> With ath10k and new mac80211 this should be never set. So, seems you still >>> have old/wrong modules and system build/configuration problem? >>> Check cfg80211.ko/mac80211.ko ... and/or add some prints to driver_nl80211.c >> >> Problem solved. I looked in the driver_nl80211.c and found that use_monitor relied on "poll_command_supported" and "data_tx_status". I printed these 2 parameters and saw that data_tx_status=0, it depends on NL80211_FEATURE_SK_TX_STATUS and this parameter was affected to the flags of wiphy->features, defined in /net/mac80211/main.c.I find this parameter was set = 0 in /backport-include/linux/nl80211.h >> That's why montior mode was forced to used with AP mode. I set that parameter = 1 and no more monitor interface in AP mode, my AP work in DFS mode now. >> I'll write a mail to backport mail list to ask them why do they set that parameter=0. >> > OK, btw I see there is a bug when sending frame using monitor > interface in mac80211 in ieee80211_monitor_start_xmit() - because of > that you have this problem. Seems for old kernel < 3.3.0 monitor > interface is required. > I will fix mac80211 issue when monitor is used. Please remove your hack (use_monitor again) and check attached patch. BR Janusz > >> I get another question: There a conflict of information about HT40+ and HT40- in hostapd and ht40allow_map (fromdebugfs). >> In the hostapd.conf example file: >> # Note: There are limits on which channels can be used with HT40- and >> # HT40+. Following table shows the channels that may be available for >> # HT40- and HT40+ use per IEEE 802.11n Annex J: >> # freq HT40- HT40+ >> # 5 GHz 40,48,56,64 36,44,52,60 >> It means the channel 48 is not available in HT40+. But the info from ht40allow_map said that channel 5240 Mhz (ie 48) is available in both 40+ and 40-. >> If I set ht-capab=[HT40+] and channel=48, hostapd can not setup AP mode. >> And the channel 140 can not be set neither in bandwidth 40+ nor 40- even my "iw list' show that channel 140 is available. >> Is there a problem with ht40allow_map? >> > Seems ht40allow_map don't care about 80211n standard, just check > neighbor channels and set -/+. So, hostapd play with this correctly. > channel 140 as I remember correctly is disabled for all atheros cards. > I think Luis write about it. > > BR > Janusz