aboutsummaryrefslogtreecommitdiffstats
path: root/wpaspy
diff options
context:
space:
mode:
authorJouni Malinen <jouni@qca.qualcomm.com>2013-03-01 19:32:33 (GMT)
committerJouni Malinen <j@w1.fi>2013-03-01 19:32:33 (GMT)
commit77e4e85321a0a1255901914d5de916aba050f9e1 (patch)
tree5d08947aba546b5ccb2fc9c1e412f5bce4958924 /wpaspy
parentcd1e2309a2ae5bf29d2bbdf798224e1a06feadef (diff)
downloadhostap-77e4e85321a0a1255901914d5de916aba050f9e1.zip
hostap-77e4e85321a0a1255901914d5de916aba050f9e1.tar.gz
hostap-77e4e85321a0a1255901914d5de916aba050f9e1.tar.bz2
P2P: Mark peer authorized for persistent group invitation
When p2p_invite persistent=<id> is used to request a persistent group to be re-invoked, the peer may reply with status=1 (info not yet available) if upper layer processing of the invitiation is requested. The peer is ten expected to start another invitation exchanged within 120 seconds if the user authorizes the connection. Allow this process to be used more easily by automatically authorizing the peer that we tried to invite to use this second invitation sequence even if persistent_reconnect=0. For this mechanism to work, the device that starts the invitation needs to start listen mode to be able to receive the invitation request from the peer. At least for now, this is not done automatically, but future changes could potentially enable this automatically at least if there are no concurrent operations in progress. Example sequence on the initiator: cmd: P2P_INVITE persistent=1 peer=<addr> event: P2P-INVITATION-RESULT status=1 cmd: P2P_LISTEN 120 wait for peer to start another invitiation round.. group will be re-invoked automatically On the peer (with persistent_reconnect=0): event: P2P-INVITATION-RECEIVED sa=<addr> persistent=1 [freq=<MHz>] wait for user approval cmd: P2P_INVITE persistent=1 peer=<addr> group will be re-invoked automatically Signed-hostap: Jouni Malinen <jouni@qca.qualcomm.com>
Diffstat (limited to 'wpaspy')
0 files changed, 0 insertions, 0 deletions