On Tue, 2016-02-09 at 17:06 +0100, Robert Henning wrote: > I am trying to get 40MHz channel width going. > But someone hostap isn't scanning for neighboring BSSes > > the end of the output of hostapd -dd looks as follows : > > hw vht capab: 0x0, conf vht capab: 0x0 > wlan0: interface state UNINITIALIZED->HT_SCAN > Scan for neighboring BSSes prior to enabling 40 MHz channel > 40 MHz affected channel range: [2392,2472] MHz > wlan0: nl80211: scan request > nl80211: Scan frequency 2412 MHz > nl80211: Scan frequency 2417 MHz > nl80211: Scan frequency 2422 MHz > nl80211: Scan frequency 2427 MHz > nl80211: Scan frequency 2432 MHz > nl80211: Scan frequency 2437 MHz > nl80211: Scan frequency 2442 MHz > nl80211: Scan frequency 2447 MHz > nl80211: Scan frequency 2452 MHz > nl80211: Scan frequency 2457 MHz > nl80211: Scan frequency 2462 MHz > Scan requested (ret=0) - scan timeout 10 seconds > Interface initialization will be completed in a callback > ctrl_iface not configured! > > Maybe, cause the interface was already in master mode? Probably, yes. hostap doesn't appear to set NL80211_SCAN_FLAG_AP which is what 'ap-force' does, so the driver will probably reject the scan request. That flag has been around since 2012, so there may be a good reason hostapd doesn't set it, but I'll leave that up to Jouni. Dan > After hostapd starts, i am unable to scan as well, i have to use > > iw dev wlan0 scan ap-force > > Thanks in advance for any hints, on how to solve the problem > > > _______________________________________________ > Hostap mailing list > Hostap@xxxxxxxxxxxxxxxxxxx > http://lists.infradead.org/mailman/listinfo/hostap _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
