[RFC] P2P: Handling single channel concurrency

Reinette Chatre reinette.chatre
Mon Jan 9 09:57:41 PST 2012

Hi Jouni,

On Sun, 2012-01-08 at 20:59 -0800, Jouni Malinen wrote:
> In other words, something above wpa_supplicant would take care of users totally separe
> preferences on how to behave based on use cases etc. It would explicitly
> need to stop previously started operations before starting the new
> conflicting one - wpa_supplicant should not need extra code for that
> part.

I agree that something above wpa_supplicant should take care of user
preferences and how to behave. I am not sure that this can efficiently
be accomplished without adding _any_ code to wpa_supplicant. How I
understand things a complete separate solution like this would add an
additional communication hop (eg. D-Bus) to things and it will also
require changes to all communication managers to now start talking to
this new entity instead of wpa_supplicant. 


More information about the Hostap mailing list