[PATCH 4/4] implement secondary SSID capability
Sat Apr 25 09:06:02 PDT 2015
On Sat, Apr 25, 2015 at 05:37:48PM +0200, Stefan Tomanek wrote:
> This change enables the definition of secondary SSID strings attached to the
> same BSS; clients actively requesting those will be able to associate with the
> BSS using the alternative names.
> So even after the (fictional) companies Path-Way and E-Tec completed their
> merger and renamed their networks, legacy devices can still connect to the old
> network names (as long as they employ active scanning, since currently no
> beacons are generated for the secondary SSIDs).
Is there really need for this? Use of active scanning for a specific
SSID is very much discourages nowadays due to privacy issues (among
other things). I would not really recommend anyone to use such
configuration for enterprise networks. As such, I don't see how this
would work with a reasonable STA configuration (use passive scanning or
only wildcard SSID in Probe Request frames) and to address such a use
case, multi-BSS design with another beaconing BSS would be used instead.
Jouni Malinen PGP id EFC895FA
More information about the Hostap