topic ap设备的mac与bssid转换规则 in Community and Online Support Services

ap设备的mac与bssid转换规则

xin_yu_jeqze1ee — Tue, 15 Oct 2019 06:15:54 GMT

X需要了解到 ap设备的mac与bssid转换规则

Re: ap设备的mac与bssid转换规则

michael_brado — Tue, 15 Oct 2019 16:24:04 GMT

In English...?

Re: ap设备的mac与bssid转换规则

xin_yu_jeqze1ee — Wed, 16 Oct 2019 02:21:18 GMT

Our customers need to understand the mac and bssid conversion rules for commercial ap devices.

Re: ap设备的mac与bssid转换规则

xin_yu_jeqze1ee — Wed, 16 Oct 2019 03:21:13 GMT

our devices is

Ruckus R300 Multimedia Hotzone Wireless AP

Version: 2.5.0.1.174

Ruckus R310 Multimedia Hotzone Wireless AP

Version: 3.6.0.0.709

thank you

Re: ap设备的mac与bssid转换规则

michael_brado — Wed, 16 Oct 2019 16:00:12 GMT

I do not understand "mac and bssid conversion". You can authenticate devices by MAC address, to BSSID Wireless LANs.

APs are running different versions of SmartZone firmware, which require a SmartZone controller to manage them.
A SmartZone controller can manage one Zone (SZ-100, vSZ-E) with one firmware version, or can manage multiple Zones (SZ300, vSZ-H) that can have different firmware versions.
Do you have a local Ruckus reseller, who offers advice for network planning if you might need other hw/sw?

Re: ap设备的mac与bssid转换规则

john_d — Wed, 16 Oct 2019 16:12:12 GMT

Perhaps Xin is referring to how Ruckus APs generate their BSSID MAC addresses from the base MAC address? Either way we could use more detail on why those values matter -- I can't imagine wanting to derive those without just asking the APs via SmartZone API or SNMP....

Re: ap设备的mac与bssid转换规则

brian_powers — Wed, 16 Oct 2019 16:22:28 GMT

That logic is not overly complicated though.

Assume APs base MAC Address - D8:38:FC:38:75:F0

2.4 GHz base MAC Address - D8:38:FC:38:75:F8

5 GHz base MAC Address - D8:38:FC:38:75:FC

Base MAC address would be used for mesh networks.

The 7th digit increases by 4 (in hex format) from the base MAC address. Once all of the hex options are used there, the 12th digit increases by 1 and the 7th digit restarts in incrementing. This is based off of their wlan0/1 base MAC address. See below.

rkscli: get wlanlist

name status type wlanID radioID bssid ssid

--------------------------------------------------------------------------------------------------

wlan0 up AP wlan0 0 d8:38:fc:38:75:f8 SSID01

wlan1 up AP wlan1 0 d8:38:fc:78:75:f8 SSID02

wlan2 up AP wlan2 0 d8:38:fc:b8:75:f8 SSID03

wlan3 up AP wlan3 0 d8:38:fc:f8:75:f8 SSID04

wlan4 up AP wlan4 0 d8:38:fc:38:75:f9 SSID05

wlan5 up AP wlan5 0 d8:38:fc:78:75:f9 SSID06

wlan6 up AP wlan6 0 d8:38:fc:b8:75:f9 SSID07

wlan7 up AP wlan7 0 d8:38:fc:f8:75:f9 SSID08

wlan8 up AP wlan8 0 d8:38:fc:38:75:fa SSID09

wlan9 up AP wlan9 0 d8:38:fc:78:75:fa SSID10

wlan10 up AP wlan10 0 d8:38:fc:b8:75:fa SSID11

wlan11 up AP wlan11 0 d8:38:fc:f8:75:fa SSID12

wlan12 up AP wlan12 0 d8:38:fc:38:75:fb SSID13

wlan13 up AP wlan13 0 d8:38:fc:78:75:fb SSID14

wlan14 up AP wlan14 0 d8:38:fc:b8:75:fb SSID15

recovery-ssid down AP wlan102 0 00:00:00:00:00:00 Recover.Me-3875F0

wlan32 up AP wlan32 1 d8:38:fc:38:75:fc SSID01

wlan33 up AP wlan33 1 d8:38:fc:78:75:fc SSID02

wlan34 up AP wlan34 1 d8:38:fc:b8:75:fc SSID03

wlan35 up AP wlan35 1 d8:38:fc:f8:75:fc SSID04

wlan36 up AP wlan36 1 d8:38:fc:38:75:fd SSID05

wlan37 up AP wlan37 1 d8:38:fc:78:75:fd SSID06

wlan38 up AP wlan38 1 d8:38:fc:b8:75:fd SSID07

wlan39 up AP wlan39 1 d8:38:fc:f8:75:fd SSID08

wlan40 up AP wlan40 1 d8:38:fc:38:75:fe SSID09

wlan41 up AP wlan41 1 d8:38:fc:78:75:fe SSID10

wlan42 up AP wlan42 1 d8:38:fc:b8:75:fe SSID11

wlan43 up AP wlan43 1 d8:38:fc:f8:75:fe SSID12

wlan44 up AP wlan44 1 d8:38:fc:38:75:ff SSID13

wlan45 up AP wlan45 1 d8:38:fc:78:75:ff SSID14

wlan46 up AP wlan46 1 d8:38:fc:b8:75:ff SSID15

wlan47 up AP wlan47 1 d8:38:fc:f8:75:ff SSID16

The interesting note here is that the 2.4 GHz radio gets wlans 0-14 and the 5 GHz radio gets wlans 32-47. Doing the math there, the 2.4 GHz radio is limited to 15 SSIDs while the 5 GHz radio can actually accept 16. This looks to be because of the recovery-ssid shown above assumed to be 2.4 GHz only.

Note some AP models only support up to 16 BSSIDs, so it'd be the 1st 8 per frequency.

We had to figure out all of this so we could write some python scripts to rename APs within an Ekahau file automatically vs. manually.

Re: ap设备的mac与bssid转换规则

michael_brado — Wed, 16 Oct 2019 16:47:37 GMT

Thanks John, that flipped a switch, and yes Brian thanks.

We have KBA-4495: BSSID to AP MAC Address translation

https://support.ruckuswireless.com/articles/000004495

Re: ap设备的mac与bssid转换规则

xin_yu_jeqze1ee — Thu, 17 Oct 2019 10:31:00 GMT

Thank you very much for your answer. You have helped me a lot and the customer's problem has been solved.

Re: ap设备的mac与bssid转换规则

xin_yu_jeqze1ee — Thu, 17 Oct 2019 10:34:04 GMT

hi, Michael Brado,
I can't open the content you provided。
the content prompt
‘We're sorry, but something went wrong.We've been notified about this issue and we'll take a look at it shortly.’

Re: ap设备的mac与bssid转换规则

michael_brado — Thu, 17 Oct 2019 16:08:25 GMT

I can share the details, much like Brian wrote.

Access Point MAC offset for WLANs:

BSSIDs generated are based on AP’s base MAC Address.
Current mechanism is described as follows.

For BSSID (WLAN’s MAC addresses):
Assume the base MAC of an AP is 00:01:02:03:04:50  (note, the last 4 bits of the last octet is always 0 in a base MAC),
The BSSID’s of the first radio (2.4G) is:

00:01:02:03:04:58  (0x50 + 0x8)
00:01:02:43:04:58
00:01:02:83:04:58
00:01:02:c3:04:58
00:01:02:03:04:59  (0x50 + 0x9)
00:01:02:43:04:59
00:01:02:83:04:59
00:01:02:c3:04:59

And the BSSID’s for the second radio (5G in your case) is

00:01:02:03:04:5c  (0x50 + 0xc)
00:01:02:43:04:5c
00:01:02:83:04:5c
00:01:02:c3:04:5c
00:01:02:03:04:5d (0x50 + 0xd)
00:01:02:43:04:5d
00:01:02:83:04:5d
00:01:02:c3:04:5d

Note the bits change in the 4th octet. The bit format of 4th octet in base MAC is always 00xxxxxx.

For Ethernet MAC addresses, they are (Base MAC +3) to (Base MAC +7)