[PATCH 0/2] RRM: Report driver-triggered Neighbor Report
Chung-Hsien Hsu
chung-hsien.hsu at infineon.com
Tue May 12 06:25:01 PDT 2026
Neighbor Report Request can be triggered by wpa_supplicant through the
control interface or by the driver/firmware. The current receive path
only reports Neighbor Report Responses that match a pending
wpa_supplicant request. Responses for driver-triggered requests are
treated as unexpected, or discarded due to dialog token mismatch, and
are not exposed to control interface monitors.
This series first moves the existing Neighbor Report control-interface
event formatting into RRM code as a shared helper, then uses that helper
to report unsolicited Neighbor Report Responses while preserving the
existing dialog token validation and timeout handling for
wpa_supplicant-triggered requests.
Chung-Hsien Hsu (2):
RRM: Move Neighbor Report event notification to RRM
RRM: Report driver-triggered Neighbor Report responses
wpa_supplicant/ctrl_iface.c | 97 +--------------
wpa_supplicant/rrm.c | 190 +++++++++++++++++++++++++++---
wpa_supplicant/wpa_supplicant_i.h | 2 +
3 files changed, 176 insertions(+), 113 deletions(-)
--
2.25.1
More information about the Hostap
mailing list