+linux-wireless, where this should've gone > I am running a single wlan0 interface in managed mode (no aliases, > no other wireless interfaces). > The association with the AP still hasn't happened. > > I noticed that if trying to change the frequency to one of the valid > values, the driver returns EBUSY. > > The call stack is > cfg80211_wext_siwfreq > -->cfg80211_mgd_wext_siwfreq > --->cfg80211_set_monitor_channel (notice call to set 'monitor' > channel > in managed mode) > ----> fails with EBUSY > > Is therefore the expected behavior to fail under the above > circumstances > (managed mode && single wlan0 interface && no association)? > And if it is, please could you clarify when would it be valid to > change the frequency in managed mode? Frankly, I don't remember - all of this is plastered all over with backward compatibility hooks etc. How are you running into this? Why are you even trying to do this? You really shouldn't use wireless extensions any more. Also, there shouldn't be much reason to be setting the channel anyway, unless you want to trigger a connection specifically on that channel, but then when you use nl80211 you get that included in the CONNECT command there. Finally, I suspect that this particular backward compatibility hook can't really work anyway and could be removed, but I'm not sure that would have the effect you want either. johannes
