Persistent P2P link with N clients

[Jouni Malinen]

On Wed, Dec 12, 2012 at 01:56:18PM +0100, Aurelien Lefebvre wrote:
> I have N clients, and I want them to be connected together via P2P, so 
> I've done the following procedure:
> 
> GO: p2p_group_add
> GO: wps_pbc
> P2P-CLIENT-1: p2p_connect XX:XX:XX:XX:XX:XX pbc join
> (Here, the link between GO and P2P-CLIENT-1 is established)
> GO: wps_pbc
> P2P-CLIENT-2: p2p_connect XX:XX:XX:XX:XX:XX pbc join
> (Here, the link between GO en P2P-CLIENT-2 is established)
> 
> At this point, I got everything I want, except one thing: I want this 
> topology to be persistent against wpa_supplicant restart or target 
> reboot. How can I manage that? Is it possible by saving config in 
> wpa_supplicant configuration files or is it mandatory to re-do the 
> previous procedure?

Yes, you can create this as a persistent group (use "p2p_group_add
persistent" on the GO). If the configuration file has update_config=1
this will allow both the GO and the P2P clients to store the persistent
group information.

> Re-applying the procedure each time is a problem as it requires human 
> actions: wps_pbc for client1, *then* for client2, etc. Because I tried 
> concurrent connection and it results in wps overlap failures.

With persistent groups, you can re-start the group with "p2p_group_add
persistent=<network id>" on the GO and P2P clients. This will use the
previously provisioned credentials instead of having to go through the
WPS step again.

-- 
Jouni Malinen                                            PGP id EFC895FA