aboutsummaryrefslogtreecommitdiffstats
path: root/wpaspy
diff options
context:
space:
mode:
authorJouni Malinen <jouni@qca.qualcomm.com>2013-03-01 19:27:31 (GMT)
committerJouni Malinen <j@w1.fi>2013-03-01 19:27:31 (GMT)
commitcd1e2309a2ae5bf29d2bbdf798224e1a06feadef (patch)
treeee5ebd836617bc53aee86c92513edc2baff2e246 /wpaspy
parent18206e02c540f0a379db507b4ecc22c8855c7acf (diff)
downloadhostap-cd1e2309a2ae5bf29d2bbdf798224e1a06feadef.zip
hostap-cd1e2309a2ae5bf29d2bbdf798224e1a06feadef.tar.gz
hostap-cd1e2309a2ae5bf29d2bbdf798224e1a06feadef.tar.bz2
P2P: Indicate frequency for upper layer invitation processing
When a device that is a GO in a persistent group receives an Invitation Request from a P2P client and persistent_reconnect=0, upper layer is notified of this with P2P-INVITATION-RECEIVED event. The upper layer is supposed to run another invitation exchange is this case, but if that does not happen and the GO is started without successful (status=0) invitation exchange, the operating channel for the group may end up getting set in a way that the P2P client is not able to support. Provide optional freq parameter in the P2P-INVITATION-RECEIVED event on the GO side. If this parameter is received and the upper layer decides to issue P2P_GROUP_ADD command, that command should include this freq parameter to make sure the operating channel gets selected from the set that the peer can support. Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
Diffstat (limited to 'wpaspy')
0 files changed, 0 insertions, 0 deletions