4 ms·
Ruckus [0] gear is generally considered to be the step-up from Ubiquiti (although their point-to-point stuff is really good). The RF design is supposedly more c
by eddyg 6y ago
Ruckus [0] gear is generally considered to be the step-up from Ubiquiti (although their point-to-point stuff is really good). The RF design is supposedly more complex and advanced in Ruckus APs with advanced antennas and their proprietary BeamFlex technology... not just reference-design SoC stuff.
See this reply (and others in the topic) for some “insight”: https://www.reddit.com/r/networking/comments/9vj2dh/comment/e9l3lya https://www.reddit.com/r/networking/comments/9vj2dh/comment/...
Also... since I’ve been looking at Ruckus APs recently (they offer several WiFi 6 APs) I learned that their APs have two part numbers with different prices. The '901' part numbers ship with Solo AP firmware that can run in either Standalone mode or will join a Ruckus ZoneDirector or SmartZone controller. The less expensive '9U1' part numbers ship with “Unleashed” code that will not connect to a ZD/SZ controller, and instead look for a local Unleashed network. The price difference is due to support entitlements; controllers license number of APs per controller/cluster, and Unleashed support is one license for up to 25 APs in the network. (Seems like most home users go with Unleashed. [1])
Also, one thing to note with some Ruckus APs (like those that support 802.11ax) are the PoE requirements. The RF power is reduced and/or some features become unavailable depending on the power available. (It’s all listed on the AP data sheets, just need to be aware of it.)
[0] https://www.commscope.com/product-type/enterprise-networking/wireless-access-points/ https://www.commscope.com/product-type/enterprise-networking...
[1] https://www.commscope.com/product-type/enterprise-networking/control-management/controller-less/controller-less/ https://www.commscope.com/product-type/enterprise-networking...
- amluto 6y agoThanks for the pointer. I’m seriously considering jumping off the UniFi bandwagon due to their mounting technical debt. UniFi seems to be stuck on MongoDB 3.4 and Java 8. I can live with that, even though it’s a sign that their developers are not keeping up. The straw that’s about to break the camel’s back that that they’re stuck on an old version of dropbear. The latest OpenSSH refuses to negotiate public key auth with it because the old dropbear doesn’t support modern signature algorithms. (Yes, I know how to override OpenSSH’s config for this. No, I shouldn’t have to.)