On Sun, Jan 17, 2010 at 1:05 PM, Johannes Berg <johannes@xxxxxxxxxxxxxxxx> wrote: > On Sun, 2010-01-17 at 22:01 +0100, Felix Fietkau wrote: > >> > But like I said, you already have that information in the relevant >> > cases. hostapd you can just look in the config file for it... > >> Nope, hostapd can deviate from the config, e.g. in the HT40 case. >> It'll >> switch primary and secondary channel, if necessary, or switch from >> HT40 >> to HT20 entirely if there are overlapping BSSs. And what about STA >> mode? >> The channel won't be in the config in that case. > > In STA and IBSS modes you already have the information from the BSS > info. > > The channel type might be more interesting, but even then > >> > The problem with this is that not all drivers will be able to >> support >> > it, and that you will be exporting stale information say in the case >> > where we're not connected at all. >> If we document the exported channel for the netdev as 'last configured >> channel', it should be fine, IMHO. > > I really don't think we should do that. And it will not be possible to > ever have iwm/rndis/orinoco etc. export such information. > > In any case I have a feeling you're trying to use the kernel as a > database for something you already know, just don't have quite as > readily available as you'd like. So a good use case is when we do automatic channel selection for AP mode of operation. We currently don't support that on hostapd but eventually we could and IMHO should. How we go about it remains to be seen but querying the actual channel used by an 802.11 device is useful in those cases. You can get that information by looking at hostapd logs but that seems overkill. Luis -- 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
