summaryrefslogtreecommitdiffstats
path: root/tools/iio
diff options
context:
space:
mode:
authorJohannes Berg <johannes.berg@intel.com>2022-08-24 12:30:16 +0200
committerJohannes Berg <johannes.berg@intel.com>2022-08-25 10:41:31 +0200
commita6ba64d0b187109dc252969c1fc9e2525868bd49 (patch)
tree65589d4c2c39b4f88526f28e6cad906c680661fb /tools/iio
parent8b06d13ed29f324c30c688919dcb02f859cf2ca7 (diff)
downloadlinux-a6ba64d0b187109dc252969c1fc9e2525868bd49.tar.bz2
wifi: mac80211: fix control port frame addressing
For an AP interface, when userspace specifieds the link ID to transmit the control port frame on (in particular for the initial 4-way-HS), due to the logic in ieee80211_build_hdr() for a frame transmitted from/to an MLD, we currently build a header with A1 = DA = MLD address of the peer MLD A2 = local link address (!) A3 = SA = local MLD address This clearly makes no sense, and leads to two problems: - if the frame were encrypted (not true for the initial 4-way-HS) the AAD would be calculated incorrectly - if iTXQs are used, the frame is dropped by logic in ieee80211_tx_dequeue() Fix the addressing, which fixes the first bullet, and the second bullet for peer MLDs, I'll fix the second one for non-MLD peers separately. Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'tools/iio')
0 files changed, 0 insertions, 0 deletions