4 ms·

Ditto the other positive comments here. We went through a handful of different wireless manufacturers when trying to set up cheap, reliable mesh networks for a

Ditto the other positive comments here. We went through a handful of different wireless manufacturers when trying to set up cheap, reliable mesh networks for a few customers. We finally discovered Ubiquiti (this was a few years ago), and we've stuck with them ever since with almost zero problems. I think we've had a single unit fail in the last several years. I don't know anything about this new hardware, but if it's anything like their wireless stuff, it'll be pretty good. If anybody wants to try out the Ubiquiti hardware, a good reseller is Baltic Networks: http://www.balticnetworks.com/ http://www.balticnetworks.com/. We order almost all of our Ubiquiti stuff from them, they're good people.

jMyles 12y ago
What do you do for software / firmware? I've been dabbling in meshbox / CJDNS lately.
- thaumaturgy 12y ago
  We just use Ubiquiti's software/firmware now. It does what we need, and zero hand-off is nice. Cloudtrax was nice too, and we used robin/batman and open-mesh for a while before that. At the time, the most common recommended hardware for that stack was Engenius, and we had a terrible experience with their hardware. I don't think we still have a single functioning Engenius unit deployed anywhere. Ubiquiti's older hardware could be custom-flashed for, I think, open-mesh, and we did that initially, but later on it became too much of a hassle. I don't know if that's still doable or not. IIRC, there was some kind of FCC dust-up with some of the wireless equipment manufacturers a couple of years back over support for custom firmware, since people were changing the country code in the firmware to violate US FCC regulations on broadcast power. Regardless, once Ubiquiti announced the zero hand-off, that became a killer feature for us and we quit messing around with the open source options. I love open source and try to use it when possible, but unless you need a specific feature that's not otherwise available, you're better off just using the Ubiquiti stack. There is one thing about Ubiquiti that irritates us at the moment: they use this really manky Java software for the initial AP setup, and it really sucks. Once you're up and running, everything's gravy, but that software really hates to run sometimes.

jMyles 12y ago

What do you do for software / firmware? I've been dabbling in meshbox / CJDNS lately.

thaumaturgy 12y ago
We just use Ubiquiti's software/firmware now. It does what we need, and zero hand-off is nice. Cloudtrax was nice too, and we used robin/batman and open-mesh for a while before that. At the time, the most common recommended hardware for that stack was Engenius, and we had a terrible experience with their hardware. I don't think we still have a single functioning Engenius unit deployed anywhere. Ubiquiti's older hardware could be custom-flashed for, I think, open-mesh, and we did that initially, but later on it became too much of a hassle. I don't know if that's still doable or not. IIRC, there was some kind of FCC dust-up with some of the wireless equipment manufacturers a couple of years back over support for custom firmware, since people were changing the country code in the firmware to violate US FCC regulations on broadcast power. Regardless, once Ubiquiti announced the zero hand-off, that became a killer feature for us and we quit messing around with the open source options. I love open source and try to use it when possible, but unless you need a specific feature that's not otherwise available, you're better off just using the Ubiquiti stack. There is one thing about Ubiquiti that irritates us at the moment: they use this really manky Java software for the initial AP setup, and it really sucks. Once you're up and running, everything's gravy, but that software really hates to run sometimes.