On Mon, Feb 07, 2011 at 04:38:51PM -0800, Ben Greear wrote: > On 02/07/2011 03:53 PM, Daniel Halperin wrote: > >Just as there are G-only APs that don't advertise 1-11 Mbps in their > >beacons, there are HT-only APs that don't advertise support for 1-11 > >or 6-54 Mbps in their beacons and *only* support MCS rates. > If anyone knows how to configure such a beast, I'll run some > tests. Or, if someone else has an AP like this, please let > me know if you see any problems with these patches. As of today, the hostap.git snapshot of hostapd allows you to configure the AP to require HT PHY support from every station trying to associate with it. This can be configured with require_ht=1. This by itself does not change the advertised rate sets, but when set, this allows following configuration to remove all non-MCS rates to be disabled: ieee80211n=1 require_ht=1 supported_rates= basic_rates= I'm not sure whether we currently handle such configuration correctly everywhere, but at least this will remove the non-MCS rates from Beacon/Probe Response frames from the AP. It does not prevent the AP from actually receiving frames at non-MCS rates, so it may still reply to Probe Request frames even if they are sent without using MCS rates. I think I can make hostapd not reply to those frames if they do not contain HT Capabilities IE, but still, you would likely see a response to a Probe Request with that IE included even if it is sent at 1 Mbps. Whether the response goes out using MCS in such a case is unknown to me at this point, though. -- Jouni Malinen PGP id EFC895FA -- 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
