Nebula should correlate MLO MAC Addresses to Source Device

jj38100

Currently with the WBE130 and Wifi 7 and MLO enabled, MAC addresses associated with the MLO connected are not associated to the Device MAC of the Client so they show up as other wired clients. The devices, therefore Nebula, know these MACs are associated as evident in the connection logs.

Zyxel_Judy

Hi @jj38100 ,

We have successfully reproduced and confirmed the issue on our end. This will be addressed in a future firmware update. We recommend keeping an eye on the WIRELAN News & Releases section for updates on enhancements and fixes.

Zyxel_Judy

Hi @jj38100 ,

I'd like to clarify your issue, so please correct me if I’m wrong.

Your issue is that your MLO wireless client, such as a phone, connects to the NWA130BE with the MLO feature enabled. When you check the Clients tab, you find that your MLO phone's MAC address is listed under the "Wired" client option, not under the "Wireless" client tab.

If this is correct, please share your phone's MAC address with us. Additionally, please enable Zyxel support Zyxel support and provide us with the name of your Nebula organization/site here or via private message by clicking on my account > Message. We'll help to check it.

jj38100

Correct, there are three clients listed, the Wireless Client has my device MAC, the two additional Wired Clients have the MAC addresses for the MLO feature (1 per band, this client supports only 2 bands).

If I go into the wireless client and look at the event log, I see the log entries that show the Wired Clients MAC addresses show up when it connects to the band for MLO. See Screenshots. I suppose the other thing is the Wireless Client doesn't reflect the Bands currently in use. Quite frankly the client entry only shows Channels as opposed to Band which I get channels are related to the band, but it would be a nice visual add

I'll PM you my Nebula Org and Site via PM

PS I do not have MAC address randomization enabled on this client (Google Pixel 8 Pro)

Zyxel_Judy

Hi @jj38100 ,

Currently, the Google Pixel 8 Pro is connected to the non-MLO SSID called PRTYSLW, making it difficult for us to clarify the issue. Could you please connect the Google Pixel 8 Pro to the MLO SSID for 2-3 minutes to reproduce the issue (Clients show Wired clients)? After that, download the diagnostic file and send it to us via private message. We'll review it and share our findings with you.

jj38100

How do you download the diagnostic file? Like each device diagnostic or is there a Nebula way to do this for the entire site? Doesn't seem to be, maybe there should be 😁

The switch that shows these MLO addresses connected, the GS1920v2 doesn't seem to have an option so I'll PM you the Tech Support File. I also did it for the WBE130 Access Point

FYI, I'll be replacing all the GS1920s with XMG1915s today, I'll report back if it makes a difference. I still don't have the second WBE130 so I won't be keeping my Pixel 8 Pro on the SSID with MLO enabled

Zyxel_Judy

Hi @jj38100 ,

We have received the diagnostic files for your NWA130BE and GS1920. We will review them and inform you of any findings.

Zyxel_Judy

Hi @jj38100 ,

We have successfully reproduced and confirmed the issue on our end. This will be addressed in a future firmware update. We recommend keeping an eye on the WIRELAN News & Releases section for updates on enhancements and fixes.