Header Only - DO NOT REMOVE - Extreme Networks
Solved

BSS Vendor identification in ADSP for Ubiquiti/Cisco Meraki

  • 16 September 2019
  • 3 replies
  • 116 views

Hello,

Some non-Extreme vendors utilize a process that changes the MAC OUI portion of the MAC address when offering multiple WLANs.

Ex.
https://help.ubnt.com/hc/en-us/articles/115002536648-UniFi-BSSID-to-MAC-Mapping
https://documentation.meraki.com/MR/WiFi_Basics_and_Best_Practices/Calculating_Cisco_Meraki_BSSID_MAC_Addresses

As the BSSIDs do not utilize OUIs that are registered in IEEE oui.txt, AirDefense fails to identify device vendor. Is there a mechanism for getting AirDefense to identify the device vendor properly in this situation?
icon

Best answer by Chris Kelly 16 September 2019, 19:00

Totally understand about the MBSSID incrementation. Just odd that they change the OUI after the base BSSID.
But yes, forgot to add that you CAN modify an existing OUI.txt file and try to import that into the system. (instead of an Internet fetch of the current file). I guess it just depends on how these OUI's are being implemented.
If it's random, then you''ll constantly be updating that file to no end.
If they just simply have some small set of custom OUI's that they stick with, then that's totally manageable, if you want to maintain your own custom OUI.txt file.
View original

3 replies

Userlevel 6
Frank,
Are the OUI's not even listed within the currently posted oui.txt file on the IEEE site?
http://standards-oui.ieee.org/oui/oui.txt

Wondering if the OUI file in your AirDefense system is maybe stale and needs updating.

Otherwise, if they are in fact simply utilizing some non-standardized OUI or it's random, then there is no way to manually modify the actual oui.txt within AirDefense.

The 'fix' for this would be for this vendor to register the OUI's they are using.
Or...request a feature for AirDefense that allows for user-definable OUI's to be added to the system.
Hi Chris,

Only the initial, BSS1 MAC is registered with IEEE. After the first MAC, they start to increment bits in the OUI portion of the MAC address, and none of the results are registered with IEEE.

I wouldn't mind that feature request, in the short term I think I will try and work around this by creating a custom OUI.txt file and importing it into the box.
Userlevel 6
Totally understand about the MBSSID incrementation. Just odd that they change the OUI after the base BSSID.
But yes, forgot to add that you CAN modify an existing OUI.txt file and try to import that into the system. (instead of an Internet fetch of the current file). I guess it just depends on how these OUI's are being implemented.
If it's random, then you''ll constantly be updating that file to no end.
If they just simply have some small set of custom OUI's that they stick with, then that's totally manageable, if you want to maintain your own custom OUI.txt file.

Reply