Ruckus Unleashed 200.5 has bug

After testing the 200.5 version of the defective R500 R600, will lead to a series of models, wireless LAN appears high delay, packet loss and other cases, only by reducing version to solve the problem, hope that the official personnel test, to fix the problem.

The problem occurs if you are using Radius authentication with only highest encryption setting selected in NPS network policy options. So... the trick would be allow less powerful encryption settings along with No Encryption setting. So far Ruckus (or anyone else) hasn't been able to tell me in what exactly does those encryption settings do.

Hi, What is your case number please? And have you or would you please ask your Tech Support to file a bug?I don't think there is any type issue reported yet (that I can find), and you seem to have a set of reproduceablesteps. Thanks!

Ruckus technical support is terrible I reopened a hotel that we had over 50 access points and was gonna buy about 75 more but they will not help without the old owners email which is impossible because he died

Hello Electa, I hope the engineer mis-understood you! Do you have a Serial Number from a controller that managed the APs? I will look in our systems to determine your previous account and get you some help.

I have tried talking to supervisors there and was supposed to have a ticket assigned to me so we can fix this we have about 50 of your units and was gonna buy about 100 more but the owner of the hotel wants to not use your company any longer due to your poor customer service if I can at least get the one at my house going I might be able to talk home into going forward with doing business but we will see call me at 727 320 7813 mike

My mesh set-up is experiencing the problem that looks similar to what Kari is describing, except it is not happening all the time - only after my mesh has been operating for a few days (~10 or so), and the problem is only seen from stations connected to the MAP (when connected directly to RAP all is fine). The built-in MAP to RAP speed test isn't showing any difference to when everything is operating normally - ~450M both ways.

I also don't use RADIUS or change any encryption settings.

The problem appeared after upgrade to 200.5, and can be resolved by rebooting the MAP.

However, couple weeks ago rebooting just the MAP didn't work - had to reboot the RAP as well, and all came back just fine, well, until today when I had to reboot the MAP to make it come to senses again.

In all cases I didn't notice APs shift 5 or 2.4 channels significantly with reboots - I'm guessing they were already on optimal channels, and came back to the same channels after reboot.

I upgraded to firmware version: 200.5.10.0.283 and as soon as I did. I lost my guest network. Prior when someone accessed the guest network they would be redirected to the captive portal where they would enter a guest pass. Now they get directed to the admin login page. Ruckus support is at a loss.

I have an open ticket with ruckus support currently. They told me that I have to set rules in my firewall to allow ports 8090, 8099, 9997 & 9998 from your guest zone to the zone that your APs are in. I have discovered that you need to expand that list to include 80 (http) and 443 (https). It sounds like they might be working to correct this loophole.

That is great news. Did ruckus support provide you this build directly? I do not see it available in the software section of the support site. So now with this build you do not have to create the new allowance rules for guest to management traffic?

Ruckus Support: Do you have an estimated time frame for the release of the build that Jim Balla is referencing (200.5.10.0.291), or one with the same fix on it for landing page redirection? I am holding off on deploying because if I don't have to modify rules on 300+ firewalls to accommodate this change in unleashed, I would rather not.