P2P Persistent Group Revoke Methods
Jouni Malinen
j
Thu Jan 22 15:42:44 PST 2015
On Tue, Jan 13, 2015 at 04:21:11AM +0000, KUMAR AMIT SINGH wrote:
> <HTML><HEAD><TITLE>Samsung Enterprise Portal mySingle</TITLE>
Please send plaintext messages to this mailing list..
> <P>You have mentioned the 2-case in which persistent revoke request receiving device may join automatically OR in other case user want to accept the connection</P>
> <P>I have been trying the 2nd case in which "user want to accept the connection". For that I am trying below steps:</P>
> <P> </P>
> <P>Device-A (Request): p2p_invite persistent=2 peer=02:90:4c:c5:12:38</P>
> <P>Device-B (Event): P2P-INVITATION-RECEIVED <BR>Device-B (Request): set persistent_reconnect 1<BR></P>
Setting persistent_reconnect to 1 is not for the case you are
interesting in. It is only for the purpose of configuring the device to
allow persistent group reinvocation without user interaction.
> <P>Ideally, Device-B should be able to join the persistent group. But it is not happening. It only SUCCEED when the Device-B has done "set persistent_reconnect 1" Before the Invitation started from Device-A.</P>
That is exactly how persistent_reconnect=1 is supposed to work.. You
need to leave it to 0 if you want user to acknowledge the connection.
> <P>I have also tried "P2P-CONNECT" on Device-B after "P2P-INVITATION-RECEIVED" Event Received but that also seems not working.</P>
P2P_CONNECT is for negotiating a new P2P group or joining an already
operating group, not for reinvoking a persistent group. You would issue
P2P_INVITE on the device to start another invitation exchange after the
user has accepted the connection. In other words, wait for this event:
P2P-INVITATION-RECEIVED sa=02:00:00:00:01:00 persistent=1 freq=2462
and issue this once user accepts:
P2P_INVITE persistent=1 peer=02:00:00:00:01:00 freq=2462
(the arguments copied from the event message assuming you do not have a
need to try to enforce different operating frequency)
--
Jouni Malinen PGP id EFC895FA
More information about the Hostap
mailing list