I have yet to see anything on this board about the FCC's current proposal to start requiring manufacturers to lockdown the firmware on open-source wifi routers such as we use. They are talking about just the frequency range and power but the way the FCC words things and paints with such a broad brush this could have dire implications. It sounds like it could make it difficult or even impossible to install 3rd party firmware. This is still only currently a proposal and the FCC is taking public input on the subject until October 9. Any updates or fills on this subject would be appreciated. Here's a link to one article:

http://arstechnica.com/information-technology/2015/09/fcc-accused-of-locking-down-wi-fi-routers-but-the-truth-is-a-bit-murkier/

I have the same problem. Ubiq 5.6.2 firmware, replaced with openwrt as per the instructions.

There is a warning on this page ; http://wiki.openwrt.org/toh/ubiquiti/airmaxm

*Special Firmware Note: AirOS XM.v5.5.X images used U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07). The OpenWRT image can be successfully flashed onto these versions of firmware. However, in July 2015 Ubiquiti released a new version of firmware XM.v5.6.X. With this firmware a new U-Boot version was released, U-Boot 1.1.4.2-s956 (Jun 10 2015 - 10:54:50). The newer U-Boot version changes the memory size and starting address for rootfs, cfg, and EEPROM. LOADING AN OPENWRT IMAGE ON A U-Boot 1.1.4.2-s956 WILL CAUSE THE DEVICE TO BE BRICKED!!!

So this is a bit of a problem, and there will continue to be bricked devices, money down the flusher, and disheartened newbies until someone either rewrites the HOWTO or at least puts a warning on it.

Can someone attend to this right away please. In the meanwhile, I will attempt to unbrick with its serial port.

Thanks,

Steve

Thanks for the heads up. I will keep that in my list of tools.

I attempted to reload the original Ubiquiti firmware and in the process bricked the the device. I can put the device into recovery mode, upload a copy of the OEM firmware, receive the file success message and then the device reboots. However once it reboots there is no ping response for 192.168.1.20 nor does a sweep tool reveal an ip address other than the laptop 192.168.1.24 address. Keep finding errata in various locations but thus far no joy. I contacted Ubiquiti and they walked me through a few steps, then responded the device was toast and suggested buying a replacement. At least I solved my search for a replacement N connector for another Ubiquiti unit with type N connector that is broke. :-(

Again thanks es 73

Chuck

During the flashing process, each time the Linksys (or Ubiquity) device goes through a reboot, briefly unplug your PC's LAN cable and plug it back in. This forces Windows to renegotiate an IP address from the device's built-in DHCP server, allowing "localnode:8080" to always work after every step.

And yes, ALWAYS have any WiFi adapter disabled while flashing, otherwise you WILL have to chase down any IP address change by hand, as you described.

I have a node that I set up a couple of years ago and never put it on the air, and looking to do so.  my question is my current version is 1.0.0, should I update to 3.0 or 3.1?

Sorry; "pre-made" not "remade".   Darn spelling corrector.

Bob W8ERD

We need to make several long ethernet runs up tall towers for our mesh nodes. I know the specifiied maximum length is 100 meters or 328 feet.  Several companies sell remade cables 300 feet long. Outdoor  shielded cables.    Does anyone have experience using such long cables?  Are there any problems?

Using an ethernet repeater would be a significant hassle.

Thanks!

Bob W8ERD

I vouch for these guys. Have bought several items. They were at Dayton.

They are now selling used Bullet M2 for $50.

www.swginc.net

Bob W8ERD

Many people now discount the older WRT54's in favor of the newer and better Ubiquiti gear.

As Alan said, WRTs are still QUITE useful for local use, as an access into the mesh, for adding services to the mesh (web, chat, mail, file server, etc). They were made for close-in usage.

But as Darryl points to Clints page, UBNT gear is made to go the long haul. They are designed for the long distances and therefore have better radios and the software is much better at the timing and other issues that come with long shots.

Here locally, we are FINALLY building out a big network, and for the really long hops, we dont even flash to BBHN firmware, but use the stock AirOS as transparent links, and then hang BBHN-flashed gear off the ends for connectivity. The BBHN gear sees the transparent links basically as a CAT5 cable, so you dont lose overhead in the hops.

So it all depends on what you want to do. If it is just tabletop exercise, then WRTs will work just fine and are seriously inexpensive and plentiful. If you want to connect buildings across town, go with UBNT.

73 & Happy Meshing!

Jim

I was wondering if anyone has or knows if we can remote control radios over a mesh node using VOIP.

I have an situation that this question has come up. This setup can be used via an internet connection using voip, so we were wondering if the same could be done on a mesh node.

I am new at this mesh node stuff and am trying to learn what I can and can't do with it.