Hi Eddie, > The AP is a Netgear WNR2000v3 running DD-WRT v24-sp2 (03/19/12) std. > > After sshing into it and playing around with the iw command, the phy is > phy0 and the device is ath0. > > "iw ath0 scan dump" returns nothing unfortunately. Yeah, sorry, I guess I confused you. I did want this info from the client, as you provided: > In case it helps, on the laptop (the client) I do get output from "iw > wlan0 scan dump": > > BSS 82:e1:fa:1a:65:00 (on wlan0) -- associated [...] > HT operation: > * primary channel: 9 > * secondary channel offset: above As you can see, it's using HT40+ on channel 9 (2452 MHz). Your HT40 allow (correctly) map showed: 2452 HT40 - This is because HT40+ isn't actually allowed on channel 9 by the standard (cf. 802.11-2012 Table E-1 (US), E-2 (Europe), E-3 (Japan). I wonder, what is the oldest kernel you tried? I think the fact that we can connect here was introduced by some older patch, and then reverted by my patch, so older kernels should have been slower as well? The problem here is that some devices (notably iwlwifi) will not allow (by firmware) to connect to such an AP as HT40- if that is not allowed. So I prevented it generally, but we can make it device dependent. I don't like it much, but I suppose we can do it. Try this patch: http://p.sipsolutions.net/0129f39c7d882289.txt It will still prohibit this configuration when the driver said it's not allowed, but will allow it when there were other reasons to not allow it. johannes -- 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
