c8dd70cfb1
Currently while deciding to create a new Multiple BSSID element based on the condition when the length reaches 255, the length value being used is the total element length (including the length of the Element ID and Length fields as well). However, the value in the length field denotes the number of octets following it and excluding itself. Hence including the total length is wrong. This leads to incorrect count of Multiple BSSID elements. And while filling the data, the length is considered porperly as it should be hence we are filling more data in a single go and all data is filled in MBSSID count which is less than originally calculated. This ultimately leads to incorrect length calculation during nla_put() and setting the beacon to the driver fails while putting the Multiple BSSID element data into the netlink socket buffer. Fix this issue by considering the length excluding the Element ID and Length field sizes. Signed-off-by: Aditya Kumar Singh <quic_adisi@quicinc.com> |
||
---|---|---|
.. | ||
ap | ||
common | ||
crypto | ||
drivers | ||
eap_common | ||
eap_peer | ||
eap_server | ||
eapol_auth | ||
eapol_supp | ||
fst | ||
l2_packet | ||
p2p | ||
pae | ||
pasn | ||
radius | ||
rsn_supp | ||
tls | ||
utils | ||
wps | ||
build.rules | ||
lib.rules | ||
Makefile | ||
objs.mk |