cancel
Showing results for 
Search instead for 
Did you mean: 

All set up -- but a couple of questions

jason_sparrow
Contributor II
Well, I have just set up my r600's in the house, and I cannot believe how easy it was, even via the web host!

Now that's all done, I have noticed that some devices appear to be connected to both ap's at the same time. I have tried tweaking the power settings etc but they still seem to hang on. Is there anything else I have missed that I should try?

Also, is there a way of renaming each device in the list rather than having to guess what the ip/mac address is?

Thanks!
14 REPLIES 14

john_d
Valued Contributor II
I've noticed that ever since recent standalone firmwares (like 100.0 and above), there's a bug where sometimes even when a client disconnects/roams, it still shows up in the radio's MAC address list for a while. Sorry, I think that's probably a UI bug currently. I wouldn't start tweaking your power settings because of that, because in reality your client is only on one or the other AP, definitely not both.


And no, I'm not aware of any way in standalone AP firmware to see the name of the device rather than the MAC. This is a form of reporting supported when you have a ZoneDirector, though. Without a ZD, I wouldn't sweat too much effort in tracking down where your clients are.


(If you believe you have a sticky client roaming problem, you would want to look into the smart-roam or bss-minrate options at the command line. However, personally I would not suggest messing with either one unless you are really noticing a significant roaming issue. In my experience, the smart-roam technique of forcibly disconnecting clients that the AP considers weak results in more trouble than benefit with modern clients. Some devices won't bother reconnecting to wifi again for a long time.)

jason_sparrow
Contributor II
Thanks John,

I'm not sure my capabilities are up to command line stuff, well not yet anyway!

Everything seems to be working well at the moment.

Using my iPhone as a gauge, I have full bars throughout the house, and then for outside I have a Unifi 5g AP to take care of that which I have turned the power right down to keep it outside.

I suppose I should just leave the settings alone for now and see how it goes.

However, do you think I should turn the power back up to full on the 600's?

That was the default setting when I I stalked them.

And lastly, I thought I would check the firmware and perform an update on them if there was one available, however it came back with a warning about not being able to connect or something similar. Just wondered if there was anything specific I should do or, are the firmware updates for the aps only available to 'paid up' members?

john_d
Valued Contributor II
(1) Yes, I would recommend just leaving advanced roaming parameters via the command line alone unless you are 100% sure you got a problem that needs to be solved. I found that most of the advice floating around in that regard no longer apply to devices made within the last couple of years. But if you do start fooling around with the CLI, make a note of all the things you changed — there's not an easy way otherwise to remember or restore things to default short of factory-resetting the AP's.

(2) I would recommend turning the power up to full (the default) unless the two AP's are really close to each other and / or need to share the same channel. In Ruckus's ZoneDirector manual, they have some best practice guidelines, and they (roughly paraphrasing) recommend that ZoneFlex AP's be set at max power because BeamFlex inherently reduces interference compared to omnidirectional antennas, thanks to their ability to direct/focus energy in the direction of the client.

(3) The ability to check for updates from the web admin interface hasn't worked for a while. Nowadays, the way to check is to go to the Downloads page for your AP from the Ruckus support portal: https://support.ruckuswireless.com/products/68-zoneflex-r500#firmwares

Standalone firmware is supposed to be downloadable by all members with accounts, even those without support contracts. If you encounter a standalone firmware that you cannot access, either file a support ticket or post something here. Historically, that's all it's taken for someone from Ruckus to fix the access controls.

jason_sparrow
Contributor II
Ok, advice noted!

One more thing (hopefully!), is it better to give them a static IP?