The mapping was being done from interface address to device address (using p2p_peer) at time of client disconnects/connects since those events did not provide device address information for a peer.<div><br></div><div>Going forward, this should go away since we now have device address from those events.</div>
<div><br></div><div>Thanks<br><br><div class="gmail_quote">On Tue, Dec 20, 2011 at 9:54 AM, hardik patel <span dir="ltr"><<a href="mailto:hk5patel@gmail.com">hk5patel@gmail.com</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi Jouni,<br>
<br>
Now we did change in GUI so instead of executing p2p_peer command to<br>
get peer address. we are using address which is come in "<br>
AP-STA-CONNECTED 00:0a:bf:45:56:78 " event message. Now it is working<br>
fine.<br>
<br>
thanks for giving information for p2p_peer command use.<br>
<br>
Thanks,<br>
Hardik<br>
<div class="HOEnZb"><div class="h5"><br>
On Tue, Dec 20, 2011 at 12:49 AM, Jouni Malinen <<a href="mailto:j@w1.fi">j@w1.fi</a>> wrote:<br>
> On Mon, Dec 19, 2011 at 11:28:13PM +0530, hardik patel wrote:<br>
>> Android Icream sandwich GUI is using this p2p_peer command to get p2p<br>
>> interface address and return that address if it got intended_addr in<br>
>> output.<br>
><br>
> If it uses intended_addr, it is quite broken.<br>
><br>
>> In Autonomous GO case, Once client get connected with AutoGO and as it<br>
>> got "AP_STA_CONNECTED_EVENT". it is executing p2p_peer command to get<br>
>> intended_addr and it is changing the state as "connected" in GUI. But<br>
>> as in AutoGO, we are not getting intended_addr in p2p_peer command<br>
>> it is not changing the state to connected and showing "available" in<br>
>> UI.<br>
><br>
> I'm not sure what exactly this is trying use the intended_addr for, but<br>
> this field is not meant to be shown to end user and some other mechanism<br>
> needs to be used for this.<br>
><br>
>> When in case of Normal GO case, in p2p_peer command we are getting<br>
>> intended_addr. So At p2p_client and p2p_go side once it got connected<br>
>> it is showing correct status in UI.<br>
><br>
> This works by accident; not by design..<br>
><br>
>> what other command we can use to get peer information ?<br>
><br>
> What exactly is the information that is needed here? Is this on the GO?<br>
> And to display the P2P Interface Address? Or on the P2P client? On GO,<br>
> AP-STA-CONNECTED event should be used.<br>
><br>
> --<br>
> Jouni Malinen PGP id EFC895FA<br>
> _______________________________________________<br>
> HostAP mailing list<br>
> <a href="mailto:HostAP@lists.shmoo.com">HostAP@lists.shmoo.com</a><br>
> <a href="http://lists.shmoo.com/mailman/listinfo/hostap" target="_blank">http://lists.shmoo.com/mailman/listinfo/hostap</a><br>
<br>
<br>
<br>
</div></div><div class="im HOEnZb">--<br>
Regards,<br>
Hardik<br>
<br>
"If you are doing what you have always been doing then expect what you<br>
have always been getting."<br>
</div><div class="HOEnZb"><div class="h5">_______________________________________________<br>
HostAP mailing list<br>
<a href="mailto:HostAP@lists.shmoo.com">HostAP@lists.shmoo.com</a><br>
<a href="http://lists.shmoo.com/mailman/listinfo/hostap" target="_blank">http://lists.shmoo.com/mailman/listinfo/hostap</a><br>
</div></div></blockquote></div><br></div>