This mail describes the purpose of the attached "hostapd" patch.
The patch avoids issue when there is mismatch between user's 11ax config and DRV capability
Behavior (without the patch):
==========================
Non-HE capable interface advertising HE IEs/Capabilities in Beacon/Probe Response/Association Response frames if "ieee80211ax=1" configuration is used
Patch Description:
================
1. The HE capability for an AP iface was read from the driver, but was not used to update the "drv_flags" for the interface
2. Change is now added to update the HE capability in the "drv_flags" of the interface
3. If the interface does not support HE capability, the "iface->conf->ieee80211ax" flag is set to 0
4. Now Beacons/Probe response/Association Response will advertise HE capabilities ONLY if the interface is HE capable
Patch Verification:
=================
1. For Intel and NXP non-11ax/HE capable chip/interface, when "ieee80211ax=1" is used in the config file, NO HE IEs are added in the Beacon/Probe Response/Association Response frames
2. For NXP 11ax/HE capable chips, the HE IEs get added correctly to the required MGMT frames
Thanks,
Deepti
Attachment:
0001-Issue-Non-HE-capable-interface-advertising-HE-IEs-Ca.patch
Description: 0001-Issue-Non-HE-capable-interface-advertising-HE-IEs-Ca.patch
_______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
