Destinova

Ultimately this is the kind of slant you are going to get from a sponsored forum...

Why discount the experience and technical expertise of others? The WFD delegates (of which I am one, as is Lee (wirednot) who was at the Meru presentation) make up some of the industry's top technical experts in independent IT analysis and influence. Go watch the videos and decide for yourself, that's all I'm saying. They offer presentation time to any vendor. The WFD folks are hands-on designing, installing and troubleshooting multi-vendor 802.11 installations every single day. I absolutely defer to their expertise and advice in this space. Look at the comments on the blog post. Keith Parsons, GT Hill for example - these are top echelon wifi experts. I'll restate from my earlier post: "Do your research and be educated to prevent long-term pain."

If anyone is interested in seeing some of the flaws in Meru's architecture and how they struggle to explain the technology while glazing over things with marketing-speak, here's some further reading: What Meru and Xirrus Need to Do | wirednot Meru Networks 802.11ac and Bonjour on Vimeo Beware the pitfalls of early adoption of 802.11ac - do not fall victim to the initial push from early-to-market vendors that aren't prepared to support you through all phases of 802.11ac and it's lifecycle. Do your research and be educated to prevent long-term pain.

Meru still hanging on I see. Likely a good eco-budget vendor for the UK folks but in North America they continue to fall short. No innovation I'm afraid and some lofty (and fundamentally incorrect) ideas around CCI and 802.11ac. Good luck with that. You know you're at the rope's end when you're competing with Xirrus.

There aren't really 'different' standards for PoE. There is PoE (802.3af) and PoE+ (802.3at). These are both IEEE standards. Any implementations outside of these two standards are non-standard proprietary iterations of the technology and may or may not work with proper af/at devices. Examples of non-standard versions of this include Cisco's original "Inline Power" which predated PoE as a standard, but is forwards compatible in most aspects.

AliG: There should be no password on your activation/hotspot SSID. Options here are set to Open/None for Authentication and Encryption. I am running 9.6.0.0 build 267

Ruckus' DPSK and Zero-IT config are working well for me. Credentials are passed and are encrypted (HTTPS) and authentication is handled via WPA2 and a PSK. Not sure what issue you are really facing here. Yes, the provisioning/activation SSID has to be forgotten. This is not an issue with the Ruckus system, but rather the device OS. Devices will tend to remember any SSID they connect to and especially connect to open SSIDs like the Zero-IT/Activation one you use for a Ruckus deployment. Forget it and the device connects just fine to the requisite SSID. Android phones are a pain simply for two reasons: Androids by default won't accept apps that are not from the Android market so this has to be turned off in the settings, and second; the OS is so fragmented each and every device handles the provisioning file so differently - I end up copying and pasting the DPSK into the device manually quite a lot.

Thank you. The CWNP does not churn out marketing drones who blather on about how their access point can defy the laws of physics and cover more area or service more clients because of their magic RF algorithm. RF is RF and you have to plan for it, and this means paying for a proper survey both pre-install and post-install. Quit being so cheap You know who you are.

The only issues I've had with Android devices have been those using the default browser. Chrome on Android works fine, as done manually copying the PSK to the device.

AirTight were recently featured as a presenter at Wireless Field Day 5, and have also acquired wifi genius Devin Akin. They are touted as the next up and comer in the wifi space and have some brilliant differentiators to other vendors. I would highly recommend taking a serious look at them, and also a glimpse at their presentations from WFD5. Wireless Field Day 5

I highly recommend Ruckus' zero-it activation process and dynamic PSK for guest access, it's brilliant. BYOD Solution | Ruckus Wireless

Check your DNS. The AP's use DNS to find the controller. If your trial controller still has a record for "zonedirector" then the AP's will be trying to get to a non-existent controller.

Cluster the controllers, and have all AP's part of the same wireless infrastructure. You can use HREAP across WAN links so the controllers do not need to be local to the APs.

I'd have to disagree. This is UTP copper, and the more you expose and untwist the pairs, the more crosstalk you introduce. Cat5e was not meant to be spliced. In addition they've installed them incorrectly by feeding both ends through the same side of the box - they're designed to have one end come in each side.

Wow I've never seen those...so basically a splice for Cat5e.... Probably pretty close to the worst idea I've even seen. Get rid of them.