Unleashed 200.9.10.4.233 firmware

[sander_groen]

Hi all,

I see that unleashed firmware 200.9.10.4.233 has been released if you look on the master AP via the browser. I don't yet see it on the site hence there are no release notes available yet. I succesfully upgraded my 3 ap's (2 x R710 and 1 x R610) to unleashed 200.9.10.4.233 however 2 AP's (except the master) were having reboot loops. They come online and shortly after they were rebooting again. I flashed back to version 200.9.10.4.212. Was the release of 200.9.10.4.233 premature?

Thanks!

[syamantakomer]

Hi All,

So far we got few cases reported by our forum members and we are working internally to find root cause and a fix.

[andrew_s]

@syamantak_omer

for awareness currently back on 200.9.10.4.233 as backout failed, still having weird issues.

found glitch on 200.9.10.4.233 where if WLAN was member of a custom AP Group 2.4Ghz network failed to operate or broadcast correctly on 1 of my WLANs, had to delete custom AP group and cycle affected WLAN, WLAN operated IOT devices that only operate on 2.4GHz so it took some time to pinpoint the issue as it worked for a phone but all IOT devices were down due to 2.4Ghz issue even though it said it was up and healthy in GUI, it wasn't broadcasting.

Seems like when it was a member of the AP Group, you couldn't edit or make changes to specific WLAN settings due a a possible permissions or ACL issue. 

[seth_johnson]

Seeing kernel panics / restarts on multiple .233 systems as well. 

[antoine_hannema]

I've upgraded both R720 and R510 to 200.9.10.4.233. Everything is working like before, except 'Application Visibility' isn't working anymore.

In the WLAN settings, this option is enabled, but in the services tab no more graphs are showing up (even waited for days...).

Anyone else having this problem? Any suggestions to get the application visibility working again in 200.9.10.4.233?

[durmus_akcan]

I did a downgrade of the firmware to 200.8.10.3.290 after the reboot issue with 200.9.10.4.233. Yesterday evening it rebooted again continiously. I found the following errors in the syslog.

Mar 29 22:34:24 Ruckus-Wireless mDNSResponder: mDNSPlatformSendUDP got error 99 (Cannot assign requested address) sending packet to FF02:0000:0000:0000:0000:0000:0000:00FB on interface 169.254.17.11/br0/32

Is there a workaround to solve this problem?