In this episode of the Clear to Send podcast, the hosts revisit the classic Wi-Fi design question: “How many SSIDs is too many?” While the long-standing technical advice has always been to minimize SSIDs to conserve airtime, the discussion explores how modern standards—like 6 GHz, multiple BSSIDs, and changing client habits—impact this rule of thumb.
The episode provides technical discussion on management overhead, strategies for network consolidation, and advice on how to communicate these technical limitations to management.
Supporting Data
Beacon airtime per SSID, per radio
| Beacon data rate | Airtime per SSID | 4 SSIDs | 8 SSIDs |
|---|---|---|---|
| 1 Mbps | ~2.0% | ~8% | ~16% |
| 6 Mbps | ~0.35% | ~1.4% | ~2.8% |
| 12 Mbps | ~0.18% | ~0.7% | ~1.4% |
| 24 Mbps | ~0.10% | ~0.4% | ~0.8% |
Based on ~10 beacons/sec at a 100 TU beacon interval and a ~200-byte beacon frame.
Co-channel multiplication – 4 SSIDs on the channel
| Beacon data rate | 1 AP | 3 co-channel APs | 5 co-channel APs |
|---|---|---|---|
| 1 Mbps | ~8% | ~24% | ~40% |
| 12 Mbps | ~0.7% | ~2.2% | ~3.6% |
| 24 Mbps | ~0.4% | ~1.2% | ~2.0% |
The headline stat for the episode: it is not the SSID count that kills you, it is the SSID count multiplied by co-channel APs and divided by your data rate.
“We need a new SSID” → the better answer
| The request | Better solution |
|---|---|
| Different PSK per IoT device type | One SSID with MPSK / iPSK / DPSK |
| Separate SSID per department | One 802.1X SSID + RADIUS role/VLAN assignment |
| Contractor network | Same 802.1X SSID, different role |
| Temporary SSID for an event | Scheduled SSID, scoped to those APs, with an expiry date |
| Marketing wants a branded guest SSID | One guest SSID, brand the captive portal instead |
