diff options
author | Daniel Gabay <daniel.gabay@intel.com> | 2024-02-05 00:06:03 +0200 |
---|---|---|
committer | Johannes Berg <johannes.berg@intel.com> | 2024-02-08 13:24:10 +0100 |
commit | 2e57b77583ca34fdb6e14f253172636c52f81cf2 (patch) | |
tree | 695d3c8a58fb1bf85661a07d893d961a43c0e82f /drivers/bluetooth | |
parent | c98d8836b817d11fdff4ca7749cbbe04ff7f0c64 (diff) | |
download | linux-stable-2e57b77583ca34fdb6e14f253172636c52f81cf2.tar.gz linux-stable-2e57b77583ca34fdb6e14f253172636c52f81cf2.tar.bz2 linux-stable-2e57b77583ca34fdb6e14f253172636c52f81cf2.zip |
wifi: iwlwifi: mvm: use correct address 3 in A-MSDU
As described in IEEE sta 802.11-2020, table 9-30 (Address
field contents), A-MSDU address 3 should contain the BSSID
address.
In TX_CMD we copy the MAC header from skb, and skb address 3
holds the destination address, but it may not be identical to
the BSSID.
Using the wrong destination address appears to work with (most)
receivers without MLO, but in MLO some devices are checking for
it carefully, perhaps as a consequence of link to MLD address
translation.
Replace address 3 in the TX_CMD MAC header with the correct
address while retaining the skb address 3 unchanged.
This ensures that skb address 3 will be utilized later for
constructing the A-MSDU subframes.
Note that we fill in the MLD address, but the firmware will do the
necessary translation to link address after encryption.
Signed-off-by: Daniel Gabay <daniel.gabay@intel.com>
Signed-off-by: Miri Korenblit <miriam.rachel.korenblit@intel.com>
Link: https://msgid.link/20240204235836.4583a1bf9188.I3f8e7892bdf8f86b4daa28453771a8c9817b2416@changeid
Signed-off-by: Johannes Berg <johannes.berg@intel.com>
Diffstat (limited to 'drivers/bluetooth')
0 files changed, 0 insertions, 0 deletions