nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

GUI for 'Directed MC/BC' in Unleashed 200.15 doesn't actually change the setting.

GollyJer

In Unleashed 200.15, GUI provides false feedback when toggling the "Directed MC/BC: Enable" setting. Checking or unchecking the box in the GUI updates the Directed MC/BC Threshold variable and the GUI's own visual state, but it fails to modify the underlying Directed Multicast Boolean in the system configuration.

I only discovered this after having issues with my mDNS and Matter/Thread network and digging into the settings by hand with the CLI.

Posting here not for help, but to surface the bug.

Find more posts tagged with

Accepted answers

sanjay_kumar

Hi,

I have verified this and I can clearly see the changes happening on GUI and CLI.
But I could not test it in 200.15, I tried in 200.19 as the issue is fixed in later releases.
Also, 200.15 is the last supported version for R610s.

All comments

Rohit_W

Hello,

I would recommend you to create a ticket with us to troubleshoot this issue.

Please use the below link to create a new ticket:
https://support.ruckuswireless.com/contact-us

Regards,
Rohit Walawalkar
Technical Support Engineer -EMEA
Work Hours: Monday-Friday, 9 AM to 5 PM GMT
Location: India

sanjay_kumar

Hi,

After enabling the "Directed MC/BC" setting, could you please confirm how you have verified that the setting has not taken effect?
Please confirm so that we can review it.

GollyJer

Hi Sanjay,

I verified the issue by comparing the visual state in the Unleashed GUI against the actual configuration output in the CLI.

When toggling the "Directed MC/BC" checkbox in the GUI, the interface appears to save and visually reflect the change. However, when SSHing into the controller and running show wlan all (or more specifically, show wlan all | include "Name|Directed Multicast"), the output clearly shows that the underlying configuration variable for Directed Multicast remains unchanged.

Because the GUI and the actual configuration state become desynchronized, the only way I could successfully enforce the correct multicast state across my R610 APs was to bypass the controller GUI entirely and apply the changes directly via the CLI.

sanjay_kumar

GollyJer

ok, so fixed in later releases but not for R610s running 200.15, which is what I'm running. No big deal. I reported the issue to hopefully get the bug fixed. Sad to hear my devices won't be supported going forward though. 😥

GollyJer

😀