23eef57018
In case the P2PS PD Request includes the P2P Channel List attribute, update the peer device supported channels and check if we have common channels with the peer that can be used for the connection establishment based on the connection capabilities: 1. In case of P2PS PD Request with no common channels, defer the flow unless auto accept equals true and the connection capabilities equals NEW (in which case the channels would be negotiated in the GO Negotiation). 2. In case of Follow up P2PS PD Request with no common channels, reject the request unless the connection capability is NEW. In addition, in case of a successful P2PS PD, save the device operating frequency (so it can be later used for join flow, etc.). Signed-off-by: Ilan Peer <ilan.peer@intel.com> |
||
---|---|---|
.. | ||
ap | ||
common | ||
crypto | ||
drivers | ||
eap_common | ||
eap_peer | ||
eap_server | ||
eapol_auth | ||
eapol_supp | ||
fst | ||
l2_packet | ||
p2p | ||
pae | ||
radius | ||
rsn_supp | ||
tls | ||
utils | ||
wps | ||
lib.rules | ||
Makefile |