Thanks for posting the screenshots! In all MetaGeek products, we have two ways of grouping SSIDs:
Physical Grouping: Where we group together virtual SSID's on the same AP.
Logical Grouping: Where we group together all of the SSID's that are part of the same network.
Each SSID has to have a unique MAC address for networking to work like it should, so if you have a few virtual SSID's on the same AP, the AP will just increment the last octet of the AP to differentiate them, like this:
D1:2F:45:FB:58:A2 - MetaGeek-Guest
D1:2F:45:FB:58:A3 - MetaGeek-Private
D1:2F:45:FB:58:A4 - MetaGeek-Test
So to inSSIDer, the AP's MAC address is D1:2F:45:FB:58:Ax, since the last nibble gets incremented, the x is a wildcard. We assume that those MAC addresses are the same AP, so when you name one, they all get named together.
The only vendor that we know of that departs from this naming scheme is Ruckus, who increments a nibble in the middle of the MAC address, and this does break this functionality in our software.
I'd say that there are two possibilities for what is going on here:
1. Your vendor increments MAC addresses in a non-standard way (it would be interesting to hear which vendor you are using)
2. This is a freak incident where have three AP's with random MAC addresses, but they just happened to all be identical except for the last nibble. Crazy!
Joel, Mobility+, ECSE, CWNE #233
Technical Trainer
MetaGeek
Bookmarks