P2P-GO remains in an autonomous group after last P2P-CLI disconnection

[Jouni Malinen]

On Mon, May 23, 2016 at 11:12:54AM +0200, Jose Blanquicet wrote:
> We have found that when our system is the P2P-GO and the last P2P-CLI
> in the P2P-Group gets disconnected, the wpa_supplicant does not delete
> the P2P-Group and instead the P2P-GO remains alone as kind of
> autonomous group. We have not found any specific behavior in such a
> scenario specified by the Wi-Fi Alliance in the P2P Specifications,
> thus how to proceed is a choice. Therefore, we would like to know if
> the no-deletion of the group follows a particular request inside the
> wpa_supplicant. If it is not true and it does not affect any other
> process, we would like to add such a deletion to avoid the P2P-GO
> remains alone in the group, which could be done by disabling the
> network associated to the group.

That's configurable behavior. By default, the GO role keeps the group
running until explicitly asked to terminate the group. If you want the
group to be terminated automatically when there are no more clients in
it, you can configure that with the p2p_group_idle parameter. That sets
the idle timeout to the specified number of seconds (default: 0 = no
timeout). If there are no clients in the group for that time, GO will
stop the group automatically.

-- 
Jouni Malinen                                            PGP id EFC895FA