I am setting up an AP and have create virtual wifi interfaces for my 3 different SSIDs. They are children of the master interface.
I don’t want to assign a SSID to the master interface, as I don’t want anyone to connect to it. Is that a valid approach? If so, how do I prevent someone from connecting to the master wifi interface?
If not valid, must I delete and child virtual interface and assign its SSID to the master? Or what’s the right way to do this?
I’m with the OP: It’s inconvenient not having this level of control, most WiFi systems allow for enabling/disabling SSIDs in a more flexible way. Moving a most-likely-to-be running (E)SSID to master is just a design constraint that exists with these products. If this is not done, then leaving it ‘on’ just to leave it ‘on’ increases the attack surface for no reason and don’t forget the performance impact: there is always overhead to carrying SSIDs on a channel, from management and control frames like beacons, probe responses, etc., which are usually sent at realtively low datarates, so don’t really see the need to absorb this too.
Feel free to do that on different bands, but how do you propose to have virtual interfaces without a functioning primary? In my recollection the primary is sine qua non