On Sun, Mar 6, 2016 at 11:17 AM, Jouni Malinen <j@xxxxx> wrote: > On Tue, Mar 01, 2016 at 05:01:27PM +0200, Eliad Peller wrote: > >> can you please explain the logic behind this (ancient) commit: >> >> commit 9290cc1 >> Author: Jouni Malinen <jouni.malinen@xxxxxxxxxxx> >> Date: Fri Oct 8 17:15:16 2010 +0300 >> >> Apply hostapd WPS commands to all interfaces on concurrent APs >> >> When the same hostapd process is controlling multiple interfaces, >> apply WPS commands (push button, add PIN, change AP PIN) to all >> interfaces that are configured to use WPS. >> >> since every bssid can have its own control interface and WPS state, >> why would WPS command sent to a single interface (e.g. WPS_PBC) should >> affect all the other ones as well? > > There are many dualband APs with 2.4 and 5 GHz radios configured with > the same network. This is why the hostapd default behavior manages the > WPS operations consistently on the radios. wps_independent=1 can be used > in a per-BSS configuration to separate a subset of BSSes into their own > independent "WPS group". > thanks Jouni! i totally overlooked it. Eliad. _______________________________________________ Hostap mailing list Hostap@xxxxxxxxxxxxxxxxxxx http://lists.infradead.org/mailman/listinfo/hostap
