On Fri, Jan 8, 2010 at 3:20 PM, Jouni Malinen <j@xxxxx> wrote: > On Fri, Jan 08, 2010 at 01:41:58PM -0800, Luis R. Rodriguez wrote: >> On Fri, Jan 8, 2010 at 5:14 AM, Jouni Malinen <j@xxxxx> wrote: >> > By the way, that looks completely bogus.. Channel number cannot be used >> > to figure out whether this is 2.4 GHz or 5 GHz band (e.g., channel 8 is >> > used in both). This really should be based on the band the frame with >> > the Country IE was received. >> >> This seems to me more like an issue with the spec. Doing it based on >> the received band is obviously possible but what if the AP wants to >> send out Country IE information for both channel 8 on 2 GHz and >> channel 8 on 5 GHz? >> > > I don't think the original Country IE design from IEEE Std 802.11d-2001 > really supported such use, i.e., you can only describe the channels from > your own band with that design. Have you really seen APs advertising > channels from the other band in their Country IE? > > I would assume you could now use the Regulatory Extension mechanism to > define another regulatory class and subband followed by channel triplets > to do that. However, even in that case, the first triplets in the IE > really needs to be for the band the frame is send on. Once the > Regulatory Extension Identifier is used, further triplets should be > interpreted differently. Anyway, I have no idea whether anyone really > supports this extension (or can parse the standard to figure out how it > would be used ;-).. Heh alright, I'll change this to match the rx'd band first but that change is a bit big for stable so we'll have to deal with how we have it now for stable. I'll submit the changes for wireless-testing. Now last question -- although I haven't seen APs send country IEs for two bands in case we do, how do you want to treat those channels? Does hostapd send just one band or two bands on the country IE? 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
