In some cases, your access point may need to have its firmware "flashed". Flashing the firmware simply means you're re-installing the firmware onto the access point. This may be needed due to the access point running outdated firmware or you're having technical problems with the access point.
Follow the instructions below to re-flash. Before adding them back to your network, ensure follow the instructions at the end of this article.
- Windows users: Install a utility program called WinPcap. Get it here: http://www.winpcap.org/install/default.htm
- Make sure to enable "Run on Startup"
- Linux users: Skip to Part B
- Mac users: Use our Mac firmware flash instructions (beta)
Download and save the flash utility for your model and network:
Latest Development Release
Current Stable Release
Previous Stable Releases
The flash utility is a "console application", so open up a console window. In Vista or Windows 7, go to the Start menu and search for "command"; in Windows 8, press the Windows key+R and enter "cmd". Once you have the console window open, you will first need to go to the directory you downloaded the file to. In most cases you can simply type cd Downloads and press Enter to get to your Downloads directory. Once in the correct directory, type open-mesh-flash-ng and press Enter. You should see output similar to the following:
open-mesh-flash-ng [ethdevice] flashes embedded kernel + rootfs: open-mesh firmware rxxx
open-mesh-flash-ng [ethdevice] rootfs.bin kernel.lzmaflashes your rootfs and kernel
open-mesh-flash-ng [ethdevice] ubnt.binflashes your ubiquiti image
open-mesh-flash-ng [ethdevice] uboot.binflashes your uboot image
open-mesh-flash-ng -vprints version information
The 'ethdevice' has to be one of the devices that are part of the supported device list which follows.You can either specify its name or the interface number.
(Description: Atheros AtcL001 Gigabit Ethernet Controller)
(Description: MS Tunnel Interface Drive
Note: the number of your actual Ethernet Device from the list displayed (in this case, "3"). Hint: It will usually contain the word "Ethernet". Some users will have to run the cmd program as "administrator" to select their interface correctly.
Type "open-mesh-flash-ng n" where "n" is the Ethernet Device number. Hit "Enter"
|C:\Users\Mike Asus\Downloads>open-mesh-flash-ng 3
Connect your Open-Mesh access point to your PC's Ethernet port and power it on.If it was already powered on, power-cycle it by removing the power and plugging it back in.
Skip to Finalizing
Part B (For Linux users only)
Download and save the flash utility for Linux. Choose the version for your model and network:
Current Stable Release
Previous Stable Releases
Find the directory, the default is Downloads.
Type "chmod +x open-mesh-flash-ng"
Note the number of your actual Ethernet Device from the list displayed (in this case, "1"). Hint: It will usually contain the word "Ethernet".
Type "./open-mesh-flash-ng n" where "n" is the Ethernet Device number. Hit "Enter"
(You may need to run "sudo ./open-mesh-flash-ng n")
|~ $ sudo ./open-mesh-flash-ng 1
Connect your Open-Mesh access point to your PC's Ethernet port and power it on. If it was already powered on, power-cycle it by removing the power and plugging it back in.
If flashing the MR500 Or OM2P, you MUST use the LAN port NEXT TO THE POWER PLUG. None of the other ports will work to reflash. A crossover cable is NOT required to connect your unit to your computer via ethernet cable.
The output of the flash utility should look similar to below (note that the MR500 output will be much shorter). If after 10 seconds you don't see this, try power cycling your router and/or check the interface number to make sure you are using your computer's Ethernet port.
|[ac:86:74:02:23:f8]: type 'OM2P router' detected
[ac:86:74:02:23:f8]: OM2P router: tftp client asks for 'fwupgrade.cfg', ser
fwupgrade.cfg portion of: embedded image (1 blocks) ...
[ac:86:74:02:23:f8]: OM2P router: tftp client asks for 'kernel', serving ke
portion of: embedded image (1861 blocks) ...
[ac:86:74:02:23:f8]: OM2P router: tftp client asks for 'rootfs', serving ro
portion of: embedded image (4097 blocks) ...
[ac:86:74:02:23:f8]: OM2P router: image successfully transmitted - writing
to flash ...
[ac:86:74:02:23:f8]: OM2P router: flash complete. Device ready to unplug.
The reflash will take about 3-15 minutes to complete (depending upon the router model) so please be patient.
The flash program will not exit on it's own. You can either plug in another node to start the process again, or hit "Ctrl+C" to exit the console and flash utility.
You can display the version of the firmware embedded in the flash utility by typing "open-mesh-flash-ng -v".
- Before plugging the access point back into your network, ensure you've selected the proper firmware version in CloudTrax and disable automatic upgrades. Different firmware versions have different dependencies in CloudTrax, and a mismatch here will cause network issues. Both of these options can be found in Configure > Maintenance.
- After re-flashing a unit and connecting it back to your local network, it must also be paired with your CloudTrax network again. An alert will show up advising you to re-pair the unit once it comes back online.
Note: If you have changed the wireless channel on your network from the default 5, you will find that after reflashing wireless nodes may take up to 40 minutes to check-in. This is because the reflash returns the units back to the default settings. An alternative is to plug the unit in via Ethernet and wait for the device to update its channel before making it a wireless node again.