Hi Tomasz,

On 03/27/2014 11:29 PM, Tomasz Bursztyka wrote:
Listen to DeviceFound and DeviceLost. From there it gets the Peer path
and properties, store it into the interface object and call relevant
peer_found/peer_lost callbacks provided by the wifi plugin.

Due to the fact wpa_supplicant might not (it's a bug) send the device
address, the peer identifier will be constructed on its name in this
case.
I have a suggestion that maybe we can get the device address from the obj_path temporarily.
You know, name is not unique to distinguish the different remote peers.
I'm afraid that we may meet many issues with name as a identifier.

Cheers,
Guoqiang

_______________________________________________
connman mailing list
[email protected]
https://lists.connman.net/mailman/listinfo/connman

Reply via email to