Assuming you have bbhn on your node currently use the sysupgrade version of the firmware to update it. With a ubnt poe adapter there is a reset button on the poe adapter. I have found a toothpick works great to push it. To go back to Airos unplug the Ethernet cable going to your node, push the reset button and hold it. While continuing to hold the reset button plug the ethernet cable back in. Hold the reset button for about 20 seconds and release it. You should be able to tftp thefirmware to the node. Follow the instructions above for setting the ip address on your computer. Some windows computers have trouble with identifying the network. I have found this is much easier to do in linux.

Exactly!

I would recommend buying the Ubiquiti 24V PoE adapters. Most have a reset button on the bottom of the power adapter that mimicks the physical reset button on the Nanostation. Very handy! D.

Outch! That would be quite the climb. This is straight from the OpenWRT Wiki:

Restore Original AirOS firmware on Nanostation
To restore original firmware back you can't use mtd or sysupgrade but you have to use tftp method.
First put Nanostation in recovery mode via reset button on power on, and then flash original flash image via tftp.
Source: http://wiki.openwrt.org/toh/ubiquiti/start

Assuming you have a certain UBNT POE adapter, you could try a remote reset through the POE adapter:
http://community.ubnt.com/t5/airMAX-General-Discussion/Remote-hardware-reset-circuitry-of-NanoStation-M/td-p/58320
http://wiki.openwrt.org/toh/ubiquiti/airmaxm#remote_reset

Google search "UBNT Firmware Recovery" and click on the link titled "Firmware Recovery - Ubiquiti Wiki"

What is the process for loading the factory firmware back onto a ubiquiiti device?

When I try to upgrade the firmware through the mesh GUI it fails.

When you first flash the routers, they will need to be configured. You can do this via WiFi (by connecting to an SSID titled MeshNode) or via Ethernet (turn off wifi) and navigating with your browser to http://localnode:8080/.

After that, they switch into AdHoc mode (you don't need to know that). But what you do need to know is that after the initial configuration, the mesh can be accessed via Ethernet (turn off WiFi) by navigating to http://localnode:8080/

I hope this helps!

Conrad, would it be possible to use the ubiquity software at 3G and run the the mesh through a tunnel until the M3 units are supported?

Are you hard wired to the node that is 200ft away? Are you having issue brining up the http://localnode:8080 page?  

Make sure to turn off your laptop wifi (if your connected to a wifi network and the node it can confuse the computer some times) 

http://www.broadband-hamnet.org/just-starting-read-this.html may be a good starting place as well to help you understand the mesh basics.

Look in the software download for LinkSys. Look for the specific file for version 4 LinkSys routers. It is the second from the last on the list  (I think).

Thanks to both of you for the quick replies.

After some thought, I came to the conclusion that side loading 3.0.0 was the way to go. Worked fine so I am busy upgrading. The new Bullet M2 flash will come next week with the arrival of the 24v supply. Now if we get just one more thaw so I can get to the roof for an install.

I would ask that consideration be given to maintaining some ability to communicate with Linksys gear once development continues past the support deadline. Even limited connectivity would be better than none.

Thanks again.

Dave KM2O

Re Question 2:  This was actually discovered last night. it's an issue on our side after 3.0.0 a few files on the website did not get refreshed so the update does not show up. We are working on that.

In the mean time the easiest way to go from any previous version to 3.0.0 is to download the trx file for Linksys and the Sysupgrade package for Ubiquiti and upload them through the web user interface manually instead of using the drop down to select the version.

I admit that I have not kept up as closely as perhaps I should have over the past few months with the rapid development since version 1.0.0. I am now confronted with a series of dilemmas. What to do with the Linksys gear now acquired by many in our area, myself included. I see that Linksys devices will now lose support next year.

After some false starts, our area is now likely to have a central node up and running as a hub. I will be able to use new Ubiquiti equipment for this node and will flash the original equipment to 3.0.0 as it appears to be the only option. Before I start to re-flash a number of Linksys routers from 1.0.0, however, I need some guidance:

1) Should I even bother?

2) If I go ahead and upgrade from 1.0.0, what is the proper path to 3.0.0? I apparently can go to 1.1.2 on board the router. Will the 3.0.0 upgrade appear following that or is it just easier to factory reset and load directly?

3) If the answer to question 1 is no, what should I tell the folks who have been asked to scrounge and flash Linksys routers waiting for the day to use them together effectively?

Thanks

Dave KM2O

Actually interesting you bring this up.

After the 3.0.0 release went RTW I spent a week and a half feeling my way around the build root, investigating various items and overall improving my general knowledge so I can better prepare for the next version iteration. 

With 900MHz out the door were now into the deeper more in depth hardware models that require a deeper understanding of hardware (which the past year with Ubiquiti gear has helped us gain that knowledge)

The 365 model testing has shown to have frontend filtering that sharply rolls off rendering them unusable for Part 97 usage. Since he focus is Part 97 (or world equivalent) not much additional focus was put towards the 365 units.

The M3 is an interesting unit as Paul explains .  It is a 5GHz node with a downconverter inside. This at first is a good thing, it means minimal changes to the rest of the system.  The interesting part comes with the fact that the drivers we use do not intended to go in to a middle dead band between two of the part 15 bands.  This is similar to the channel 0 issue for 2.4 GHz discussed elsewhere.  The advantage to the M3 is it's expected to operate in that band, I expect we will find additional calibration data that we can work on pulling in.

It has a fair bit of work before it will even be ready for testing but as Paul says in time we will likely pull in the M3 in time. It certainly is on the desire plan as it's a band many may find useful (though I'm not sure I will get to use it as San Diego  may be in an area for DoD 3.4GHz radar more research is needed on that as well) 

We worked the easy gear, now it's on to the advanced topics as the dev team working on Ubiquiti looks to continue to raise the bar on what we can do with these powerful yet affordable devices.

I wouldn't hold your breath on it being "soon" however as the one thing I've learned over the past year is nothing goes as planned. We likely have a large number of hours ahead of us working on this and other priorities that it will take time to produce.  As much as has been learned we still have more.

Hello if you are near eastern Tennessee to the north or the south and even the west drop in and please give us your location we are on a 20 unit setup in process, contact us and 73's

KD4YSH

Hello Newbee here ok I have flashed 3 out of my 12 wrt54g routers and have them plugged in and from any of my computers it does not see them. Do I need to load any type of software on my laptop that is 200 feet away to connect or see the nodes and communicate and see the traffic? Please any help will be much appreciated.

73's

You are correct. I have looked into this for a considerable time. To summarize, UBNT 3.4GHz radios are merely UBNT 5GHz devices with a 2GHz downconverter. The 3.4GHz US hamband (before downconverting) falls between the 5GHz "Lower Band" (5150-5320MHz) and the 5GHz "Middle Band" (5500-5850MHz). The PA on the M3 devices are rated from 3.5GHz to 3.7GHz Furthermore, the output power drops off considerably outside the PA's range. So much so that the devices do not even see eachother on 5320MHz even when they are touching with the antennas pointed directly at each other. Simply put, it is not easy, but I am sure we will get there eventually.