topic Re: How to make “no qos directed-multicast” persist across reboots? in Unleashed

How to make “no qos directed-multicast” persist across reboots?

Zuul — Mon, 12 Apr 2021 05:28:13 GMT

I’m running an R650 (Unleashed 200.9.10.4.233) with a number of wireless Sonos speakers on my network. I’ve applied the fix through the CLI to allow the Sonos controller to see the speakers:

enable

config

wlan MyWifiNetwork

no qos directed-multicast

end

Unleashed confirms the settings have been saved.

However whenever I reboot my AP, I have to reapply the fix or my speakers remain unavailable.

How can I make this change persist across reboots?

Re: How to make “no qos directed-multicast” persist across reboots?

Zuul — Tue, 13 Apr 2021 14:21:03 GMT

After additional troubleshooting, I've determined that this setting does get saved but does not seem to be applied after the AP restarts so this looks to be a bug to me. I was able to reproduce this with 200.9.10.4.212 as well.

To test this, I ran the commands in the OP on my AP then immediately rebooted it. About 10 minutes after the AP came back up, I was still unable to see my Sonos speakers or my AirPrint printer (both of which use multicast AFAIK).

So I sshed into the AP and got info on my AP:

Welcome to Ruckus Unleashed Network Command Line Interface
ruckus> enable
ruckus# config
You have all rights in this mode.
ruckus(config)# wlan MyWifiNetwork
The WLAN service 'MyWifiNetwork' has been loaded. To save the WLAN service, type 'end' or 'exit'.
ruckus(config-wlan)# show
WLAN Service:
ID:
2:
NAME = MyWifiNetwork
Tx. Rate of Management Frame(2.4GHz) = 2.0Mbps
Tx. Rate of Management Frame(5GHz) = 6.0Mbps
Beacon Interval = 100ms
SSID = MyWifiNetwork
Description = MyWifiNetwork
Type = Standard Usage
Authentication = open
Encryption = wpa2
Algorithm = aes
Passphrase = REDACTED
FT Roaming = Enabled
802.11k Neighbor report = Enabled
Web Authentication = Disabled
Authentication Server = Disabled
Called-Station-Id type = wlan-bssid
Tunnel Mode = Disabled
Background Scanning = Enabled
Max. Clients = 100
Isolation per AP = Disabled
Isolation across AP = Disabled
Zero-IT Activation = Disabled
Priority = High
Load Balancing = Disabled
Band Balancing = Disabled
Dynamic PSK = Disabled
Rate Limiting Uplink = Disabled
PerSSID Rate Limiting Uplink = 0
Rate Limiting Downlink = Disabled
PerSSID Rate Limiting Downlink = 0
Auto-Proxy configuration:
Status = Disabled
Inactivity Timeout:
Status = Enabled
Timeout = 1 Minutes
VLAN-ID = 1
Dynamic VLAN = Disabled
Closed System = Disabled
Https Redirection = Disabled
OFDM-Only State = Disabled
Multicast Filter State = Disabled
Directed Multicast= Disabled
802.11d State = Enabled
Force DHCP State = Disabled
Force DHCP Timeout = 10
DHCP Option82:
Status = Disabled
Option82 sub-Option1 = Disabled
Option82 sub-Option2 = Disabled
Option82 sub-Option150 = Disabled
Option82 sub-Option151 = Disabled
Ignore unauthorized client statistic = Disabled
STA Info Extraction State = Enabled
BSS Minrate = Disabled
DTIM period = 3
Directed MC/BC Threshold = 0
Call Admission Control State = Disabled
PMK Cache Timeout= 720 minutes
PMK Cache for Reconnect= Enabled
NAS-ID Type= wlan-bssid
Roaming Acct-Interim-Update= Disabled
PAP Message Authenticator = Enabled
Send EAP-Failure = Disabled
L2/MAC = No ACLS
L3/L4/IP Address = No ACLS
L3/L4/IPv6 Address = No ACLS
Precedence = Default
Proxy ARP = Disabled
Device Policy = No ACLS
Vlan Pool = No Pools
Role based Access Control Policy = Disabled
SmartRoam = Disabled Roam-factor = 1
White List = No ACLS
URL Filtering = Disabled
Application Recognition & Control = Enabled
Apply ARC Policy = NO POLICY
WIFICalling Enabled= Disabled
WIFICalling Profile= 0
Client Flow Data Logging = Disabled
Wlan Bind = all
Client Connection Data = Disabled
Transient Client Management = Disabled
80211w-pmf = Disabled

ruckus(config-wlan)# exit
The WLAN service 'MyWifiNetwork' has been updated and saved.
Your changes have been saved.
ruckus(config)# exit
Your changes have been saved.
ruckus# exit
Exit ruckus CLI.

So, directed-multicast is marked as disabled.

However, upon exiting (saving changes) with no changes made, I was able to see my AirPrint printer and Sonos speakers within a few seconds.

By simply re-saving the AP configuration with no changes, I was able to get everything working again so this sounds like a bug to me. Should I report this or am I missing something?

Re: How to make “no qos directed-multicast” persist across reboots?

syamantakomer — Mon, 19 Apr 2021 19:15:44 GMT

Hi Derek,

Refer below KBA and see if that helps. If not, feel free to open a case with support and report the issue.

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

Re: How to make “no qos directed-multicast” persist across reboots?

Zuul — Mon, 19 Apr 2021 19:43:46 GMT

Hi Syamantak,

I can't view that article but I can confirm that the issue I reported persists. It seems that simply re-saving the WLAN at the CLI is required to get multicast working properly following a reboot.

Thanks.

Re: How to make “no qos directed-multicast” persist across reboots?

syamantakomer — Mon, 19 Apr 2021 19:46:10 GMT

Hi Derek,

I just tried accessing the link again and its working for me.

Are you getting any error?

Re: How to make “no qos directed-multicast” persist across reboots?

Zuul — Mon, 19 Apr 2021 20:53:03 GMT

Hi Syamantak,

"To access that KB Article please upgrade your support account"

Thanks.

Re: How to make “no qos directed-multicast” persist across reboots?

john_d — Sun, 25 Apr 2021 04:46:22 GMT

I'm seeing the same behavior with Sonos speakers and also LG TVs. On 200.9.10.4.233, if I reboot the master AP, when the network comes up, Sonos speakers don't show up in AirPlay. 100% reproducible. However, if I reboot a slave instead of a master, this doesn't happen.

If I just go into a wlan in the unleashed CLI and save any WLAN config (which disconnects and reconnects all clients), then it works again.

Looking at both the supportinfo and the unleashed CLI, the directed multicast and directed threshold settings are both correctly shown and not different in the failing or success state.

(I'm using a pair of R750s)

The article is otherwise correct that what gets Sonos wireless-connected speakers working is "no qos directed-multicast" and "directed-threshold 0" on each SSID.

Re: How to make “no qos directed-multicast” persist across reboots?

john_d — Sun, 25 Apr 2021 05:18:39 GMT

I just looked through a diff of the supportinfo.txt before and after re-deploying the network and don't see any differences, all the rpmkeys are the same and the QOS info is all the same too. I don't know what else to look for, but I've repeated this experiment 2 more times and can confirm the symptoms, it seems like the directed-threshold and directed-multicast settings don't apply properly if the master AP in unleashed reboots.

Re: How to make “no qos directed-multicast” persist across reboots?

syamantakomer — Sun, 25 Apr 2021 07:14:39 GMT

Hi All,

If you are able to reproduce the issue, please report it to support so that they can check this further.

Re: How to make “no qos directed-multicast” persist across reboots?

john_d — Sun, 25 Apr 2021 16:06:10 GMT

I don’t have a support contract currently so I’m not sure if I’m the best one to file this. These R750s were just in my testing lab and saw this issue.

Re: How to make “no qos directed-multicast” persist across reboots?

Zuul — Mon, 26 Apr 2021 00:30:22 GMT

Same—I do not have a support contract and I am not going to purchase one just so I can report this bug. I am new to Ruckus in general so I am hoping someone there picks up on this even though I am reporting this without an active support contract. I am fairly confident this can be reproduced with the information I've already provided in this thread.

Re: How to make “no qos directed-multicast” persist across reboots?

Zuul — Mon, 26 Apr 2021 00:35:04 GMT

@john_dong FWIW I have worked around this issue by connecting my Sonos speakers in a wired configuration (i.e., the connection is no longer going through the R650), one speaker is wired directly to my switch. It's not ideal since (I think) I'd prefer to have my speakers connected directly to my AP but it's a workaround that gets me by.

Re: How to make “no qos directed-multicast” persist across reboots?

john_d — Mon, 26 Apr 2021 00:36:52 GMT

Yep that’s an okay workaround for a lot of Sonos speakers but the newest additions, the Roam and the Move, only work over infrastructure Wi-Fi and don’t work over SonosNet.

Re: How to make “no qos directed-multicast” persist across reboots?

syamantakomer — Fri, 21 May 2021 17:52:49 GMT

Hi @derek_fong

As discussed over the support case, issue is no longer observed on 200.9.10.4.243 version.

Re: How to make “no qos directed-multicast” persist across reboots?

Zuul — Fri, 21 May 2021 17:53:02 GMT

Thanks @syamantak_omer and to the Ruckus support team for being so responsive!