[EDT][PATCH] P2P :- Listen frequence and Operating frequency information

[Rahul Jain]

hello Jouni,

Thanks for your reply.
>From debugging point of view, Listen and Operating frequency information of peer are required for capturing the air logs of peer.
Peer can have only one listen frequency and multiple operating frequency (due to MCC. Right?).
Currently, there is no way to get this information when wpa_supplicant is running over dbus.

This patch is targeting the hurdle during connection failure between p2p devices.

Regarding documentation, You want us to change ListenFreq to DebugListenFreq & OperFreq to DebugOperFreq.

Please correct me.

Thanks
-Rahul Jain 
EP-A39FC82E86A64058A3D483D9DB07ED2D


------- Original Message -------
Sender : Jouni Malinen<j at w1.fi>
Date : Jun 06, 2015 20:11 (GMT+05:30)
Title : Re: [EDT][PATCH] P2P :- Listen frequence and Operating frequency information

On Mon, Jun 01, 2015 at 12:21:13PM +0000, Amit Khatri wrote:
> Thanks for suggestion. i have made the changes accrodingly.

Could you please clarify what you are planning on using this information
for? While you do note this is for "debug over dbus interface", I do not
really want to expose these internal parameters from wpa_supplicant
through the D-Bus interface since there is significant risk of them
being misused just like they did over the control interface.

> diff --git a/doc/dbus.doxygen b/doc/dbus.doxygen
> @@ -1642,6 +1642,14 @@ Interface implemented by objects representing P2P peer devices.
>    

> +    
ListenFreq - i - (read)

> +  

> +
> +  

> +    
OperFreq - i - (read)

> +  


This is even documenting these variables without any sign of debugging
mentioned here. These fields are simply not reliable since they may
change at any point in time and OperFreq is even worse since the peer
may have multiple operating channels.

-- 
Jouni Malinen                                            PGP id EFC895FA