p2p_peer command is not showing intended_addr in auto GO mode
Tue Dec 20 09:54:17 PST 2011
Now we did change in GUI so instead of executing p2p_peer command to
get peer address. we are using address which is come in "
AP-STA-CONNECTED 00:0a:bf:45:56:78 " event message. Now it is working
thanks for giving information for p2p_peer command use.
On Tue, Dec 20, 2011 at 12:49 AM, Jouni Malinen <j at w1.fi> wrote:
> On Mon, Dec 19, 2011 at 11:28:13PM +0530, hardik patel wrote:
>> Android Icream sandwich GUI is using this p2p_peer command to get p2p
>> interface address and return that address if it got intended_addr in
> If it uses intended_addr, it is quite broken.
>> In Autonomous GO case, Once client get connected with AutoGO and as it
>> got "AP_STA_CONNECTED_EVENT". it is executing p2p_peer command to get
>> intended_addr and it is changing the state as "connected" in GUI. But
>> as in AutoGO, we are not getting ?intended_addr ?in p2p_peer command
>> it is not changing the state to connected and showing "available" in
> I'm not sure what exactly this is trying use the intended_addr for, but
> this field is not meant to be shown to end user and some other mechanism
> needs to be used for this.
>> When in case of Normal GO case, in p2p_peer command we are getting
>> intended_addr. So At p2p_client and p2p_go side once it got connected
>> it is showing correct status in UI.
> This works by accident; not by design..
>> what other command we can use to get peer information ?
> What exactly is the information that is needed here? Is this on the GO?
> And to display the P2P Interface Address? Or on the P2P client? On GO,
> AP-STA-CONNECTED event should be used.
> Jouni Malinen ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ? ?PGP id EFC895FA
> HostAP mailing list
> HostAP at lists.shmoo.com
"If you are doing what you have always been doing then expect what you
have always been getting."
More information about the Hostap