summaryrefslogtreecommitdiff
path: root/include
diff options
context:
space:
mode:
authorChin-Yen Lee <timlee@realtek.com>2026-05-15 04:44:28 +0300
committerPing-Ke Shih <pkshih@realtek.com>2026-05-25 08:58:12 +0300
commitdcf5c7262bffa2cbafc6523be63c287d15d8ae22 (patch)
tree464f24d1e9446d299da8bf144ce7cfb96eb67ab4 /include
parent8c9e5fb13434ca76a0f8247e8f9dc1bbfb298e34 (diff)
downloadlinux-dcf5c7262bffa2cbafc6523be63c287d15d8ae22.tar.xz
wifi: rtw89: wow: send ARP reply packets instead of Null packets to keep alive
In WoWLAN mode, the firmware periodically sends Null packets to the AP to keep the connection alive and prevent the AP from disconnecting the client due to inactivity. However, it was observed that certain APs, such as TP-Link Archer BE800, do not recognize Null packets as valid activity and still drop the connection. Replacing Null packets with ARP reply packets effectively resolves this compatibility issue and maintains the connection. Specifically, while the firmware typically handles standard ARP offloads by dynamically modifying target IP/MAC fields, these keep-alive ARP reply packets are pre-filled by the driver with the DUT's own MAC and IP addresses for both sender and target fields. In this case, the firmware transmits the packets as-is without further modification. This approach ensures compatibility with APs that require valid Layer 3 traffic for activity monitoring while simplifying the firmware's processing logic during WoWLAN mode. Signed-off-by: Chin-Yen Lee <timlee@realtek.com> Signed-off-by: Ping-Ke Shih <pkshih@realtek.com> Link: https://patch.msgid.link/20260515014433.16168-9-pkshih@realtek.com
Diffstat (limited to 'include')
0 files changed, 0 insertions, 0 deletions