Sudo Room - User contributions [en]

Mesh/WalkThrough

2018-06-26T23:39:56Z

Robb: /* Configure */

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with Sudo Mesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by Sudo Mesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to ensure your router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || '''[https://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest]''' [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
'''[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest]'''
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0]
|-
|}

Builds for other routers can be found on our [http://builds.sudomesh.org/builds/sudowrt/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use Sudo Mesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Configure =
A freshly flashed node automatically sets its IP address to 172.30.0.xx. You will need to configure your laptop to use the following network settings to communicate with the node:

* IP address: 172.30.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.30.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

== Autoconf (v.0.3.0) ==
[[File:Nodeports.jpg|100px|frame|right|Plug into port 3 to access the private network from your laptop. Port 2 connects to the public 'peoplesopen.net' network]] Connect your newly-flashed MyNet N600 to your existing Internet router via ethernet from your existing router's LAN port to your new node's Internet port. Wait a few minutes for your new node to connect to the Internet and obtain its private IP address, then try connecting to your unconfigured router by opening a browser and navigating to http://172.30.0.1

If the flash was successful you should be brought to the following screen:

[[File:Peoplesopen-dash.jpg|frame|center|upright=2]]

Here you can set the amount of downstream and upstream bandwidth you're willing to share (default is set to 4096kb, or roughly 4 megabits/second):
[[File:homeScreen.jpg|frame|center|upright=2]]

[[File:WifiSettings.jpg|frame|left|upright=2|Set your private SSID and password via the 'WIFi Settings' tab. NOTE: When you first set your private SSID name and hit 'Save', you will have to reconnect to the newly-named SSID using the original default password ('meshtheworld') and then reconnect again with the new password after setting it in the dashboard]] [[File:Connections.jpg|frame|right|upright=2|See all devices connected to your node via the 'Connections' tab]]

 If you installed autoconfiguring [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers, you will not need to use makenode ([[##Makenode|instructions further down]]) after flashing the sudowrt-firmware to your router to configure it to work on People's Open Network.

== Makenode (v.0.2.3 and earlier) ==
After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

=== Install Dependencies ===
You first will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

==== Linux ====

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

===== OS Compatibility checklist =====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

==== Mac ====

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

==== Windows 10 (Experimental)====

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

=== Install and run makenode ===
From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the flashing and configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available. It should also be populated on the [https://peoplesopen.herokuapp.com monitor]!

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, upload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/WalkThrough

2018-06-26T08:17:58Z

Robb: /* Reconfigure your computer's network settings */ change ip of router

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with the SudoMesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by SudoMesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to find out the router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || [https://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest] [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0]
|-
|}

Builds for other routers can be found on our [http://builds.sudomesh.org/builds/sudowrt/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use a SudoMesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= makenode/Configure =
After flashing sudowrt-firmware to your router you will need to configure it to work on a People's Open Network
* unless you installed [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers which auto configures & you are done. See [https://github.com/sudomesh/sudowrt-firmware/pull/132 proposal for sudowrt 0.3.0] for more info.

== Reconfigure your computer's network settings ==
A freshly flashed node automatically sets its IP address to 172.30.0.1. You will need to configure your laptop to use the following network settings to communicate with the node.

* IP address: 172.30.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.30.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

To test that the flashing was successful, feel free to try connecting to your unconfigured router by opening a browser and navigating to http://172.30.0.1
You can SSH into the node as root using the password 'meshtheplanet'. If the flash was successfull you should be brought to the following screen:

[[File:Peoplesopen-dash.png|thumb|center|upright=2]]

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

== Preparing your laptop for makenode ==

You will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

=== Linux ===

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

==== OS Compatibility checklist ====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

=== Mac ===

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

=== Windows 10 (Experimental)===

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

== Install and run makenode ==

From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the makenode configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available.

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, updload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/WalkThrough

2018-06-26T08:16:29Z

Robb: /* Reconfigure your computer's network settings */

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with the SudoMesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by SudoMesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to find out the router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || [https://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest] [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0]
|-
|}

Builds for other routers can be found on our [http://builds.sudomesh.org/builds/sudowrt/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use a SudoMesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= makenode/Configure =
After flashing sudowrt-firmware to your router you will need to configure it to work on a People's Open Network
* unless you installed [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers which auto configures & you are done. See [https://github.com/sudomesh/sudowrt-firmware/pull/132 proposal for sudowrt 0.3.0] for more info.

== Reconfigure your computer's network settings ==
A freshly flashed node automatically sets its IP address to 172.22.0.1. You will need to configure your laptop to use the following network settings to communicate with the node.

* IP address: 172.30.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.30.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

To test that the flashing was successful, feel free to try connecting to your unconfigured router by opening a browser and navigating to http://172.30.0.1
You can SSH into the node as root using the password 'meshtheplanet'. If the flash was successfull you should be brought to the following screen:

[[File:Peoplesopen-dash.png|thumb|center|upright=2]]

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

== Preparing your laptop for makenode ==

You will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

=== Linux ===

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

==== OS Compatibility checklist ====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

=== Mac ===

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

=== Windows 10 (Experimental)===

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

== Install and run makenode ==

From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the makenode configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available.

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, updload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/WalkThrough

2018-06-26T08:16:09Z

Robb: /* Reconfigure your computer's network settings */

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with the SudoMesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by SudoMesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to find out the router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || [https://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest] [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
[https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2][https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0]
|-
|}

Builds for other routers can be found on our [http://builds.sudomesh.org/builds/sudowrt/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use a SudoMesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= makenode/Configure =
After flashing sudowrt-firmware to your router you will need to configure it to work on a People's Open Network
* unless you installed [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers which auto configures & you are done. See [https://github.com/sudomesh/sudowrt-firmware/pull/132 proposal for sudowrt 0.3.0] for more info.

== Reconfigure your computer's network settings ==
A freshly flashed node automatically sets its IP address to 172.22.0.1. You will need to configure your laptop to use the following network settings to communicate with the node.

* IP address: 172.30.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.30.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

To test that the flashing was successful, feel free to try connecting to your unconfigured router by opening a browser and navigating to http://172.22.0.1
You can SSH into the node as root using the password 'meshtheplanet'. If the flash was successfull you should be brought to the following screen:

[[File:Peoplesopen-dash.png|thumb|center|upright=2]]

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

== Preparing your laptop for makenode ==

You will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

=== Linux ===

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

==== OS Compatibility checklist ====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

=== Mac ===

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

=== Windows 10 (Experimental)===

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

== Install and run makenode ==

From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the makenode configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available.

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, updload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/WalkThrough

2018-06-24T02:46:43Z

Robb: /* makenode/Configure */

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with the SudoMesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by SudoMesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to find out the router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] || [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.3.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
|-
|}

Builds for other routers can be found on our [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use a SudoMesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= makenode/Configure =
After flashing sudowrt-firmware to your router you will need to configure it to work on a People's Open Network
* unless you installed [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] for myNet N600 routers which auto configures & you are done. See [https://github.com/sudomesh/sudowrt-firmware/pull/132 proposal for sudowrt 0.3.0] for more info.

== Reconfigure your computer's network settings ==
A freshly flashed node automatically sets its IP address to 172.22.0.1. You will need to configure your laptop to use the following network settings to communicate with the node.

* IP address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.22.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

To test that the flashing was successful, feel free to try connecting to your unconfigured router by opening a browser and navigating to http://172.22.0.1
You can SSH into the node as root using the password 'meshtheplanet'. If the flash was successfull you should be brought to the following screen:

[[File:Peoplesopen-dash.png|thumb|center|upright=2]]

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

== Preparing your laptop for makenode ==

You will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

=== Linux ===

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

==== OS Compatibility checklist ====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

=== Mac ===

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

=== Windows 10 (Experimental)===

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

== Install and run makenode ==

From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the makenode configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available.

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, updload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/WalkThrough

2018-06-24T02:45:31Z

Robb: /* Notice for (MyNet N600 only) Release 0.3.0 */

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with the SudoMesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by SudoMesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to find out the router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] || [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.3.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
|-
|}

Builds for other routers can be found on our [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use a SudoMesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= makenode/Configure =
After flashing sudowrt-firmware to your router you will need to configure it to work on a People's Open Network
* unless you installed [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] which auto configures & you are done. See [https://github.com/sudomesh/sudowrt-firmware/pull/132 proposal for sudowrt 0.3.0] for more info.

== Reconfigure your computer's network settings ==
A freshly flashed node automatically sets its IP address to 172.22.0.1. You will need to configure your laptop to use the following network settings to communicate with the node.

* IP address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.22.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

To test that the flashing was successful, feel free to try connecting to your unconfigured router by opening a browser and navigating to http://172.22.0.1
You can SSH into the node as root using the password 'meshtheplanet'. If the flash was successfull you should be brought to the following screen:

[[File:Peoplesopen-dash.png|thumb|center|upright=2]]

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

== Preparing your laptop for makenode ==

You will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

=== Linux ===

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

==== OS Compatibility checklist ====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

=== Mac ===

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

=== Windows 10 (Experimental)===

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

== Install and run makenode ==

From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the makenode configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available.

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, updload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/WalkThrough

2018-06-24T02:45:01Z

Robb: /* makenode/Configure */

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with the SudoMesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by SudoMesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to find out the router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] || [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.3.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
|-
|}

Builds for other routers can be found on our [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use a SudoMesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Notice for (MyNet N600 only) Release 0.3.0 =
[https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0/ Release 0.3.0 (dispossessed)] allows a newly flashed node to retrieve an IP over its WAN connection from a [https://github.com/sudomesh/meshnode-database sudomesh/meshnode-database]. Once the node gets an IP, it configures itself to mesh with other People's Open Nodes and tunnel to a [https://github.com/sudomesh/exitnode sudomesh/exitnode]. makenode/Configure is no longer required & you are done installing the firmware. [https://github.com/sudomesh/sudowrt-firmware/pull/132 More information.]

= makenode/Configure =
After flashing sudowrt-firmware to your router you will need to configure it to work on a People's Open Network
* unless you installed [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] which auto configures & you are done. See [https://github.com/sudomesh/sudowrt-firmware/pull/132 proposal for sudowrt 0.3.0] for more info.

== Reconfigure your computer's network settings ==
A freshly flashed node automatically sets its IP address to 172.22.0.1. You will need to configure your laptop to use the following network settings to communicate with the node.

* IP address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.22.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

To test that the flashing was successful, feel free to try connecting to your unconfigured router by opening a browser and navigating to http://172.22.0.1
You can SSH into the node as root using the password 'meshtheplanet'. If the flash was successfull you should be brought to the following screen:

[[File:Peoplesopen-dash.png|thumb|center|upright=2]]

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

== Preparing your laptop for makenode ==

You will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

=== Linux ===

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

==== OS Compatibility checklist ====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

=== Mac ===

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

=== Windows 10 (Experimental)===

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

== Install and run makenode ==

From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the makenode configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available.

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, updload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/WalkThrough

2018-06-24T02:43:37Z

Robb: /* makenode/Configure */ add info for release 0.3.0

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with the SudoMesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by SudoMesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to find out the router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] || [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.3.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
|-
|}

Builds for other routers can be found on our [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use a SudoMesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Notice for (MyNet N600 only) Release 0.3.0 =
[https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0/ Release 0.3.0 (dispossessed)] allows a newly flashed node to retrieve an IP over its WAN connection from a [https://github.com/sudomesh/meshnode-database sudomesh/meshnode-database]. Once the node gets an IP, it configures itself to mesh with other People's Open Nodes and tunnel to a [https://github.com/sudomesh/exitnode sudomesh/exitnode]. makenode/Configure is no longer required & you are done installing the firmware. [https://github.com/sudomesh/sudowrt-firmware/pull/132 More information.]

= makenode/Configure =
After flashing sudowrt-firmware to your router you will need to configure it to work on a People's Open Network unless you installed unless you installed [https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0 release 0.3.0] which auto configures & you are done. See [https://github.com/sudomesh/sudowrt-firmware/pull/132 proposal for sudowrt 0.3.0] for more info.

== Reconfigure your computer's network settings ==
A freshly flashed node automatically sets its IP address to 172.22.0.1. You will need to configure your laptop to use the following network settings to communicate with the node.

* IP address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.22.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

To test that the flashing was successful, feel free to try connecting to your unconfigured router by opening a browser and navigating to http://172.22.0.1
You can SSH into the node as root using the password 'meshtheplanet'. If the flash was successfull you should be brought to the following screen:

[[File:Peoplesopen-dash.png|thumb|center|upright=2]]

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

== Preparing your laptop for makenode ==

You will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

=== Linux ===

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

==== OS Compatibility checklist ====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

=== Mac ===

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

=== Windows 10 (Experimental)===

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

== Install and run makenode ==

From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the makenode configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available.

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, updload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/WalkThrough

2018-06-24T02:33:46Z

Robb: /* Notice for latest Release 0.3.0 */

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with the SudoMesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by SudoMesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to find out the router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] || [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.3.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
|-
|}

Builds for other routers can be found on our [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use a SudoMesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Notice for (MyNet N600 only) Release 0.3.0 =
[https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0/ Release 0.3.0 (dispossessed)] allows a newly flashed node to retrieve an IP over its WAN connection from a [https://github.com/sudomesh/meshnode-database sudomesh/meshnode-database]. Once the node gets an IP, it configures itself to mesh with other People's Open Nodes and tunnel to a [https://github.com/sudomesh/exitnode sudomesh/exitnode]. makenode/Configure is no longer required & you are done installing the firmware. [https://github.com/sudomesh/sudowrt-firmware/pull/132 More information.]

= makenode/Configure =
After flashing sudowrt-firmware to your router you will need to configure it work on a People's Open Network.

== Reconfigure your computer's network settings ==
A freshly flashed node automatically sets its IP address to 172.22.0.1. You will need to configure your laptop to use the following network settings to communicate with the node.

* IP address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.22.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

To test that the flashing was successful, feel free to try connecting to your unconfigured router by opening a browser and navigating to http://172.22.0.1
You can SSH into the node as root using the password 'meshtheplanet'. If the flash was successfull you should be brought to the following screen:

[[File:Peoplesopen-dash.png|thumb|center|upright=2]]

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

== Preparing your laptop for makenode ==

You will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

=== Linux ===

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

==== OS Compatibility checklist ====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

=== Mac ===

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

=== Windows 10 (Experimental)===

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

== Install and run makenode ==

From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the makenode configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available.

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, updload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/WalkThrough

2018-06-24T02:30:43Z

Robb: /* Notice for latest Release 0.3.0 */ add (myNet only)

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with the SudoMesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by SudoMesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to find out the router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] || [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.3.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
|-
|}

Builds for other routers can be found on our [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use a SudoMesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Notice for latest Release 0.3.0 =
[https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0/ Release 0.3.0 (dispossessed)] (MyNet N600 only) allows a newly flashed node to retrieve an IP over its WAN connection from a [https://github.com/sudomesh/meshnode-database sudomesh/meshnode-database]. Once the node gets an IP, it configures itself to mesh with other People's Open Nodes and tunnel to a [https://github.com/sudomesh/exitnode sudomesh/exitnode]. makenode/Configure is no longer required & you are done installing the firmware. [https://github.com/sudomesh/sudowrt-firmware/pull/132 More information.]

= makenode/Configure =
After flashing sudowrt-firmware to your router you will need to configure it work on a People's Open Network.

== Reconfigure your computer's network settings ==
A freshly flashed node automatically sets its IP address to 172.22.0.1. You will need to configure your laptop to use the following network settings to communicate with the node.

* IP address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.22.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

To test that the flashing was successful, feel free to try connecting to your unconfigured router by opening a browser and navigating to http://172.22.0.1
You can SSH into the node as root using the password 'meshtheplanet'. If the flash was successfull you should be brought to the following screen:

[[File:Peoplesopen-dash.png|thumb|center|upright=2]]

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

== Preparing your laptop for makenode ==

You will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

=== Linux ===

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

==== OS Compatibility checklist ====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

=== Mac ===

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

=== Windows 10 (Experimental)===

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

== Install and run makenode ==

From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the makenode configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available.

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, updload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/WalkThrough

2018-06-24T02:22:59Z

Robb: /* Download/Build */ added link to dispossessed firmware

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with the SudoMesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by SudoMesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to find out the router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] || [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3] [http://builds.sudomesh.org/builds/sudowrt/dispossessed/0.3.0/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.3.0]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
|-
|}

Builds for other routers can be found on our [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use a SudoMesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Notice for latest Release 0.3.0 =
[https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0/ Release 0.3.0 (dispossessed)] allows a newly flashed node to retrieve an IP over its WAN connection from a [https://github.com/sudomesh/meshnode-database sudomesh/meshnode-database]. Once the node gets an IP, it configures itself to mesh with other People's Open Nodes and tunnel to a [https://github.com/sudomesh/exitnode sudomesh/exitnode]. makenode/Configure is no longer required & you are done installing the firmware. [https://github.com/sudomesh/sudowrt-firmware/pull/132 More information.]

= makenode/Configure =
After flashing sudowrt-firmware to your router you will need to configure it work on a People's Open Network.

== Reconfigure your computer's network settings ==
A freshly flashed node automatically sets its IP address to 172.22.0.1. You will need to configure your laptop to use the following network settings to communicate with the node.

* IP address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.22.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

To test that the flashing was successful, feel free to try connecting to your unconfigured router by opening a browser and navigating to http://172.22.0.1
You can SSH into the node as root using the password 'meshtheplanet'. If the flash was successfull you should be brought to the following screen:

[[File:Peoplesopen-dash.png|thumb|center|upright=2]]

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

== Preparing your laptop for makenode ==

You will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

=== Linux ===

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

==== OS Compatibility checklist ====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

=== Mac ===

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

=== Windows 10 (Experimental)===

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

== Install and run makenode ==

From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the makenode configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available.

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, updload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/WalkThrough

2018-06-24T02:08:18Z

Robb: add section about autoconf for dispossessed

Congratulations on choosing to become part of a People's Open Network! This is a walkthrough for flashing a node (a home router) with the SudoMesh's sudowrt-firmware (a custom build of OpenWRT) and then configuring it with makenode (a custom javascript tool developed by SudoMesh). At the end of the walkthrough, you'll be able to plug in your router and join the mesh. The walkthrough assumes you're using a linux-ish OS (mac OSX should work also) and that you have [https://help.ubuntu.com/community/UsingTheTerminal basic knowledge of the terminal]. The general idea of building your own mesh node consists of three steps, [[#Download/Build|downloading or compiling]] custom firmware, [[#Flash/Upload|flashing that firmware]] to the node (i.e. copying firmware to [https://en.wikipedia.org/wiki/Flash_memory flash memory]), and [[#makenode/Configure|configuring the node]] to function as part of a mesh (with a software tool such as makenode).

Before you flash your router, it is recommended that you read the [[Home and extender nodes#Home_nodes|home node info]] to find out the router works as a mesh node.

= Download/Build =

Now that you have a node, you will probably want to learn how to flash it with the latest sudowrt-firmware. The first step is to download the firmware image file for your supported router.

At the moment, we are supporting the following routers:

{| class="wikitable"
! Name !! OpenWRT Doc !! Firmware Image
|-
| TP-Link WDR3500 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3500 OpenWRT Docs] || [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3500-v1-squashfs-factory.bin 0.2.3]
|-
| TP-Link WDR3600 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr3600 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr3600-v1-squashfs-factory.bin 0.2.3]

|-
| TP-Link WDR4300 || [https://wiki.openwrt.org/toh/tp-link/tl-wdr4300 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-tl-wdr4300-v1-squashfs-factory.bin 0.2.3]
|-
| Western Digital MyNet N600 || [https://wiki.openwrt.org/toh/wd/n600 OpenWRT Docs] || [https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n600-squashfs-factory.bin 0.2.3]
|-
| Western Digital MyNet N750 || [https://wiki.openwrt.org/toh/wd/n750 OpenWRT Docs] ||
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin latest] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.0] [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.2/ar71xx/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.2]
[https://zenodo.org/record/1205601/files/openwrt-ar71xx-generic-mynet-n750-squashfs-factory.bin 0.2.3]
|-
|}

Builds for other routers can be found on our [https://builds.sudomesh.org/builds/sudowrt/fledgling/0.2.0/ar71xx/ builds server] or on [https://doi.org/10.5281/zenodo.1205601 zenodo], though there is no guarantee the firmware will work with any given router. For release notes, please go to our [https://github.com/sudomesh/sudowrt-firmware/releases github release pages].

Alternatively, you can build your own copy of the firmware images by following the guide in the [https://github.com/sudomesh/sudowrt-firmware sudowrt-firmware source].

If you do not want to use a SudoMesh's OpenWRT image, you can also install [https://downloads.openwrt.org/ a standard OpenWRT] release and configure it from scratch.

= Flash/Upload =

Once you have a copy of the sudowrt-firmware intended for your router, you can proceed with flashing it to your router. There are different techniques for flashing each of the routers. Use the links above to the OpenWRT wiki and follow the instructions there to flash the router with the firmware you've downloaded.

For convenience, if you have a Western Digital MyNet N600 or N750, follow these instructions:

== Reset your new N750/N600 router ==
* Plug one end of the Ethernet cable into your laptop.
* Plug the other end of the Ethernet cable into one of the normal ports (LAN) on the router (not the Internet/WAN port).
* With the router plugged in and power turned off, push a pin into the reset hole and hold it.
* With the pin held down, turn on the router power button.
* Watch the front blue light - they will flash on and off a few times.
* Once the front blue is flashing, you can let go of the pin.

== Configure your computer's network settings ==
On your laptop edit your network settings to reflect the following:

* Network Manager Method: Manual
* IP Address: 192.168.1.10 (some devices will only accept from this IP)
* Subnet Mask: 255.255.255.0
* Gateway: 0.0.0.0 (Or leave blank)

You can also use the commands:
sudo ip link set <eth_interface> down
sudo ip addr add 192.168.1.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [[Mesh/Network%20Configuration%20for%20Linux | Linux]], [[Mesh/Network%20Configuration%20for%20MacOS%20X | Mac]]

== Upload sudowrt-firmware ==
In your web browser:

* Go to [http://192.168.1.1 http://192.168.1.1], if the reset was successful, you should see the following page:
[[File:Screenshot from 2017-04-04 18-27-09.png|thumb|center|upright=2]]
* Click 'Browse' and select the firmware file you downloaded
* Click Upload and you will be taken to an exciting countdown timer:
[[File:Screenshot from 2017-04-02 17-20-51.png|thumb|center|upright=2]]

Note: Sometimes the firmware upload will not complete. After you click on 'Upload' You should get a page with a countdown of 120+ seconds. If this does not occur, reboot the router with the pin reset button depressed (as noted above), and try again.

= Notice for latest Release 0.3.0 =
[https://github.com/sudomesh/sudowrt-firmware/releases/tag/0.3.0/ Release 0.3.0 (dispossessed)] allows a newly flashed node to retrieve an IP over its WAN connection from a [https://github.com/sudomesh/meshnode-database sudomesh/meshnode-database]. Once the node gets an IP, it configures itself to mesh with other People's Open Nodes and tunnel to a [https://github.com/sudomesh/exitnode sudomesh/exitnode]. makenode/Configure is no longer required & you are done installing the firmware. [https://github.com/sudomesh/sudowrt-firmware/pull/132 More information.]

= makenode/Configure =
After flashing sudowrt-firmware to your router you will need to configure it work on a People's Open Network.

== Reconfigure your computer's network settings ==
A freshly flashed node automatically sets its IP address to 172.22.0.1. You will need to configure your laptop to use the following network settings to communicate with the node.

* IP address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

Or use the commands
sudo ip link set <eth_interface> down
sudo ip addr add 172.22.0.10/24 dev <eth_interface>
sudo ip link set <eth_interface> up

where <eth_interface> is the name of your ethernet interface found using `ip addr` (common names include eth0, enp3s0, ...)

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

To test that the flashing was successful, feel free to try connecting to your unconfigured router by opening a browser and navigating to http://172.22.0.1
You can SSH into the node as root using the password 'meshtheplanet'. If the flash was successfull you should be brought to the following screen:

[[File:Peoplesopen-dash.png|thumb|center|upright=2]]

After you have successfully flashed your router with OpenWRT, you will need to use [https://github.com/sudomesh/makenode makenode] to complete the setup. makenode registers your node on the peoplesopen network, resulting in the assignment of a 64 IPv4 address subnet to your node, in addition to applying basic configuration.

== Preparing your laptop for makenode ==

You will need to install the dependencies for [https://github.com/sudomesh/makenode makenode].

=== Linux ===

If you are working with a fresh installation of one of the operating systems listed in the compatibility checklist, you will need to install a few pieces of software.
To install them, open your terminal and enter the following commands.

sudo apt update
sudo apt install curl git dropbear
curl -o- https://raw.githubusercontent.com/creationix/nvm/v0.33.2/install.sh | bash
export NVM_DIR="$HOME/.nvm" # or you can close and reopen your terminal before using nvm
nvm install 7.10

==== OS Compatibility checklist ====

{| class="wikitable"
! OS !! Compatible !! Link to ISO !! Notes
|-
| Ubuntu 16.04 LTS || yes || http://releases.ubuntu.com/16.04/ ||
|-
| Ubuntu 14.04 LTS || please verify || http://releases.ubuntu.com/14.04/ ||
|-
| Debian 9.3 Stretch || yes || https://www.debian.org/distrib/ ||
|-
| Debian 8.1 Jessie || yes || https://www.debian.org/releases/jessie/debian-installer/ ||
|-
| Arch Linux || yes || https://www.archlinux.org/download/ || you may have to build dropbear from [https://github.com/mkj/dropbear source]
|-
|}

=== Mac ===

Install the [http://brew.sh/ Homebrew] package manager, then install the required binaries.

brew install nodejs
brew install git
brew install npm
brew install dropbear
brew install gnu-tar
brew install fakeroot
brew install iproute2mac

=== Windows 10 (Experimental)===

'''Note: Windows is not currently recommened for setting up a node due to Dropbear not supporting Windows. What follows is instructions for Windows Subsytem for Linux.'''

Due to Dropbear requirements your best bet is to use [[Windows Subsystem for Linux]] (WSL) and follow the instructions for Linux with additional instructions to get WSL set up. Follow the instructions for [https://docs.microsoft.com/en-us/windows/wsl/install-win10 installing] WSL on your Windows 10 PC. For now Ubuntu has been tested and appears to work. SUSE and other WSL flavors have not been tested.

Once WSL is installed. Install dependencies (assuming Ubuntu).

sudo apt update
sudo apt install python
sudo apt install make
sudo apt install build-essential

WSL doesn't fully support SYSV IPC so fakeroot needs to be rebuilt using tcp.

sudo update-alternatives --set fakeroot /usr/bin/fakeroot-tcp

Follow Linux [[Mesh/WalkThrough#Linux | instructions]] for installing Dropbear and dependencies.

== Install and run makenode ==

From your terminal, run the following:

git clone https://github.com/sudomesh/makenode -b 0.0.1
cd makenode
npm install
cp settings.js.example settings.js

The default settings in <tt>settings.js</tt> should suffice in most cases, but if you need to make changes, do them in <tt>settings.js</tt>.

Make sure the Ethernet cable is connected to the 4th port on the router, and that your computer has a working internet connection (e.g. over WiFi). From a terminal, you should be able to ping the home node at 172.22.0.1 and arbitrary websites like github.com.

Once your network configuration is refreshed, use the following command to run the script and configure your node:

./makenode.js

Now the configuration wizard will ask you a number of questions:

* "enter valid hostname" - name of the box, will only be seen when you SSH into the router - For info on what constitutes a valid hostname, see: [http://stackoverflow.com/questions/3523028/valid-characters-of-a-hostname valid characters of a hostname]
* "max share upstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network, measured in kbps (kilobits per second). So if you'd like to share 10mbps (megabits per second) enter "10000" or if you want to share 256kbps (kilobits per second) enter "256". You may want to run a [http://www.dslreports.com/speedtest speed test] to find out how much bandwidth you have and determine how much you want to share.
* "max share downstream bandwidth" - how much of your home network upstream bandwidth you wish to share with the mesh network - eg. "512" would share 512 kbps
* "admin user password" - used to log into the admin dashboard where you can modify some settings at http://172.22.0.1 (if on wired connection) or http://172.30.0.1 (if on private wifi network)
* "root user password" - used to SSH into the router so you modify files and manually configure your router. Make sure that your root password is strong! If you don't enter a root password, a strong one will be generated and will be logged to screen. It's generally preferable to not use the root password at all and instead add an ssh key to the device, ssh keys are stored in /etc/dropbear/authorized_keys.
* "wifi transmit power" - set this to 23 dBm (which is equivalent to 200 milliwatts)
* "private wifi SSID" - name of the private wireless network that can be used to administer this router. It will be publicly visible so pick something amusing or descriptive.
* "private wifi password" - password for the private wireless network named in the previous step. It's the one you'll want to give to friends, so come up with something amusing or memorable. Note: it must be at least 8 characters long.
* "operator name" - name that the network admins can associate with the node - so use a unique name like your first name or location name
* "Operator email" - email that network admis can contact you at
* "Expected node address (optional)" - address location of node

= Testing =

After you're finished with the makenode configuration, your home node should be available for connections via your private WiFi SSID. Additionally the public SSID 'peoplesopen.net' will be available.

A third interface named 'pplsopen.net-node2node' will be detectable as well. This is the interface used for the nodes to mesh with each other.

At this point you're setup. For more information on using your node, such as accessing the web-based management interface, see [[Home and extender nodes#Home_nodes|Home node info]]

For more technical details on the internals of the home node, see the [[Mesh/Technical_Overview]]

For more in depth testing procedures, see our [https://github.com/sudomesh/babeld-lab/blob/master/operator_manual.md mesh node operator's manual].

= Troubleshooting =
If you get the error "no such file or directory", open a new terminal and run this command to ensure that <tt>node</tt> points to your NodeJS executable:

sudo ln -s nodejs node

In the new terminal, return to the 'makenode' source code directory and try again:

npm install
./makenode.js

= Flashing TP-Link Routers =
If you happen to come across a TP-Link router, such as a WDR4300, you may discover that the above instructions absolutely do not work. This is especially true if the router has previously been flashed with the sudowrt firmware (or any kind of OpenWRT or DD-WRT?). If you find yourself attempting to reflash a TP-Link router, you will first need to reset the router to its factory default firmware. Luckily, redconfetti has provided instructions on how to do this, http://www.rubycoloredglasses.com/2016/04/tp-link-wdr4300-recovery/ (TODO, test/update these instructions and copy them to this wiki)

Next, updload the sudort-firmware manually through the router's gui? Presumably, I haven't gotten that far yet...

After that, makenode should just work right?

There also exists something called tp-flasher, https://github.com/sudomesh/tp-flasher. However, it is highly recommended that you avoid using this because there is a very good chance you will brick your router if you use it incorrectly. Of course, we don't want to discourage anyone from improving tp-flasher.

= Flashing Extender Nodes =

If you would like to make long distance point-to-point connections between two or more home nodes, you'll want to setup an extender node (a roof mounted antenna).

See [[Mesh/Flashing extender nodes]]

Mesh/Flashing extender nodes

2017-10-26T08:47:30Z

Robb: /* Downgrading to earlier AirOS */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Notes !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M2 and M5 || Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015 M5 versions and all M2 versions] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016 M5 versions]
|-
| Ubiquiti Picostation 2 || Previous generation 802.11g (not the same as M2) || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobeam M2 and M5 || NBEâ€‘M2â€‘13 and NBEâ€‘M5â€‘16 work but some (earlier?) NBEâ€‘M5â€‘19 have ethernet port issues. Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobridge M2 and M5 || || Same as pre-2015 Nanostation M || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|}

== Downgrading to earlier AirOS ==

Anything with version 5.6 of AirOS and above needs to be downgraded to an earlier AirOS version before you can flash it with OpenWRT. If you don't know if you need to do this then proceed to the next section (Flash the Extender Node) and come back here if you get an error saying "Firmware check failed".

If you get this error DO NOT try to flash sudowrt/openwrt through the AirOS web interface. It will succeed and you will be stuck with a partially working system (all changes lost on every reboot) and no easy way to get it fully working.

The solution is to use the built-in AirOS web UI to upload a version 5.5 of AirOS. This will downgrade the bootloader to a point where it's compatible with sudowrt/openwrt. Here's how:

XM.v6.0.4 (v6.0.4) firmware version does not appear to be downgradable via the following method, use command-line method.

* Download the [http://home.pilsfree.net/morce/Firmware/UBNT/XW.v5.5.10.bin v5.5 AirOS firmware]
* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Power on the router.
* Wait for a couple of minutes.
* Ensure you're not connected to a wifi network that has an 192.168.1.x IP range. Disconnect/disable your wifi if you're unsure.
* In your browser go to http://192.168.1.20
* Log in using the credentials username: ubnt and password: ubnt
* Click the "System" tab.
* Click the "Browse" button next to the "Upload Firmware" box
* Select the XW.v5.5.10.bin file that you downloaded earlier.
* Click "Upload".
* After uploading you will be asked if you want to upgrade/install the firmware. Click yes/accept.
* Let the router finish flashing and wait for it to fully reboot before proceeding to flash sudowrt as described in the next section.

command-line method:

$ ssh-keygen -f "/home/yourusername/.ssh/known_hosts" -R 192.168.1.20

$ scp /''path''/''to''/''firmware''/XM.v5.5.11.28002.150723.1344.bin ubnt@192.168.1.20:/tmp/fwupdate.bin

$ ssh ubnt@192.168.1.20 (password is ubnt)

$ /sbin/fwupdate -m

$ :)

== Flash the Extender Node ==

* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings. Mac users will need to discover the proper META key to use with their Terminal program. iTerm uses the 'ESC' key.

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Extender Node Installation ==
=== Installation Order ===
#Flash home nodes and extender nodes
#Get on roof and determine which direction to face the extender nodes
#Install J-Pole
#Crimp end onto Ethernet cable
#Run Ethernet cable from j-pole down to location of home node (either through a soffit indoors or to an outdoor enclosure)
#Crimp other end of Ethernet cable and connect to home node via a POE adaptor
#Install extender node on J-Pole using zip-ties - check lights to make sure unit is powered up
#Walk around the neighborhood to check the signal

=== Gear Checklist ===

Protective and personal gear
*Wear clothes you can get dirty and sturdy boots for roof walking
*Sunscreen
*Sunglasses
*Pocketknife (for cutting zip ties etc)
*Ladder
*Safety harness & rope in a bucket
*Smart phone (to check signal and take pictures)
Home node gear
*2 flashed Western Digital Mynet N600 Home Nodes
*paperclip (to reset equipment)
*Laptop (to configure equipment)
*Plastic outdoor enclosure for router (optional)
*Power Strip
J-Pole gear
*J-Pole
*Latex gloves (for dealing with roofing sealant)
*Roofing sealant
*Ratchet set - 10mm for small bolts, 13mm for large bolts
*Corldless Drill
*3/16" drill bit for J-pole bolts
*Steel One-Hole Conduit Straps (for holding Ethernet cable along eves)
*Screws for the Steel one-hole straps
Ethernet cable gear
*Ethernet Spool
*Ethernet Ends
*Ethernet Crimper
*Laminated card showing the Ethernet cable order
*Label Maker - so you can know which cable is which
Extender node gear
*Flashed Ubiquiti Nanostation M2 or M5 extender Node(s)
*Power over Ethernet (POE) adapters
*Zip Ties

Mesh/Flashing extender nodes

2017-10-26T08:46:03Z

Robb: /* Downgrading to earlier AirOS */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Notes !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M2 and M5 || Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015 M5 versions and all M2 versions] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016 M5 versions]
|-
| Ubiquiti Picostation 2 || Previous generation 802.11g (not the same as M2) || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobeam M2 and M5 || NBEâ€‘M2â€‘13 and NBEâ€‘M5â€‘16 work but some (earlier?) NBEâ€‘M5â€‘19 have ethernet port issues. Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobridge M2 and M5 || || Same as pre-2015 Nanostation M || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|}

== Downgrading to earlier AirOS ==

Anything with version 5.6 of AirOS and above needs to be downgraded to an earlier AirOS version before you can flash it with OpenWRT. If you don't know if you need to do this then proceed to the next section (Flash the Extender Node) and come back here if you get an error saying "Firmware check failed".

If you get this error DO NOT try to flash sudowrt/openwrt through the AirOS web interface. It will succeed and you will be stuck with a partially working system (all changes lost on every reboot) and no easy way to get it fully working.

The solution is to use the built-in AirOS web UI to upload a version 5.5 of AirOS. This will downgrade the bootloader to a point where it's compatible with sudowrt/openwrt. Here's how:

XM.v6.0.4 (v6.0.4) firmware version does not appear to be downgradable via the following method, use command-line method.

* Download the [http://home.pilsfree.net/morce/Firmware/UBNT/XW.v5.5.10.bin v5.5 AirOS firmware]
* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Power on the router.
* Wait for a couple of minutes.
* Ensure you're not connected to a wifi network that has an 192.168.1.x IP range. Disconnect/disable your wifi if you're unsure.
* In your browser go to http://192.168.1.20
* Log in using the credentials username: ubnt and password: ubnt
* Click the "System" tab.
* Click the "Browse" button next to the "Upload Firmware" box
* Select the XW.v5.5.10.bin file that you downloaded earlier.
* Click "Upload".
* After uploading you will be asked if you want to upgrade/install the firmware. Click yes/accept.
* Let the router finish flashing and wait for it to fully reboot before proceeding to flash sudowrt as described in the next section.

command-line method:

$ ssh-keygen -f "/home/yourusername/.ssh/known_hosts" -R 192.168.1.20

$ scp /""path""/""to""/""firmware""/XM.v5.5.11.28002.150723.1344.bin ubnt@192.168.1.20:/tmp/fwupdate.bin

$ ssh ubnt@192.168.1.20 (password is ubnt)

$ /sbin/fwupdate -m

$ :)

== Flash the Extender Node ==

* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings. Mac users will need to discover the proper META key to use with their Terminal program. iTerm uses the 'ESC' key.

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Extender Node Installation ==
=== Installation Order ===
#Flash home nodes and extender nodes
#Get on roof and determine which direction to face the extender nodes
#Install J-Pole
#Crimp end onto Ethernet cable
#Run Ethernet cable from j-pole down to location of home node (either through a soffit indoors or to an outdoor enclosure)
#Crimp other end of Ethernet cable and connect to home node via a POE adaptor
#Install extender node on J-Pole using zip-ties - check lights to make sure unit is powered up
#Walk around the neighborhood to check the signal

=== Gear Checklist ===

Protective and personal gear
*Wear clothes you can get dirty and sturdy boots for roof walking
*Sunscreen
*Sunglasses
*Pocketknife (for cutting zip ties etc)
*Ladder
*Safety harness & rope in a bucket
*Smart phone (to check signal and take pictures)
Home node gear
*2 flashed Western Digital Mynet N600 Home Nodes
*paperclip (to reset equipment)
*Laptop (to configure equipment)
*Plastic outdoor enclosure for router (optional)
*Power Strip
J-Pole gear
*J-Pole
*Latex gloves (for dealing with roofing sealant)
*Roofing sealant
*Ratchet set - 10mm for small bolts, 13mm for large bolts
*Corldless Drill
*3/16" drill bit for J-pole bolts
*Steel One-Hole Conduit Straps (for holding Ethernet cable along eves)
*Screws for the Steel one-hole straps
Ethernet cable gear
*Ethernet Spool
*Ethernet Ends
*Ethernet Crimper
*Laminated card showing the Ethernet cable order
*Label Maker - so you can know which cable is which
Extender node gear
*Flashed Ubiquiti Nanostation M2 or M5 extender Node(s)
*Power over Ethernet (POE) adapters
*Zip Ties

Mesh/Flashing extender nodes

2017-10-26T08:29:26Z

Robb: /* Downgrading to earlier AirOS */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Notes !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M2 and M5 || Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015 M5 versions and all M2 versions] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016 M5 versions]
|-
| Ubiquiti Picostation 2 || Previous generation 802.11g (not the same as M2) || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobeam M2 and M5 || NBEâ€‘M2â€‘13 and NBEâ€‘M5â€‘16 work but some (earlier?) NBEâ€‘M5â€‘19 have ethernet port issues. Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobridge M2 and M5 || || Same as pre-2015 Nanostation M || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|}

== Downgrading to earlier AirOS ==

Anything with version 5.6 of AirOS and above needs to be downgraded to an earlier AirOS version before you can flash it with OpenWRT. If you don't know if you need to do this then proceed to the next section (Flash the Extender Node) and come back here if you get an error saying "Firmware check failed".

If you get this error DO NOT try to flash sudowrt/openwrt through the AirOS web interface. It will succeed and you will be stuck with a partially working system (all changes lost on every reboot) and no easy way to get it fully working.

The solution is to use the built-in AirOS web UI to upload a version 5.5 of AirOS. This will downgrade the bootloader to a point where it's compatible with sudowrt/openwrt. Here's how:

XM.v6.0.4 (v6.0.4) firmware version does not appear to be downgradable via the following method, use command-line method.

* Download the [http://home.pilsfree.net/morce/Firmware/UBNT/XW.v5.5.10.bin v5.5 AirOS firmware]
* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Power on the router.
* Wait for a couple of minutes.
* Ensure you're not connected to a wifi network that has an 192.168.1.x IP range. Disconnect/disable your wifi if you're unsure.
* In your browser go to http://192.168.1.20
* Log in using the credentials username: ubnt and password: ubnt
* Click the "System" tab.
* Click the "Browse" button next to the "Upload Firmware" box
* Select the XW.v5.5.10.bin file that you downloaded earlier.
* Click "Upload".
* After uploading you will be asked if you want to upgrade/install the firmware. Click yes/accept.
* Let the router finish flashing and wait for it to fully reboot before proceeding to flash sudowrt as described in the next section.

command-line method:

$ ssh-keygen -f "/home/yourusername/.ssh/known_hosts" -R 192.168.1.20

$ scp /path/to/firmware/XM.v5.5.11.28002.150723.1344.bin ubnt@192.168.1.20:/tmp/fwupdate.bin

$ ssh ubnt@192.168.1.20 (password is ubnt)

$ /sbin/fwupdate -m

$ :)

== Flash the Extender Node ==

* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings. Mac users will need to discover the proper META key to use with their Terminal program. iTerm uses the 'ESC' key.

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Extender Node Installation ==
=== Installation Order ===
#Flash home nodes and extender nodes
#Get on roof and determine which direction to face the extender nodes
#Install J-Pole
#Crimp end onto Ethernet cable
#Run Ethernet cable from j-pole down to location of home node (either through a soffit indoors or to an outdoor enclosure)
#Crimp other end of Ethernet cable and connect to home node via a POE adaptor
#Install extender node on J-Pole using zip-ties - check lights to make sure unit is powered up
#Walk around the neighborhood to check the signal

=== Gear Checklist ===

Protective and personal gear
*Wear clothes you can get dirty and sturdy boots for roof walking
*Sunscreen
*Sunglasses
*Pocketknife (for cutting zip ties etc)
*Ladder
*Safety harness & rope in a bucket
*Smart phone (to check signal and take pictures)
Home node gear
*2 flashed Western Digital Mynet N600 Home Nodes
*paperclip (to reset equipment)
*Laptop (to configure equipment)
*Plastic outdoor enclosure for router (optional)
*Power Strip
J-Pole gear
*J-Pole
*Latex gloves (for dealing with roofing sealant)
*Roofing sealant
*Ratchet set - 10mm for small bolts, 13mm for large bolts
*Corldless Drill
*3/16" drill bit for J-pole bolts
*Steel One-Hole Conduit Straps (for holding Ethernet cable along eves)
*Screws for the Steel one-hole straps
Ethernet cable gear
*Ethernet Spool
*Ethernet Ends
*Ethernet Crimper
*Laminated card showing the Ethernet cable order
*Label Maker - so you can know which cable is which
Extender node gear
*Flashed Ubiquiti Nanostation M2 or M5 extender Node(s)
*Power over Ethernet (POE) adapters
*Zip Ties

Mesh/Flashing extender nodes

2017-10-26T08:25:04Z

Robb: /* Downgrading to earlier AirOS */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Notes !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M2 and M5 || Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015 M5 versions and all M2 versions] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016 M5 versions]
|-
| Ubiquiti Picostation 2 || Previous generation 802.11g (not the same as M2) || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobeam M2 and M5 || NBEâ€‘M2â€‘13 and NBEâ€‘M5â€‘16 work but some (earlier?) NBEâ€‘M5â€‘19 have ethernet port issues. Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobridge M2 and M5 || || Same as pre-2015 Nanostation M || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|}

== Downgrading to earlier AirOS ==

Anything with version 5.6 of AirOS and above needs to be downgraded to an earlier AirOS version before you can flash it with OpenWRT. If you don't know if you need to do this then proceed to the next section (Flash the Extender Node) and come back here if you get an error saying "Firmware check failed".

If you get this error DO NOT try to flash sudowrt/openwrt through the AirOS web interface. It will succeed and you will be stuck with a partially working system (all changes lost on every reboot) and no easy way to get it fully working.

The solution is to use the built-in AirOS web UI to upload a version 5.5 of AirOS. This will downgrade the bootloader to a point where it's compatible with sudowrt/openwrt. Here's how:

XM.v6.0.4 (v6.0.4) firmware version does not appear to be downgradable via the following method, use command-line method.

* Download the [http://home.pilsfree.net/morce/Firmware/UBNT/XW.v5.5.10.bin v5.5 AirOS firmware]
* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Power on the router.
* Wait for a couple of minutes.
* Ensure you're not connected to a wifi network that has an 192.168.1.x IP range. Disconnect/disable your wifi if you're unsure.
* In your browser go to http://192.168.1.20
* Log in using the credentials username: ubnt and password: ubnt
* Click the "System" tab.
* Click the "Browse" button next to the "Upload Firmware" box
* Select the XW.v5.5.10.bin file that you downloaded earlier.
* Click "Upload".
* After uploading you will be asked if you want to upgrade/install the firmware. Click yes/accept.
* Let the router finish flashing and wait for it to fully reboot before proceeding to flash sudowrt as described in the next section.

command-line method:

$ scp /path/to/firmware/XM.v5.5.11.28002.150723.1344.bin ubnt@192.168.1.20:/tmp/fwupdate.bin

$ ssh ubnt@192.168.1.20 (password is ubnt)

$ /sbin/fwupdate -m

$ :)

== Flash the Extender Node ==

* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings. Mac users will need to discover the proper META key to use with their Terminal program. iTerm uses the 'ESC' key.

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Extender Node Installation ==
=== Installation Order ===
#Flash home nodes and extender nodes
#Get on roof and determine which direction to face the extender nodes
#Install J-Pole
#Crimp end onto Ethernet cable
#Run Ethernet cable from j-pole down to location of home node (either through a soffit indoors or to an outdoor enclosure)
#Crimp other end of Ethernet cable and connect to home node via a POE adaptor
#Install extender node on J-Pole using zip-ties - check lights to make sure unit is powered up
#Walk around the neighborhood to check the signal

=== Gear Checklist ===

Protective and personal gear
*Wear clothes you can get dirty and sturdy boots for roof walking
*Sunscreen
*Sunglasses
*Pocketknife (for cutting zip ties etc)
*Ladder
*Safety harness & rope in a bucket
*Smart phone (to check signal and take pictures)
Home node gear
*2 flashed Western Digital Mynet N600 Home Nodes
*paperclip (to reset equipment)
*Laptop (to configure equipment)
*Plastic outdoor enclosure for router (optional)
*Power Strip
J-Pole gear
*J-Pole
*Latex gloves (for dealing with roofing sealant)
*Roofing sealant
*Ratchet set - 10mm for small bolts, 13mm for large bolts
*Corldless Drill
*3/16" drill bit for J-pole bolts
*Steel One-Hole Conduit Straps (for holding Ethernet cable along eves)
*Screws for the Steel one-hole straps
Ethernet cable gear
*Ethernet Spool
*Ethernet Ends
*Ethernet Crimper
*Laminated card showing the Ethernet cable order
*Label Maker - so you can know which cable is which
Extender node gear
*Flashed Ubiquiti Nanostation M2 or M5 extender Node(s)
*Power over Ethernet (POE) adapters
*Zip Ties

Mesh/Flashing extender nodes

2017-10-26T08:23:46Z

Robb: /* Downgrading to earlier AirOS */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Notes !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M2 and M5 || Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015 M5 versions and all M2 versions] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016 M5 versions]
|-
| Ubiquiti Picostation 2 || Previous generation 802.11g (not the same as M2) || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobeam M2 and M5 || NBEâ€‘M2â€‘13 and NBEâ€‘M5â€‘16 work but some (earlier?) NBEâ€‘M5â€‘19 have ethernet port issues. Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobridge M2 and M5 || || Same as pre-2015 Nanostation M || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|}

== Downgrading to earlier AirOS ==

Anything with version 5.6 of AirOS and above needs to be downgraded to an earlier AirOS version before you can flash it with OpenWRT. If you don't know if you need to do this then proceed to the next section (Flash the Extender Node) and come back here if you get an error saying "Firmware check failed".

If you get this error DO NOT try to flash sudowrt/openwrt through the AirOS web interface. It will succeed and you will be stuck with a partially working system (all changes lost on every reboot) and no easy way to get it fully working.

The solution is to use the built-in AirOS web UI to upload a version 5.5 of AirOS. This will downgrade the bootloader to a point where it's compatible with sudowrt/openwrt. Here's how:

XM.v6.0.4 (v6.0.4) firmware version does not appear to be downgradable via the following method, use commandline method.

* Download the [http://home.pilsfree.net/morce/Firmware/UBNT/XW.v5.5.10.bin v5.5 AirOS firmware]
* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Power on the router.
* Wait for a couple of minutes.
* Ensure you're not connected to a wifi network that has an 192.168.1.x IP range. Disconnect/disable your wifi if you're unsure.
* In your browser go to http://192.168.1.20
* Log in using the credentials username: ubnt and password: ubnt
* Click the "System" tab.
* Click the "Browse" button next to the "Upload Firmware" box
* Select the XW.v5.5.10.bin file that you downloaded earlier.
* Click "Upload".
* After uploading you will be asked if you want to upgrade/install the firmware. Click yes/accept.
* Let the router finish flashing and wait for it to fully reboot before proceeding to flash sudowrt as described in the next section.

commandline method:

$ scp /path/to/firmware/XM.v5.5.11.28002.150723.1344.bin ubnt@192.168.1.20:/tmp/fwupdate.bin

$ ssh ubnt@192.168.1.20 (password is ubnt)

$ /sbin/fwupdate -m

$ :)

== Flash the Extender Node ==

* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings. Mac users will need to discover the proper META key to use with their Terminal program. iTerm uses the 'ESC' key.

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Extender Node Installation ==
=== Installation Order ===
#Flash home nodes and extender nodes
#Get on roof and determine which direction to face the extender nodes
#Install J-Pole
#Crimp end onto Ethernet cable
#Run Ethernet cable from j-pole down to location of home node (either through a soffit indoors or to an outdoor enclosure)
#Crimp other end of Ethernet cable and connect to home node via a POE adaptor
#Install extender node on J-Pole using zip-ties - check lights to make sure unit is powered up
#Walk around the neighborhood to check the signal

=== Gear Checklist ===

Protective and personal gear
*Wear clothes you can get dirty and sturdy boots for roof walking
*Sunscreen
*Sunglasses
*Pocketknife (for cutting zip ties etc)
*Ladder
*Safety harness & rope in a bucket
*Smart phone (to check signal and take pictures)
Home node gear
*2 flashed Western Digital Mynet N600 Home Nodes
*paperclip (to reset equipment)
*Laptop (to configure equipment)
*Plastic outdoor enclosure for router (optional)
*Power Strip
J-Pole gear
*J-Pole
*Latex gloves (for dealing with roofing sealant)
*Roofing sealant
*Ratchet set - 10mm for small bolts, 13mm for large bolts
*Corldless Drill
*3/16" drill bit for J-pole bolts
*Steel One-Hole Conduit Straps (for holding Ethernet cable along eves)
*Screws for the Steel one-hole straps
Ethernet cable gear
*Ethernet Spool
*Ethernet Ends
*Ethernet Crimper
*Laminated card showing the Ethernet cable order
*Label Maker - so you can know which cable is which
Extender node gear
*Flashed Ubiquiti Nanostation M2 or M5 extender Node(s)
*Power over Ethernet (POE) adapters
*Zip Ties

Mesh/Flashing extender nodes

2017-10-26T08:20:57Z

Robb: /* Downgrading to earlier AirOS */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Notes !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M2 and M5 || Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015 M5 versions and all M2 versions] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016 M5 versions]
|-
| Ubiquiti Picostation 2 || Previous generation 802.11g (not the same as M2) || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobeam M2 and M5 || NBEâ€‘M2â€‘13 and NBEâ€‘M5â€‘16 work but some (earlier?) NBEâ€‘M5â€‘19 have ethernet port issues. Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobridge M2 and M5 || || Same as pre-2015 Nanostation M || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|}

== Downgrading to earlier AirOS ==

Anything with version 5.6 of AirOS and above needs to be downgraded to an earlier AirOS version before you can flash it with OpenWRT. If you don't know if you need to do this then proceed to the next section (Flash the Extender Node) and come back here if you get an error saying "Firmware check failed".

If you get this error DO NOT try to flash sudowrt/openwrt through the AirOS web interface. It will succeed and you will be stuck with a partially working system (all changes lost on every reboot) and no easy way to get it fully working.

The solution is to use the built-in AirOS web UI to upload a version 5.5 of AirOS. This will downgrade the bootloader to a point where it's compatible with sudowrt/openwrt. Here's how:

XM.v6.0.4 (v6.0.4) firmware version does not appear to be downgradable via the following method, use commandline method.

* Download the [http://home.pilsfree.net/morce/Firmware/UBNT/XW.v5.5.10.bin v5.5 AirOS firmware]
* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Power on the router.
* Wait for a couple of minutes.
* Ensure you're not connected to a wifi network that has an 192.168.1.x IP range. Disconnect/disable your wifi if you're unsure.
* In your browser go to http://192.168.1.20
* Log in using the credentials username: ubnt and password: ubnt
* Click the "System" tab.
* Click the "Browse" button next to the "Upload Firmware" box
* Select the XW.v5.5.10.bin file that you downloaded earlier.
* Click "Upload".
* After uploading you will be asked if you want to upgrade/install the firmware. Click yes/accept.
* Let the router finish flashing and wait for it to fully reboot before proceeding to flash sudowrt as described in the next section.

commandline method:

$ scp /path/to/firmware/XM.v5.5.11.28002.150723.1344.bin ubnt@192.168.1.20:/tmp/fwupdate.bin

$ ssh ubnt@192.168.1.20

$ /sbin/fwupdate -m

$ :)

== Flash the Extender Node ==

* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings. Mac users will need to discover the proper META key to use with their Terminal program. iTerm uses the 'ESC' key.

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Extender Node Installation ==
=== Installation Order ===
#Flash home nodes and extender nodes
#Get on roof and determine which direction to face the extender nodes
#Install J-Pole
#Crimp end onto Ethernet cable
#Run Ethernet cable from j-pole down to location of home node (either through a soffit indoors or to an outdoor enclosure)
#Crimp other end of Ethernet cable and connect to home node via a POE adaptor
#Install extender node on J-Pole using zip-ties - check lights to make sure unit is powered up
#Walk around the neighborhood to check the signal

=== Gear Checklist ===

Protective and personal gear
*Wear clothes you can get dirty and sturdy boots for roof walking
*Sunscreen
*Sunglasses
*Pocketknife (for cutting zip ties etc)
*Ladder
*Safety harness & rope in a bucket
*Smart phone (to check signal and take pictures)
Home node gear
*2 flashed Western Digital Mynet N600 Home Nodes
*paperclip (to reset equipment)
*Laptop (to configure equipment)
*Plastic outdoor enclosure for router (optional)
*Power Strip
J-Pole gear
*J-Pole
*Latex gloves (for dealing with roofing sealant)
*Roofing sealant
*Ratchet set - 10mm for small bolts, 13mm for large bolts
*Corldless Drill
*3/16" drill bit for J-pole bolts
*Steel One-Hole Conduit Straps (for holding Ethernet cable along eves)
*Screws for the Steel one-hole straps
Ethernet cable gear
*Ethernet Spool
*Ethernet Ends
*Ethernet Crimper
*Laminated card showing the Ethernet cable order
*Label Maker - so you can know which cable is which
Extender node gear
*Flashed Ubiquiti Nanostation M2 or M5 extender Node(s)
*Power over Ethernet (POE) adapters
*Zip Ties

Mesh/Flashing extender nodes

2017-10-26T08:20:23Z

Robb: /* Downgrading to earlier AirOS */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Notes !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M2 and M5 || Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015 M5 versions and all M2 versions] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016 M5 versions]
|-
| Ubiquiti Picostation 2 || Previous generation 802.11g (not the same as M2) || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobeam M2 and M5 || NBEâ€‘M2â€‘13 and NBEâ€‘M5â€‘16 work but some (earlier?) NBEâ€‘M5â€‘19 have ethernet port issues. Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobridge M2 and M5 || || Same as pre-2015 Nanostation M || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|}

== Downgrading to earlier AirOS ==

Anything with version 5.6 of AirOS and above needs to be downgraded to an earlier AirOS version before you can flash it with OpenWRT. If you don't know if you need to do this then proceed to the next section (Flash the Extender Node) and come back here if you get an error saying "Firmware check failed".

If you get this error DO NOT try to flash sudowrt/openwrt through the AirOS web interface. It will succeed and you will be stuck with a partially working system (all changes lost on every reboot) and no easy way to get it fully working.

The solution is to use the built-in AirOS web UI to upload a version 5.5 of AirOS. This will downgrade the bootloader to a point where it's compatible with sudowrt/openwrt. Here's how:

XM.v6.0.4 (v6.0.4) firmware version does not appear to be downgradable via the following method, use commandline method.

* Download the [http://home.pilsfree.net/morce/Firmware/UBNT/XW.v5.5.10.bin v5.5 AirOS firmware]
* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Power on the router.
* Wait for a couple of minutes.
* Ensure you're not connected to a wifi network that has an 192.168.1.x IP range. Disconnect/disable your wifi if you're unsure.
* In your browser go to http://192.168.1.20
* Log in using the credentials username: ubnt and password: ubnt
* Click the "System" tab.
* Click the "Browse" button next to the "Upload Firmware" box
* Select the XW.v5.5.10.bin file that you downloaded earlier.
* Click "Upload".
* After uploading you will be asked if you want to upgrade/install the firmware. Click yes/accept.
* Let the router finish flashing and wait for it to fully reboot before proceeding to flash sudowrt as described in the next section.

commandline method:
$ scp /path/to/firmware/XM.v5.5.11.28002.150723.1344.bin ubnt@192.168.1.20:/tmp/fwupdate.bin
$ ssh ubnt@192.168.1.20
$ /sbin/fwupdate -m
$ :)

== Flash the Extender Node ==

* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings. Mac users will need to discover the proper META key to use with their Terminal program. iTerm uses the 'ESC' key.

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Extender Node Installation ==
=== Installation Order ===
#Flash home nodes and extender nodes
#Get on roof and determine which direction to face the extender nodes
#Install J-Pole
#Crimp end onto Ethernet cable
#Run Ethernet cable from j-pole down to location of home node (either through a soffit indoors or to an outdoor enclosure)
#Crimp other end of Ethernet cable and connect to home node via a POE adaptor
#Install extender node on J-Pole using zip-ties - check lights to make sure unit is powered up
#Walk around the neighborhood to check the signal

=== Gear Checklist ===

Protective and personal gear
*Wear clothes you can get dirty and sturdy boots for roof walking
*Sunscreen
*Sunglasses
*Pocketknife (for cutting zip ties etc)
*Ladder
*Safety harness & rope in a bucket
*Smart phone (to check signal and take pictures)
Home node gear
*2 flashed Western Digital Mynet N600 Home Nodes
*paperclip (to reset equipment)
*Laptop (to configure equipment)
*Plastic outdoor enclosure for router (optional)
*Power Strip
J-Pole gear
*J-Pole
*Latex gloves (for dealing with roofing sealant)
*Roofing sealant
*Ratchet set - 10mm for small bolts, 13mm for large bolts
*Corldless Drill
*3/16" drill bit for J-pole bolts
*Steel One-Hole Conduit Straps (for holding Ethernet cable along eves)
*Screws for the Steel one-hole straps
Ethernet cable gear
*Ethernet Spool
*Ethernet Ends
*Ethernet Crimper
*Laminated card showing the Ethernet cable order
*Label Maker - so you can know which cable is which
Extender node gear
*Flashed Ubiquiti Nanostation M2 or M5 extender Node(s)
*Power over Ethernet (POE) adapters
*Zip Ties

Mesh/Flashing extender nodes

2017-10-26T06:13:47Z

Robb: /* Downgrading to earlier AirOS */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Notes !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M2 and M5 || Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015 M5 versions and all M2 versions] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016 M5 versions]
|-
| Ubiquiti Picostation 2 || Previous generation 802.11g (not the same as M2) || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobeam M2 and M5 || NBEâ€‘M2â€‘13 and NBEâ€‘M5â€‘16 work but some (earlier?) NBEâ€‘M5â€‘19 have ethernet port issues. Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobridge M2 and M5 || || Same as pre-2015 Nanostation M || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|}

== Downgrading to earlier AirOS ==

Anything with version 5.6 of AirOS and above needs to be downgraded to an earlier AirOS version before you can flash it with OpenWRT. If you don't know if you need to do this then proceed to the next section (Flash the Extender Node) and come back here if you get an error saying "Firmware check failed".

If you get this error DO NOT try to flash sudowrt/openwrt through the AirOS web interface. It will succeed and you will be stuck with a partially working system (all changes lost on every reboot) and no easy way to get it fully working.

The solution is to use the built-in AirOS web UI to upload a version 5.5 of AirOS. This will downgrade the bootloader to a point where it's compatible with sudowrt/openwrt. Here's how:

XM.v6.0.4 (v6.0.4) firmware version does not appear to be downgradable via the following method (please write FCC with complaints, if you're bored)

* Download the [http://home.pilsfree.net/morce/Firmware/UBNT/XW.v5.5.10.bin v5.5 AirOS firmware]
* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Power on the router.
* Wait for a couple of minutes.
* Ensure you're not connected to a wifi network that has an 192.168.1.x IP range. Disconnect/disable your wifi if you're unsure.
* In your browser go to http://192.168.1.20
* Log in using the credentials username: ubnt and password: ubnt
* Click the "System" tab.
* Click the "Browse" button next to the "Upload Firmware" box
* Select the XW.v5.5.10.bin file that you downloaded earlier.
* Click "Upload".
* After uploading you will be asked if you want to upgrade/install the firmware. Click yes/accept.
* Let the router finish flashing and wait for it to fully reboot before proceeding to flash sudowrt as described in the next section.

== Flash the Extender Node ==

* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings. Mac users will need to discover the proper META key to use with their Terminal program. iTerm uses the 'ESC' key.

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Extender Node Installation ==
=== Installation Order ===
#Flash home nodes and extender nodes
#Get on roof and determine which direction to face the extender nodes
#Install J-Pole
#Crimp end onto Ethernet cable
#Run Ethernet cable from j-pole down to location of home node (either through a soffit indoors or to an outdoor enclosure)
#Crimp other end of Ethernet cable and connect to home node via a POE adaptor
#Install extender node on J-Pole using zip-ties - check lights to make sure unit is powered up
#Walk around the neighborhood to check the signal

=== Gear Checklist ===

Protective and personal gear
*Wear clothes you can get dirty and sturdy boots for roof walking
*Sunscreen
*Sunglasses
*Pocketknife (for cutting zip ties etc)
*Ladder
*Safety harness & rope in a bucket
*Smart phone (to check signal and take pictures)
Home node gear
*2 flashed Western Digital Mynet N600 Home Nodes
*paperclip (to reset equipment)
*Laptop (to configure equipment)
*Plastic outdoor enclosure for router (optional)
*Power Strip
J-Pole gear
*J-Pole
*Latex gloves (for dealing with roofing sealant)
*Roofing sealant
*Ratchet set - 10mm for small bolts, 13mm for large bolts
*Corldless Drill
*3/16" drill bit for J-pole bolts
*Steel One-Hole Conduit Straps (for holding Ethernet cable along eves)
*Screws for the Steel one-hole straps
Ethernet cable gear
*Ethernet Spool
*Ethernet Ends
*Ethernet Crimper
*Laminated card showing the Ethernet cable order
*Label Maker - so you can know which cable is which
Extender node gear
*Flashed Ubiquiti Nanostation M2 or M5 extender Node(s)
*Power over Ethernet (POE) adapters
*Zip Ties

Mesh/Flashing extender nodes

2017-10-25T18:44:40Z

Robb: /* Downgrading to earlier AirOS */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Notes !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M2 and M5 || Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015 M5 versions and all M2 versions] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016 M5 versions]
|-
| Ubiquiti Picostation 2 || Previous generation 802.11g (not the same as M2) || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobeam M2 and M5 || NBEâ€‘M2â€‘13 and NBEâ€‘M5â€‘16 work but some (earlier?) NBEâ€‘M5â€‘19 have ethernet port issues. Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobridge M2 and M5 || || Same as pre-2015 Nanostation M || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|}

== Downgrading to earlier AirOS ==

Anything with version 5.6 of AirOS and above needs to be downgraded to an earlier AirOS version before you can flash it with OpenWRT. If you don't know if you need to do this then proceed to the next section (Flash the Extender Node) and come back here if you get an error saying "Firmware check failed".

If you get this error DO NOT try to flash sudowrt/openwrt through the AirOS web interface. It will succeed and you will be stuck with a partially working system (all changes lost on every reboot) and no easy way to get it fully working.

The solution is to use the built-in AirOS web UI to upload a version 5.5 of AirOS. This will downgrade the bootloader to a point where it's compatible with sudowrt/openwrt. Here's how:

* Download the [http://home.pilsfree.net/morce/Firmware/UBNT/XW.v5.5.10.bin v5.5 AirOS firmware]
* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Power on the router.
* Wait for a couple of minutes.
* Ensure you're not connected to a wifi network that has an 192.168.1.x IP range. Disconnect/disable your wifi if you're unsure.
* In your browser go to http://192.168.1.20
* Log in using the credentials username: ubnt and password: ubnt
* Click the "System" tab.
* Click the "Browse" button next to the "Upload Firmware" box (may have to change default username/password in order to Browse)
* Select the XW.v5.5.10.bin file that you downloaded earlier.
* Click "Upload".
* After uploading you will be asked if you want to upgrade/install the firmware. Click yes/accept.
* Let the router finish flashing and wait for it to fully reboot before proceeding to flash sudowrt as described in the next section.

== Flash the Extender Node ==

* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings. Mac users will need to discover the proper META key to use with their Terminal program. iTerm uses the 'ESC' key.

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Extender Node Installation ==
=== Installation Order ===
#Flash home nodes and extender nodes
#Get on roof and determine which direction to face the extender nodes
#Install J-Pole
#Crimp end onto Ethernet cable
#Run Ethernet cable from j-pole down to location of home node (either through a soffit indoors or to an outdoor enclosure)
#Crimp other end of Ethernet cable and connect to home node via a POE adaptor
#Install extender node on J-Pole using zip-ties - check lights to make sure unit is powered up
#Walk around the neighborhood to check the signal

=== Gear Checklist ===

Protective and personal gear
*Wear clothes you can get dirty and sturdy boots for roof walking
*Sunscreen
*Sunglasses
*Pocketknife (for cutting zip ties etc)
*Ladder
*Safety harness & rope in a bucket
*Smart phone (to check signal and take pictures)
Home node gear
*2 flashed Western Digital Mynet N600 Home Nodes
*paperclip (to reset equipment)
*Laptop (to configure equipment)
*Plastic outdoor enclosure for router (optional)
*Power Strip
J-Pole gear
*J-Pole
*Latex gloves (for dealing with roofing sealant)
*Roofing sealant
*Ratchet set - 10mm for small bolts, 13mm for large bolts
*Corldless Drill
*3/16" drill bit for J-pole bolts
*Steel One-Hole Conduit Straps (for holding Ethernet cable along eves)
*Screws for the Steel one-hole straps
Ethernet cable gear
*Ethernet Spool
*Ethernet Ends
*Ethernet Crimper
*Laminated card showing the Ethernet cable order
*Label Maker - so you can know which cable is which
Extender node gear
*Flashed Ubiquiti Nanostation M2 or M5 extender Node(s)
*Power over Ethernet (POE) adapters
*Zip Ties

Mesh/Flashing extender nodes

2017-10-25T18:43:36Z

Robb: /* Downgrading to earlier AirOS */

== Download the Image File For a Extender Node ==

The extender nodes that we currently support are:

{| class="wikitable"
! Name !! Notes !! OpenWRT Doc !! Firmware Image
|-
| Ubiquiti Nanostation M2 and M5 || Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanostationm5 OpenWRT Docs] || firmware: [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin pre 2015 M5 versions and all M2 versions] or [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin 2015-2016 M5 versions]
|-
| Ubiquiti Picostation 2 || Previous generation 802.11g (not the same as M2) || [https://wiki.openwrt.org/toh/ubiquiti/picostation2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ath25.extender-node/openwrt-ath25-ubnt2-pico2-squashfs.bin firmware image]
|-
| Ubiquiti Picostation M2 || || [https://wiki.openwrt.org/toh/ubiquiti/picostationm2 OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobeam M2 and M5 || NBEâ€‘M2â€‘13 and NBEâ€‘M5â€‘16 work but some (earlier?) NBEâ€‘M5â€‘19 have ethernet port issues. Newer models need [[#Downgrading_to_earlier_AirOS|AirOS downgrade]] before flashing! || [https://wiki.openwrt.org/toh/ubiquiti/nanobeam OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-loco-m-xw-squashfs-factory.bin firmware image]
|-
| Ubiquiti Nanobridge M2 and M5 || || Same as pre-2015 Nanostation M || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin firmware image]
|-
| Ubiquiti Bullet M2 and M5 || || [https://wiki.openwrt.org/toh/ubiquiti/bullet OpenWRT Docs] || [https://builds.sudomesh.org/builds/chaos_calmer/ar71xx.extender-node/openwrt-ar71xx-generic-ubnt-bullet-m-squashfs-factory.bin firmware image]
|}

== Downgrading to earlier AirOS ==

Anything with version 5.6 of AirOS and above needs to be downgraded to an earlier AirOS version before you can flash it with OpenWRT. If you don't know if you need to do this then proceed to the next section (Flash the Extender Node) and come back here if you get an error saying "Firmware check failed".

If you get this error DO NOT try to flash sudowrt/openwrt through the AirOS web interface. It will succeed and you will be stuck with a partially working system (all changes lost on every reboot) and no easy way to get it fully working.

The solution is to use the built-in AirOS web UI to upload a version 5.5 of AirOS. This will downgrade the bootloader to a point where it's compatible with sudowrt/openwrt. Here's how:

* Download the [http://home.pilsfree.net/morce/Firmware/UBNT/XW.v5.5.10.bin v5.5 AirOS firmware]
* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Power on the router.
* Wait for a couple of minutes.
* Ensure you're not connected to a wifi network that has an 192.168.1.x IP range. Disconnect/disable your wifi if you're unsure.
* In your browser go to http://192.168.1.20
* Log in using the credentials username: ubnt and password: ubnt
* Click the "System" tab.
* Click the "Browse" button next to the "Upload Firmware" box (may have to change default username/password to Browse)
* Select the XW.v5.5.10.bin file that you downloaded earlier.
* Click "Upload".
* After uploading you will be asked if you want to upgrade/install the firmware. Click yes/accept.
* Let the router finish flashing and wait for it to fully reboot before proceeding to flash sudowrt as described in the next section.

== Flash the Extender Node ==

* Configure your wired ethernet interface to use IP: 192.168.1.10, subnet: 255.255.255.0
* Plug one Ethernet cable into your laptop on one end and into the "LAN" port of the power-over-ethernet power supply on the other end.
* Plug another Ethernet cable into your node/router on one end and into the "POE" port of the power-over-ethernet power supply on the other end.
* Push a pin into the reset hole and hold it.
* With the pin held down, plug in the power to the power-over-ethernet power supply.
* Watch the lights on the antenna - they will all flash together a few times, then they will flash up and down.
* Once the lights on the antenna are flashing up and down, you can let go of the pin.

You should be able to ping the extender at 192.168.1.20.

$ ping 192.168.1.20
PING 192.168.1.20 (192.168.1.20) 56(84) bytes of data.
64 bytes from 192.168.1.20: icmp_seq=1 ttl=64 time=1.54 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=64 time=0.826 ms

In your Linux terminal, type:

git clone https://github.com/sudomesh/ubi-flasher
cd ubi-flasher
npm install
./flasher.js '<path to firmware>'

The terminal will tell you "The firmware has been successfully sent to the router. In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up). This means that the router is flashing itself with the new firmware. Once the router goes back to having only the power LED lit, the router has been successfully flashed."

Wait until the antenna has only the power LED lit and you're done.

Reconfigure your machine with the following static network configuration.

* IP Address: 172.22.0.10
* Subnet mask: 255.255.255.0
* Gateway: 0.0.0.0

See Network Configuration Guides: [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20Linux Linux] [https://sudoroom.org/wiki/Mesh/Network%20Configuration%20for%20MacOS%20X Mac]

If you ping the extender node on 172.22.0.2 and it responds, it should be ready to connect to your home node on the appropriate wired Ethernet port.

$ ping 172.22.0.2
PING 172.22.0.2 (172.22.0.2) 56(84) bytes of data.
64 bytes from 172.22.0.2: icmp_seq=1 ttl=64 time=0.617 ms
64 bytes from 172.22.0.2: icmp_seq=2 ttl=64 time=0.316 ms
64 bytes from 172.22.0.2: icmp_seq=3 ttl=64 time=0.398 ms

== Extender Detection ==

Log into your home node via SSH, and tail <tt>/var/log/messages</tt>

Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: eth0.3: Physical disconnect detected
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: Listening on interface eth0.3:
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client IP: 100.64.37.3
Sun May 8 00:51:08 2016 daemon.debug notdhcpserver: client netmask 26
Sun May 8 00:51:12 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
...
Sun May 8 00:54:00 2016 daemon.debug notdhcpserver: eth0.3: Recieved HEARTBEAT for interface that hadn't been ACKed.
Sun May 8 00:54:00 2016 daemon.info hostapd: priv5: STA 80:e6:50:0e:fe:6e WPA: group key handshake completed (RSN)
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.2: Received lease request
Sun May 8 00:54:04 2016 daemon.debug notdhcpserver: eth0.3: sending response (with ssl certificate)
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Running up hook script
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK
Sun May 8 00:54:32 2016 daemon.debug notdhcpserver: eth0.3: Received redundant ACK

There should be a debug message in the log from notdhcpserver concerning the extender node.

== Troubleshooting ==

=== USB to Serial Connection ===

If you experience trouble flashing your device via the web interface, or via the TFTP image upload method, you'll want to establish a serial connection to troubleshoot further. Methods for flashing your device involving a serial connection may become more common as devices adopt configurations to lock down [http://www.networkworld.com/article/3038722/mobile-wireless/manufacturers-start-to-lock-down-wi-fi-router-firmware-thanks-fcc.html wi-fi router firmware] to prevent flashing.

The following notes describe steps to interface with a Nanostation M5 (NSM5) via the serial interface.

==== Order a USB to Serial Converter ====

USB to serial converter devices exist at a cost of $4 - $8 online, with much lower pricing and longer delivery times if ordered from China. Search for "USB to UART TTL", including "5 pin" in the search. Make sure the specifications do not mention anything other than 3.3 volts.

Mac OS X users may need to install a device driver for their device. For example, for devices using the CP210X chip, you can download the [https://www.silabs.com/products/mcu/Pages/USBtoUARTBridgeVCPDrivers.aspx#mac CP210x USB to UART Bridge VCP Driver], which is made available as <tt>/dev/tty.SLAB_USBtoUART</tt>.

==== Connecting to Serial ====

You will need to connect the following pins from the converter to the pins on the device.

* Ground (GND)
* Serial Out (Transmit / TX)
* Serial In (Receive / RX)

Begin by connecting the Ground of the converter to the Ground of the device. Next connect the Transmit/TX of the converter to the Receive/RX of the device, then connect the Receive/RX of the converter to the Transmit/TX of the device.

Nanostation M5 (NSM5) Example:

[[File:CP2102-usb-to-serial-converter.jpg|400px|KEDSUMÂ® CP2102 Module STC Download Cable USB 2.0 to TTL 6PIN Serial Converter For STC]]

[[File:Ubiquity-NSM5-serial-connectors.jpg|400px|Ubiquiti Nanostation NSM5 - Serial pins with connections]]

==== Serial Communications Program ====

You need to install a serial communication program. Linux users can use Minicom.

sudo apt-get install minicom

Mac OS X users can as well

brew install minicom

By default the Minicom program will attempt to use /dev/tty8, and will also attempt to initialize the device (expecting a modem) by default.

$ minicom
minicom: cannot open /dev/tty8: Permission denied

Run the program so that it starts the program on the USB converter that is connected by adding <tt>-D /dev/ttyUSB0</tt>, and specify that it should skip initialization by adding <tt>-o</tt>. Mac users may need to reference a different device (such as <tt>/dev/tty.SLAB_USBtoUART</tt>).

You can also specify from the command line that it use the baud rate and '8N1' settings specified below by including <tt>-b 115200 -8</tt>.

sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8

In Minicom, CTRL-A to get settings, then Press O, to access settings. Mac users will need to discover the proper META key to use with their Terminal program. iTerm uses the 'ESC' key.

Go to Serial Port Setup, use these settings:

* Set the serial device (should be /dev/tty/USB0)
* Baud Rate (Bits Per Second): 115200
* Settings '8N1' (short hand for 8 bits, no parity, 1 stop bit)
* Turn off hardware and software flow control

Reboot the device, and it will let you drop into a command line. You will then have to figure out how to enable the network from the boot loader (Uboot or Redboot) and transfer the firmware to the device to flash it.

==== Interupting Boot ====

The device will not detect the key you press unless Minicom is configured properly.

* To access the Help screen, Press CTRL-A, then press Z.
* To access the configuration/settings, press CTRL-A, then press O.

From the configuration window, select to view the 'Serial port setup'

$ sudo minicom -D /dev/ttyUSB0 -o -b 115200 -8
Welcome to minicom 2.7

OPTIONS: I18n
Compiled on Jan 1 2014, 17:13:19.
Port /dev/ttyUSB0, 21:47:56

Press CTRL-A Z for help on special keys

+-----[configuration]------+
| Filenames and paths |
| File transfer protocols |
| Serial port setup |
| Modem and dialing |
| Screen and keyboard |
| Save setup as dfl |
| Save setup as.. |
| Exit |
+--------------------------+

+-----------------------------------------------------------------------+
| A - Serial Device : /dev/ttyUSB0 |
| B - Lockfile Location : /var/lock |
| C - Callin Program : |
| D - Callout Program : |
| E - Bps/Par/Bits : 115200 8N1 |
| F - Hardware Flow Control : Yes |
| G - Software Flow Control : No |
| |
| Change which setting? |
+-----------------------------------------------------------------------+

By default the Hardware Flow Control will be enabled. Press 'F' to disable Hardware Flow Control. Press ENTER to exit the Serial port setup window, and then select EXIT to go back to the program.

At this point plug in the Ethernet cable to the 'Main' Ethernet port, with the other end connected to the 'POE' port on the Power Over Ethernet adapter that came with the device. As the device boots up, you'll see output similar to the following.

You'll need to make sure to press a key before it boots the default image.

=== Picostation M2HP ===

Insightful post on [https://www.strugglingcoder.info/index.php/tag/ubnt/ loading FreeBSD image] with help from serial communications. Could be useful with troubleshooting other models.
=== Nanostation M2 ===
==== Firmware check failure ====

The following are simply notes. A solution to this issue is still pending.

Flashing the Nanostation M2 (FCC ID: SWX-M2N) using the TFTP rescue mode will result in a Firmware check failure error.

$ tftp 192.168.1.20
tftp> bin
tftp> put openwrt-ar71xx-generic-om2p-squashfs-factory.bin
Error code 2: Firmware check failed
Sent 4609024 bytes in 12.6 seconds

You can boot up the M2 with a serial connection similar to the instructions below concerning the Nanostation M5.

Board: Ubiquiti Networks XM board (rev 1.0 e012)
DRAM: 32 MB
Flash: 8 MB
PCIe WLAN Module found (#1).
Net: eth0, eth1
Hit any key to stop autoboot: 0
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: |
Receiving file from 192.168.1.10:35456
Received 4609501 bytes
Firmware check failed! (-2)

The method outlined for the Nanostation M5 below doesn't work with the M2.

Update the firmware to [http://dl.ubnt.com/firmwares/XN-fw/v5.6.4/XM.v5.6.4.28924.160331.1253.bin airOS for XM board firmware v5.6.4].

Serial Connection:

ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

Terminal:

$ tftp 192.168.1.20
tftp> bin
tftp> put XM.v5.6.4.28924.160331.1253.bin
Sent 7537129 bytes in 20.8 seconds

Serial Connection:

Receiving file from 192.168.1.10:55113
Received 7537129 bytes
Firmware Version: XM.ar7240.v5.6.4.28924.160331.1253
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... done
Protected 1 sectors
Will not overwrite u-boot partition! Skipped.
Copying partition 'kernel' to flash memory:
erasing range 0x9F050000..0x9F14FFFF: ................ done
Erased 16 sectors
writing to address 0x9f050000, length 0x00100000 ...
Copying partition 'rootfs' to flash memory:
erasing range 0x9F150000..0x9F74FFFF: .............................................................................................e
Erased 96 sectors
writing to address 0x9f150000, length 0x00600000 ...

Firmware update complete.

Resetting...

U-Boot 1.1.4.2-s594 (Dec 5 2012 - 15:23:07)

Board: Ubiquiti Networks XM board (rev 1.0 e012)

Attempting to run the same process after performing an official firmware update doesn't resolve the issue.

=== Nanostation M5 ===

Official firmware from Ubiquity Nanostation M5 (NSM5)

* [https://www.ubnt.com/download/airmax-m/nanostationm/default/airos-xw-board-firmware-v564 airOS for XW board firmware v5.6.4]

==== Firmware check failure ====

Flashing the Nanostation M5 (FCC ID: SWX-NSM5D) using the TFTP rescue mode will result in a Firmware check failure error.

If you attempt to flash the extender and receive a 'Firmware check failed' error, then you have a version of the NSM5 that is protected from being flashed via the default TFTP method. You will need to obtain a serial to USB interface (USB to UART TTL Module Serial Converter, 5 pin) and use it to flash the firmware.

$ ./flasher.js openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending openwrt-ar71xx-generic-ubnt-nano-m-squashfs-factory.bin to 192.168.1.20 using tftp put
[Error: (Server) Firmware check failed]

When connected to the NSM5 via a serial connection, a similar error is displayed when attempting to load the SudoWRT firmware image.

Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Will reset device configuration (Reset button active after 10 seconds).
Erasing sector 123..126

First 0x7b last 0x7e sector size 0x10000
.... done
Waiting for connection: \
Receiving file from 192.168.1.10:49763
Received 4325788 bytes
Firmware check failed! (1)

===== Drop into U-Boot Command Prompt =====

Connect a USB to Serial adapter to the correct pins of the NSM5, as shown above. Unplug the Ethernet cable from the device, and then plug it back in to provide Power Over Ethernet once again, resulting in a reboot of the device.

During the boot process, press a key to during the boot process to make the [https://wiki.openwrt.org/doc/techref/bootloader/uboot U-Boot] bootloader to drop into a command line prompt.

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
ar7240>

===== Running TFTPd =====

Although U-Boot can support two protocols for transfering files, kermit or y-modem, the bootloader does not support the <tt>loadb</tt> or <tt>loady</tt>. Minicom only supports y-modem protocol.

We do not have to resort to a direct serial file transfer however. The 'mtdparts' command that is used to define flash memory partitions can be used to reset the partition table to the defaults before running 'urescue' to start the TFTP server.

ar7240> help mtdparts
mtdparts
- list partition table
mtdparts delall
- delete all partitions
mtdparts del part-id
- delete partition (e.g. part-id = nand0,1)
mtdparts add <mtd-dev> <size>[@<offset>] [<name>] [ro]
- add partition
mtdparts default
- reset partition table to defaults
ar7240> mtdparts default
ar7240> urescue
Setting default IP 192.168.1.20
Starting TFTP server...
Using eth0 (192.168.1.20), address: 0x81000000
Waiting for connection: \

In your other terminal window, run the ubi-flasher script.

$ ./flasher.js /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin
Accessing http://192.168.1.20/login.cgi
Connection timed out
Sending /home/redconfetti/Projects/mesh/openwrt-images/nanostation-m5/2015-2016/openwrt-ar71xx-generic-ubnt-nano-m-xw-squashfs-factory.bin to 192.168.1.20 using tftp put
Firmware flashing begun!
The firmware has been successfully sent to the router.
In a few seconds, the router should begin flashing its four status LEDs sweeping from left to right, then right to left (or up down, down up).
This means that the router is flashing itself with the new firmware.
Once the router goes back to having only the power LED lit, the router has been successfully flashed.

In the terminal running Minicom you should see the firmware successfully flashing.

Receiving file from 192.168.1.10:52289
Received 4325788 bytes
Firmware Version: XW.ar934x.v6.0.0-OpenWrt-r47662
Setting U-Boot environment variables
Un-Protected 1 sectors
Erasing Flash.... done
Erased 1 sectors
Writing to Flash... write addr: 9f040000
done
Protected 1 sectors
Copying partition 'kernel' to flash memory:

First 0x5 last 0x14 sector size 0x10000
................ done
write addr: 9f050000
Copying partition 'rootfs' to flash memory:

First 0x15 last 0x6e sector size 0x10000
.......................................................................................... done
write addr: 9f150000

Firmware update complete.

Resetting...

U-Boot 1.1.4-s958 (Jun 10 2015 - 10:56:20)

DRAM: 64 MB
Flash: 8 MB (0xc2, 0x20, 0x17)
Net: AR8236
eth0, eth1
Board: Ubiquiti Networks AR9342 board (e855-22585.1122.0030)
Radio: 0777:e855
Reset: Normal
Hit any key to stop autoboot: 0
## Booting image at 9f050000 ...
Image Name: MIPS OpenWrt Linux-3.18.23
Created: 2015-12-01 0:03:51 UTC
Image Type: MIPS Linux Kernel Image (lzma compressed)
Data Size: 1135619 Bytes = 1.1 MB
Load Address: 80060000
Entry Point: 80060000
Verifying Checksum at 0x9f050040 ...OK
Uncompressing Kernel Image ... OK

Starting kernel ...

[ 0.000000] Linux version 3.18.23 (sudowrt-builder@build-test2) (gcc version 4.8.3 (OpenWrt/Linaro GCC 4.8-2014.04 r47662) ) #2 Mon Nov 5

After it reboots if you see the first line mention 'sudowrt-builder', the device is booting the SudoWRT firmware build.

You can press ENTER once it is finished, and it should drop into the command line for the SudoWRT system.

[ 25.650000] jffs2: Newly-erased block contained word 0xdeadc0de at offset 0x00000000
[ 25.660000] done.
[ 25.660000] jffs2: notice: (993) jffs2_build_xattr_subsystem: complete building xattr subsystem, 0 of xdatum (0 unchecked, 0 orphan) and.

BusyBox v1.23.2 (2015-11-30 18:48:50 EST) built-in shell (ash)

._______.___ ._______.______ ._____ .___ .___ .______ ._____
:_ ____/| | : .____/:_ _ \ :_ ___\ | | : __|: \ :_ ___\
| _/ | | | : _/\ | | || |___| | | : || || |___
| | | |/\ | / \| . | || / || |/\ | || | || / |
|_. | | / \|_.: __/|. ____/ |. __ || / \| ||___| ||. __ |
:/ |______/ :/ :/ :/ |. ||______/|___| |___| :/ |. |
: : : :/ : :/
: :
-------------------------------------------------------------------------
sudo mesh v0.2 (fledgling.extender)
based on OpenWRT 15.05 (Chaos Calmer)
-------------------------------------------------------------------------
"When your rage is choking you, it is best to say nothing."
- Octavia E. Butler, Fledgling
-------------------------------------------------------------------------

root@sudomesh-node:/#

== Extender Node Installation ==
=== Installation Order ===
#Flash home nodes and extender nodes
#Get on roof and determine which direction to face the extender nodes
#Install J-Pole
#Crimp end onto Ethernet cable
#Run Ethernet cable from j-pole down to location of home node (either through a soffit indoors or to an outdoor enclosure)
#Crimp other end of Ethernet cable and connect to home node via a POE adaptor
#Install extender node on J-Pole using zip-ties - check lights to make sure unit is powered up
#Walk around the neighborhood to check the signal

=== Gear Checklist ===

Protective and personal gear
*Wear clothes you can get dirty and sturdy boots for roof walking
*Sunscreen
*Sunglasses
*Pocketknife (for cutting zip ties etc)
*Ladder
*Safety harness & rope in a bucket
*Smart phone (to check signal and take pictures)
Home node gear
*2 flashed Western Digital Mynet N600 Home Nodes
*paperclip (to reset equipment)
*Laptop (to configure equipment)
*Plastic outdoor enclosure for router (optional)
*Power Strip
J-Pole gear
*J-Pole
*Latex gloves (for dealing with roofing sealant)
*Roofing sealant
*Ratchet set - 10mm for small bolts, 13mm for large bolts
*Corldless Drill
*3/16" drill bit for J-pole bolts
*Steel One-Hole Conduit Straps (for holding Ethernet cable along eves)
*Screws for the Steel one-hole straps
Ethernet cable gear
*Ethernet Spool
*Ethernet Ends
*Ethernet Crimper
*Laminated card showing the Ethernet cable order
*Label Maker - so you can know which cable is which
Extender node gear
*Flashed Ubiquiti Nanostation M2 or M5 extender Node(s)
*Power over Ethernet (POE) adapters
*Zip Ties

5MoF

2017-07-22T15:00:09Z

Robb: /* Future of 5MoFs */

<div style="margin:auto;text-align: center;border: 6px solid #00b;background-color:#fff;color:#000; margin:1em;">
<big><big><big>SIGN UP NOW! [[5MoF 2017-06-14|Upcoming 5MoF: June 14, 2017 8:00pm]]</big></big></big>
</div>

The sudo room five minutes of fame is a social event where a bunch of folks meet up and munch on snacks while some folks make short 5 minute presentations about projects they're working on or things they care about.

This type of event is blatantly stolen^H^H^H^H^H^H^H^H^H^H^H^H^H^H^H^Hheavily inspired by the noisebridge 5MoF events.

People are encouraged to bring snacks/food/drinks.

= Schedule =

These events happen every first Wednesday of the month at sudo room!

Email info@sudoroom.org or [https://sudoroom.org/lists/listinfo/sudo-discuss the sudo room mailing list] to claim a slot for your project. All we need is the title of your presentation and a way to contact you.

7 minutes are allocated to each 5MoF presentation which includes 5 minutes for the presentation, time for questions and time for the next person to get their computer hooked up.

*7 pm: People shuffle in, snack on food and get settled
*7:30 pm: 1st 5MoF presentation
*7:37 pm: 2nd 5MoF presentation
*7:44 pm: 3rd 5MoF presentation
*7:51 pm: 4th 5MoF presentation
*7:58 pm: 5th 5MoF presentation
*8:05 pm: 10 minute break (announced as a 5 minute break so we actually stay on time)
*8:15 pm: two-minute explanation of sudo room and the Omni. Donation hat passed around. New members encouraged to sign up right then and there.
*8:18 pm: 6th 5MoF presentation - This is the remote presentation which gives time to set up the video conferencing during the break.
*8:25 pm: 7th 5MoF presentation
*8:32 pm: 8th 5MoF presentation
*8:39 pm: 9th 5MoF presentation
*8:46 pm: 10th 5MoF presentation
*8:53 pm: Announce https://pad.riseup.net/p/sudoride for letting people ride-share back home.
*8:54 pm: Social hangouts and tour of omni for new folk.
*10:00 pm: Cleanup of food, chairs, etc. and moving folks to sudo room for continued hacking/socializing.

= For speakers =

We provide a stage with a small podium for a laptop, amplified microphone, spotlights and a projector.

We provide a laptop running lubuntu (with firefox) which is already hooked up to the projector, internet and audio. It has LibreOffice and the Eye of Gnome image viewer. You can either make you presentation available on the internet or on a USB stick. As you are setting up to speak please tell a volunteer if you plan to use audio from the laptop.

If you want to use your own laptop we provide the following connectors:

* VGA and HDMI for projector hookup. If you need anything else then bring the appropriate adapter.
* Ethernet for internet. Don't rely on wifi. If you don't have ethernet then bring the appropriate adapter.
* Mini jack (3.5 mm TRRS) for audio output from your laptop.
* Power

If you want to remote in, please email info@sudoroom.org before the event. You will need to use a WebRTC-based (web-based) video chat client which works in firefox and does not require any plugins to be installed nor any signup. Right now we're recommending [https://talky.io/ takly] but we're open to suggestions.

If you have any other needs, please contact info@sudoroom.org before the event.

= Previous of 5MoFs =

* [[5MoF 2017-05-03]]
* [[5MoF 2017-04-05]]
* [[5MoF 2017-03-01]]

= Future of 5MoFs =

* [[5MoF 2017-08-2]]

Logo

2017-01-27T01:47:21Z

Robb: /* Gallery */

[[File:SudoRoom Logo.jpg|thumb|meeting about the logo]] The current Sudo Room logo is in '''iteration 2.0''', and can be downloaded as '''icon''' and '''wordmark''' in both print and web resolutions.

==Reverse-Inspiration==
'''Post-design readings of the new logo 2.0.''' Check this out: [https://en.wikipedia.org/wiki/Flower_of_life Flower of Life] and this: [https://en.wikipedia.org/wiki/File:Metatron_solids.svg Metatron's Cube and the Platonic Solids]

==Gallery==
<gallery>
File:Sudo 2.0 Logo.png|thumb|Sudo Room logo, web version. Approximately 3" tall @ 72 dpi.
File:Sudo 2.0 Print Logo.jpg|thumb|Sudo Room logo, print version. Approximately 3" tall @ 300 dpi.
File:Sudoroom logo.png|thumb|alternative raster version of logo
File:Sudoroom logo.svg|thumb|scalable vector graphic (svg) version of logo
File:Sudo 2.0 Web Wordmark.png|thumb|Sudo Room logo with wordmark, web version. Approximately 5" wide @ 72dpi.
File:Sudo 2.0 Print Wordmark.jpg|thumb|Sudo Room logo with wordmark, web version. Approximately 5" wide @ 300dpi.
File:Sudoroom logo text.png|thumb|alternative raster version of logo and text
File:Sudoroom logo text.svg|thumb|scalable vector graphic (svg) version of logo and text
File:Sudoroom-sticker.png|thumb|sudoroom hexagon sticker type 1
File:Sudoroom-hexagon-sticker-2.png|thumb|sudoroom hexagon sticker type 2
File:Sudo-logo-spin.mp4.mp4|thumb|Sudoroom logo Synfig animation
</gallery>

File:Sudo-logo-spin.png.png

2017-01-27T00:17:09Z

Robb:

Thumbnail 4 sudo-logo-spin.mp4

File:Sudo-logo-spin.mp4.mp4

2017-01-27T00:08:04Z

Robb:

Synfig animation

Omniphwn

2016-01-18T09:37:45Z

Robb:

Omniphonix server running AsteriskNow @100.64.64.30 configured as VOIP intercom on our local network.

VOIP phones

2016-01-18T09:35:41Z

Robb:

voip phones on the network

extension/name/ip address - description

7836/5ud0r00m/100.64.64.31 - that's us at sudoroom :)

3667/door/100.64.64.32 - frontdoor "pay"phone

225/ccl/100.64.64.33 - counter culture labs [not online]

782/pub/100.64.64.34 - public terminals

100.64.64.35/Voice_adminPage.htm
admin
omniphonix
http://innomedia.com/wp-content/uploads/2013/10/MTA-6328-2Re-DS.pdf
00:10:99:04:b7:ef

when you plug into its LAN port it gives you dhcp, you can go to http://192.168.251.1/Voice_adminPage.htm

http://www.dslreports.com/forum/r22145431-Unlock-I-think-I-bricked-my-Innomedia-MTA6328-2Re

1. Disconnect to WAN ( no internet).
2. Connect the gizmo via WAN to computer and login to it using user id
Â»192.168.1.xx/
id=user, pass=welcome
3. cut and paste the following link aninter desktop computer & giant_robot_arm serial host]]
| [[User:jake|jake]] d press enter to Restore factory default
Â»192.168.1.xx/restore2.ssi
4. power cycle the gizmo and login to admin link with factory default password.
Â»192.168.1.xx/Voice_adminPage.htm
id=admin, pass=slapshot (for V3.0.77, V3.0.75)
5. Disable Provisioning
Menu--IP Network ---Provisioning Setting
6. Change username and password!

VOIP phones

2016-01-18T09:33:32Z

Robb:

voip phones on the network

ip address/name/extension - description

100.64.64.31/5ud0r00m/7836 - that's us at sudoroom :)

100.64.64.32/door/3667 - frontdoor "pay"phone

100.64.64.33/ccl/225 - counter culture labs

100.64.64.34/pub/782 - public terminals

100.64.64.35/Voice_adminPage.htm
admin
omniphonix
http://innomedia.com/wp-content/uploads/2013/10/MTA-6328-2Re-DS.pdf
00:10:99:04:b7:ef

when you plug into its LAN port it gives you dhcp, you can go to http://192.168.251.1/Voice_adminPage.htm

http://www.dslreports.com/forum/r22145431-Unlock-I-think-I-bricked-my-Innomedia-MTA6328-2Re

1. Disconnect to WAN ( no internet).
2. Connect the gizmo via WAN to computer and login to it using user id
Â»192.168.1.xx/
id=user, pass=welcome
3. cut and paste the following link aninter desktop computer & giant_robot_arm serial host]]
| [[User:jake|jake]] d press enter to Restore factory default
Â»192.168.1.xx/restore2.ssi
4. power cycle the gizmo and login to admin link with factory default password.
Â»192.168.1.xx/Voice_adminPage.htm
id=admin, pass=slapshot (for V3.0.77, V3.0.75)
5. Disable Provisioning
Menu--IP Network ---Provisioning Setting
6. Change username and password!

VOIP phones

2016-01-18T09:32:53Z

Robb:

VOIP phones

2016-01-18T09:31:34Z

Robb:

voip phones on the network

ip address/name/extension - description

100.64.64.31/5ud0r00m/7836 - that's us at sudoroom :)
100.64.64.32/door/3667 - frontdoor "pay"phone
100.64.64.33/ccl/225 - counter culture labs
100.64.64.34/pub/782 - public terminals

100.64.64.35/Voice_adminPage.htm
admin
omniphonix
http://innomedia.com/wp-content/uploads/2013/10/MTA-6328-2Re-DS.pdf
00:10:99:04:b7:ef

when you plug into its LAN port it gives you dhcp, you can go to http://192.168.251.1/Voice_adminPage.htm

http://www.dslreports.com/forum/r22145431-Unlock-I-think-I-bricked-my-Innomedia-MTA6328-2Re

1. Disconnect to WAN ( no internet).
2. Connect the gizmo via WAN to computer and login to it using user id
Â»192.168.1.xx/
id=user, pass=welcome
3. cut and paste the following link aninter desktop computer & giant_robot_arm serial host]]
| [[User:jake|jake]] d press enter to Restore factory default
Â»192.168.1.xx/restore2.ssi
4. power cycle the gizmo and login to admin link with factory default password.
Â»192.168.1.xx/Voice_adminPage.htm
id=admin, pass=slapshot (for V3.0.77, V3.0.75)
5. Disable Provisioning
Menu--IP Network ---Provisioning Setting
6. Change username and password!

Omniphwn

2016-01-18T09:16:35Z

Robb: Created page with "Omniphonix server running AsteriskNow @100.64.64.30 configured to be a VOIP intercom on our local network."

Omniphonix server running AsteriskNow @100.64.64.30 configured to be a VOIP intercom on our local network.

Network

2016-01-18T09:13:45Z

Robb: /* Addresses */

__NOTOC__
''For more information about sudo room's systems in general, see [[Systems Administration]]''

The sudo room '''network''' provides internal networking, internet access, wireless service, and some externally accessible devices or services. Information about the various devices in use and their configuration is available below.

== peoplesopen.net ==

If you wish to connect to the local mesh network [https://peoplesopen.net peoplesopen.net], then you can either connect using the peoplesopen.net wifi network, <s>or you can connect using ethernet through the D-Link DIR-601A router on the shelf next to the main switch</s>. Use DHCP to get a 10.0.0.0/8 IP address on the mesh network. The router will handle the meshing protocol for you and also provide you with normal Internet access.

== Routing ==
* [[Router/Config/Interface|Configure Interface Addresses]]
* [[Router/Config/PortForward|Open a port to the outside world]]

== Network Info ==
{|class="altop"
|
Internet access is via '''space.local''', a rackmount server running Ubuntu 14.04. If you follow the ethernet cable from the LMI modem through the patch panel, this is the first box connected to it.

=== External ===
==== Addresses ====

Our public IP is 142.254.26.9 aka '''room.sudoroom.org'''.

=== Internal ===
==== Ranges ====
* Internal subnet: 192.168.0.0/16
* DHCP range: 192.168.50.1 to 192.168.200.254

==== Addresses ====
{| class="wikitable blue_lines"
!style="width:120px;"| IPv4 Address
!style="width:110px;"| IPv6 Address
!style="width:110px;"| Assigned to
!Notes
!Who set it up?
|-
| 192.168.42.1 / 142.254.26.9
| fd4f:dc5d:8d1::1
| [[space.local|space.local / room.sudoroom.org]]
| Our gateway. Located in the sudo room server "room".
| maxb and somebody
|-
| 100.64.64.11
|
| omnidoor
| beaglebone black controlling the door
| juul and jake
|-
| 192.168.42.3
| No IPv6 address
| No host name
| Dell PowerConnect 5324 24 port gigabit switch
| juul
|-
| 192.168.42.4
| No IPv6 address
| No host name
| Dell PowerConnect 5448 48 port gigabit switch
| juul
|-
| 192.168.42.6
| fe80::219:b9ff:fe17:821c
| reproxy.local
| Load balancer and reverse proxy (not yet in commission).
| wrought
|-
| 192.168.42.7
| fe80::214:22ff:feb0:606
| shell.local
| Shell server (not yet in commission).
| wrought
|-
| 192.168.42.9
|
| BespokeBridge
| temporary wireless bridge to '''LaCommuneFront''' for public terminals near den in upstairs mezzanine
| [[User:Wrought|wrought]]
|-
| 192.168.42.10
|
| nodeconf.local
| The sudo mesh node configuration and build server
| Primarily [[User:Juul|juul]] and maxb
|-
| 192.168.42.12
|
|
| [[Brother_HL-2270DW| Brother HL-2270DW laser printer]] (wifi)
| [[User:Yar|yar]]
|-
| 100.64.64.20
|
| sudobot-3d.local
| [[sudobot-3d| 3d printer desktop computer & giant_robot_arm serial host]]
| [[User:jake|jake]] and [[User:Muxlux|muxlux]]
|-
| 100.64.64.27
|
|
| [[bigtv| raspberry pi connected to the big TV above skÃ¼lgaard]]
| [[User:jake|jake]]
|-
| 100.64.64.30
|
|
| [[omniphwn| omniphwn asterisk telephony server]]
| [[User:jake|jake]]
|-
| 100.64.64.31 through .60
|
|
| [[VOIP_phones| voip telephone extensions]]
| [[User:jake|jake]] and [[User:Muxlux|muxlux]]
|-
| 100.64.64.77
|
|
| [[pairprogramming| Dual-Monitor/Keyboard/Mouse Pair Programming Station]]
| [[User:jake|jake]]
|-
| 192.168.42.22
| Used only to build sudo mesh firmware and turned off when not in use.
| meshbuild.local
| [[Mesh/Build server|sudo mesh build server]]
| [[User:Juul|juul]]
|-
| 192.168.42.24
|
| ccl.local
| The Counter Culture Labs server. Located in the sudo room server rack.
| [[User:Juul|juul]]
|-
| 192.168.42.31
|
| hackomat.local
| The [[hack-o-mat]] vending machine.
| [[User:Juul|juul]]
|-
| 192.168.42.42
|
| omnidoor.local
| Dell laptop controlling the main Omni door access.
| [[User:Juul|juul]]
|-
| 192.168.42.47
|
| spartacus.local
| Dell desktop proxy server, apt server, for setting up new computers
| [[User:biged|biged]]
|-
! 192.168.42.50 - 192.168.42.254
|
!colspan=3| '''DHCP'''
|}

== Wireless Access Points ==
{| class="wikitable blue_lines"
!SSID
!Security
!Key
!MAC
!IP
!Channel
!Location
!Hardware
!Who set it up?
|-
|sudomesh
|open
|''n/a''
|Find Me
|192.168.42.18
|11
|zip-tied near server rack
|Ubiquiti Nanostation M2 Loco
|[[User:Juul|juul]]
|-
|Omni Ballroom
|open
|''n/a''
|Find Me
|192.168.42.19
|11
|Ballroom near stage
|Ubiquiti Picostation 2
|[[User:Maxb|maxb]]
}

[[Category:Network]]

Network

2016-01-18T09:12:59Z

Robb: /* Addresses */

__NOTOC__
''For more information about sudo room's systems in general, see [[Systems Administration]]''

The sudo room '''network''' provides internal networking, internet access, wireless service, and some externally accessible devices or services. Information about the various devices in use and their configuration is available below.

== peoplesopen.net ==

If you wish to connect to the local mesh network [https://peoplesopen.net peoplesopen.net], then you can either connect using the peoplesopen.net wifi network, <s>or you can connect using ethernet through the D-Link DIR-601A router on the shelf next to the main switch</s>. Use DHCP to get a 10.0.0.0/8 IP address on the mesh network. The router will handle the meshing protocol for you and also provide you with normal Internet access.

== Routing ==
* [[Router/Config/Interface|Configure Interface Addresses]]
* [[Router/Config/PortForward|Open a port to the outside world]]

== Network Info ==
{|class="altop"
|
Internet access is via '''space.local''', a rackmount server running Ubuntu 14.04. If you follow the ethernet cable from the LMI modem through the patch panel, this is the first box connected to it.

=== External ===
==== Addresses ====

Our public IP is 142.254.26.9 aka '''room.sudoroom.org'''.

=== Internal ===
==== Ranges ====
* Internal subnet: 192.168.0.0/16
* DHCP range: 192.168.50.1 to 192.168.200.254

==== Addresses ====
{| class="wikitable blue_lines"
!style="width:120px;"| IPv4 Address
!style="width:110px;"| IPv6 Address
!style="width:110px;"| Assigned to
!Notes
!Who set it up?
|-
| 192.168.42.1 / 142.254.26.9
| fd4f:dc5d:8d1::1
| [[space.local|space.local / room.sudoroom.org]]
| Our gateway. Located in the sudo room server "room".
| maxb and somebody
|-
| 100.64.64.11
|
| omnidoor
| beaglebone black controlling the door
| juul and jake
|-
| 192.168.42.3
| No IPv6 address
| No host name
| Dell PowerConnect 5324 24 port gigabit switch
| juul
|-
| 192.168.42.4
| No IPv6 address
| No host name
| Dell PowerConnect 5448 48 port gigabit switch
| juul
|-
| 192.168.42.6
| fe80::219:b9ff:fe17:821c
| reproxy.local
| Load balancer and reverse proxy (not yet in commission).
| wrought
|-
| 192.168.42.7
| fe80::214:22ff:feb0:606
| shell.local
| Shell server (not yet in commission).
| wrought
|-
| 192.168.42.9
|
| BespokeBridge
| temporary wireless bridge to '''LaCommuneFront''' for public terminals near den in upstairs mezzanine
| [[User:Wrought|wrought]]
|-
| 192.168.42.10
|
| nodeconf.local
| The sudo mesh node configuration and build server
| Primarily [[User:Juul|juul]] and maxb
|-
| 192.168.42.12
|
|
| [[Brother_HL-2270DW| Brother HL-2270DW laser printer]] (wifi)
| [[User:Yar|yar]]
|-
| 100.64.64.20
|
| sudobot-3d.local
| [[sudobot-3d| 3d printer desktop computer & giant_robot_arm serial host]]
| [[User:jake|jake]] [[User:Muxlux|muxlux]]
|-
| 100.64.64.27
|
|
| [[bigtv| raspberry pi connected to the big TV above skÃ¼lgaard]]
| [[User:jake|jake]]
|-
| 100.64.64.30
|
|
| [[omniphwn| omniphwn asterisk telephony server]]
| [[User:jake|jake]]
|-
| 100.64.64.31 through .60
|
|
| [[VOIP_phones| voip telephone extensions]]
| [[User:jake|jake]] [[User:Muxlux|muxlux]]
|-
| 100.64.64.77
|
|
| [[pairprogramming| Dual-Monitor/Keyboard/Mouse Pair Programming Station]]
| [[User:jake|jake]]
|-
| 192.168.42.22
| Used only to build sudo mesh firmware and turned off when not in use.
| meshbuild.local
| [[Mesh/Build server|sudo mesh build server]]
| [[User:Juul|juul]]
|-
| 192.168.42.24
|
| ccl.local
| The Counter Culture Labs server. Located in the sudo room server rack.
| [[User:Juul|juul]]
|-
| 192.168.42.31
|
| hackomat.local
| The [[hack-o-mat]] vending machine.
| [[User:Juul|juul]]
|-
| 192.168.42.42
|
| omnidoor.local
| Dell laptop controlling the main Omni door access.
| [[User:Juul|juul]]
|-
| 192.168.42.47
|
| spartacus.local
| Dell desktop proxy server, apt server, for setting up new computers
| [[User:biged|biged]]
|-
! 192.168.42.50 - 192.168.42.254
|
!colspan=3| '''DHCP'''
|}

== Wireless Access Points ==
{| class="wikitable blue_lines"
!SSID
!Security
!Key
!MAC
!IP
!Channel
!Location
!Hardware
!Who set it up?
|-
|sudomesh
|open
|''n/a''
|Find Me
|192.168.42.18
|11
|zip-tied near server rack
|Ubiquiti Nanostation M2 Loco
|[[User:Juul|juul]]
|-
|Omni Ballroom
|open
|''n/a''
|Find Me
|192.168.42.19
|11
|Ballroom near stage
|Ubiquiti Picostation 2
|[[User:Maxb|maxb]]
}

[[Category:Network]]

Network

2016-01-18T09:12:33Z

Robb: /* Addresses */

__NOTOC__
''For more information about sudo room's systems in general, see [[Systems Administration]]''

The sudo room '''network''' provides internal networking, internet access, wireless service, and some externally accessible devices or services. Information about the various devices in use and their configuration is available below.

== peoplesopen.net ==

If you wish to connect to the local mesh network [https://peoplesopen.net peoplesopen.net], then you can either connect using the peoplesopen.net wifi network, <s>or you can connect using ethernet through the D-Link DIR-601A router on the shelf next to the main switch</s>. Use DHCP to get a 10.0.0.0/8 IP address on the mesh network. The router will handle the meshing protocol for you and also provide you with normal Internet access.

== Routing ==
* [[Router/Config/Interface|Configure Interface Addresses]]
* [[Router/Config/PortForward|Open a port to the outside world]]

== Network Info ==
{|class="altop"
|
Internet access is via '''space.local''', a rackmount server running Ubuntu 14.04. If you follow the ethernet cable from the LMI modem through the patch panel, this is the first box connected to it.

=== External ===
==== Addresses ====

Our public IP is 142.254.26.9 aka '''room.sudoroom.org'''.

=== Internal ===
==== Ranges ====
* Internal subnet: 192.168.0.0/16
* DHCP range: 192.168.50.1 to 192.168.200.254

==== Addresses ====
{| class="wikitable blue_lines"
!style="width:120px;"| IPv4 Address
!style="width:110px;"| IPv6 Address
!style="width:110px;"| Assigned to
!Notes
!Who set it up?
|-
| 192.168.42.1 / 142.254.26.9
| fd4f:dc5d:8d1::1
| [[space.local|space.local / room.sudoroom.org]]
| Our gateway. Located in the sudo room server "room".
| maxb and somebody
|-
| 100.64.64.11
|
| omnidoor
| beaglebone black controlling the door
| juul and jake
|-
| 192.168.42.3
| No IPv6 address
| No host name
| Dell PowerConnect 5324 24 port gigabit switch
| juul
|-
| 192.168.42.4
| No IPv6 address
| No host name
| Dell PowerConnect 5448 48 port gigabit switch
| juul
|-
| 192.168.42.6
| fe80::219:b9ff:fe17:821c
| reproxy.local
| Load balancer and reverse proxy (not yet in commission).
| wrought
|-
| 192.168.42.7
| fe80::214:22ff:feb0:606
| shell.local
| Shell server (not yet in commission).
| wrought
|-
| 192.168.42.9
|
| BespokeBridge
| temporary wireless bridge to '''LaCommuneFront''' for public terminals near den in upstairs mezzanine
| [[User:Wrought|wrought]]
|-
| 192.168.42.10
|
| nodeconf.local
| The sudo mesh node configuration and build server
| Primarily [[User:Juul|juul]] and maxb
|-
| 192.168.42.12
|
|
| [[Brother_HL-2270DW| Brother HL-2270DW laser printer]] (wifi)
| [[User:Yar|yar]]
|-
| 100.64.64.20
|
| sudobot-3d.local
| [[sudobot-3d| 3d printer desktop computer & giant_robot_arm serial host]]
| [[User:jake|jake]] [[User:Muxlux|Muxlux]]
|-
| 100.64.64.27
|
|
| [[bigtv| raspberry pi connected to the big TV above skÃ¼lgaard]]
| [[User:jake|jake]]
|-
| 100.64.64.30
|
|
| [[omniphwn| omniphwn asterisk telephony server]]
| [[User:jake|jake]]
|-
| 100.64.64.31 through .60
|
|
| [[VOIP_phones| voip telephone extensions]]
| [[User:jake|jake]] [[User:Muxlux|muxlux]]
|-
| 100.64.64.77
|
|
| [[pairprogramming| Dual-Monitor/Keyboard/Mouse Pair Programming Station]]
| [[User:jake|jake]]
|-
| 192.168.42.22
| Used only to build sudo mesh firmware and turned off when not in use.
| meshbuild.local
| [[Mesh/Build server|sudo mesh build server]]
| [[User:Juul|juul]]
|-
| 192.168.42.24
|
| ccl.local
| The Counter Culture Labs server. Located in the sudo room server rack.
| [[User:Juul|juul]]
|-
| 192.168.42.31
|
| hackomat.local
| The [[hack-o-mat]] vending machine.
| [[User:Juul|juul]]
|-
| 192.168.42.42
|
| omnidoor.local
| Dell laptop controlling the main Omni door access.
| [[User:Juul|juul]]
|-
| 192.168.42.47
|
| spartacus.local
| Dell desktop proxy server, apt server, for setting up new computers
| [[User:biged|biged]]
|-
! 192.168.42.50 - 192.168.42.254
|
!colspan=3| '''DHCP'''
|}

== Wireless Access Points ==
{| class="wikitable blue_lines"
!SSID
!Security
!Key
!MAC
!IP
!Channel
!Location
!Hardware
!Who set it up?
|-
|sudomesh
|open
|''n/a''
|Find Me
|192.168.42.18
|11
|zip-tied near server rack
|Ubiquiti Nanostation M2 Loco
|[[User:Juul|juul]]
|-
|Omni Ballroom
|open
|''n/a''
|Find Me
|192.168.42.19
|11
|Ballroom near stage
|Ubiquiti Picostation 2
|[[User:Maxb|maxb]]
}

[[Category:Network]]

Network

2016-01-18T09:10:54Z

Robb: /* Addresses */

__NOTOC__
''For more information about sudo room's systems in general, see [[Systems Administration]]''

The sudo room '''network''' provides internal networking, internet access, wireless service, and some externally accessible devices or services. Information about the various devices in use and their configuration is available below.

== peoplesopen.net ==

If you wish to connect to the local mesh network [https://peoplesopen.net peoplesopen.net], then you can either connect using the peoplesopen.net wifi network, <s>or you can connect using ethernet through the D-Link DIR-601A router on the shelf next to the main switch</s>. Use DHCP to get a 10.0.0.0/8 IP address on the mesh network. The router will handle the meshing protocol for you and also provide you with normal Internet access.

== Routing ==
* [[Router/Config/Interface|Configure Interface Addresses]]
* [[Router/Config/PortForward|Open a port to the outside world]]

== Network Info ==
{|class="altop"
|
Internet access is via '''space.local''', a rackmount server running Ubuntu 14.04. If you follow the ethernet cable from the LMI modem through the patch panel, this is the first box connected to it.

=== External ===
==== Addresses ====

Our public IP is 142.254.26.9 aka '''room.sudoroom.org'''.

=== Internal ===
==== Ranges ====
* Internal subnet: 192.168.0.0/16
* DHCP range: 192.168.50.1 to 192.168.200.254

==== Addresses ====
{| class="wikitable blue_lines"
!style="width:120px;"| IPv4 Address
!style="width:110px;"| IPv6 Address
!style="width:110px;"| Assigned to
!Notes
!Who set it up?
|-
| 192.168.42.1 / 142.254.26.9
| fd4f:dc5d:8d1::1
| [[space.local|space.local / room.sudoroom.org]]
| Our gateway. Located in the sudo room server "room".
| maxb and somebody
|-
| 100.64.64.11
|
| omnidoor
| beaglebone black controlling the door
| juul and jake
|-
| 192.168.42.3
| No IPv6 address
| No host name
| Dell PowerConnect 5324 24 port gigabit switch
| juul
|-
| 192.168.42.4
| No IPv6 address
| No host name
| Dell PowerConnect 5448 48 port gigabit switch
| juul
|-
| 192.168.42.6
| fe80::219:b9ff:fe17:821c
| reproxy.local
| Load balancer and reverse proxy (not yet in commission).
| wrought
|-
| 192.168.42.7
| fe80::214:22ff:feb0:606
| shell.local
| Shell server (not yet in commission).
| wrought
|-
| 192.168.42.9
|
| BespokeBridge
| temporary wireless bridge to '''LaCommuneFront''' for public terminals near den in upstairs mezzanine
| [[User:Wrought|wrought]]
|-
| 192.168.42.10
|
| nodeconf.local
| The sudo mesh node configuration and build server
| Primarily [[User:Juul|juul]] and maxb
|-
| 192.168.42.12
|
|
| [[Brother_HL-2270DW| Brother HL-2270DW laser printer]] (wifi)
| [[User:Yar|yar]]
|-
| 100.64.64.20
|
| sudobot-3d.local
| [[sudobot-3d| 3d printer desktop computer & giant_robot_arm serial host]]
| [[User:jake|jake]] [[User:Muxlux|Muxlux]]
|-
| 100.64.64.27
|
|
| [[bigtv| raspberry pi connected to the big TV above skÃ¼lgaard]]
| [[User:jake|jake]]
|-
| 100.64.64.30
|
|
| [[omniphwn| omniphwn asterisk telephony server]]
| [[User:jake|jake]]
|-
| 100.64.64.31 through .60
|
|
| [[VOIP_phones| voip telephone extensions]]
| [[User:jake|jake]] [[User:Muxlux|Muxlux]]
|-
| 100.64.64.77
|
|
| [[pairprogramming| Dual-Monitor/Keyboard/Mouse Pair Programming Station]]
| [[User:jake|jake]]
|-
| 192.168.42.22
| Used only to build sudo mesh firmware and turned off when not in use.
| meshbuild.local
| [[Mesh/Build server|sudo mesh build server]]
| [[User:Juul|juul]]
|-
| 192.168.42.24
|
| ccl.local
| The Counter Culture Labs server. Located in the sudo room server rack.
| [[User:Juul|juul]]
|-
| 192.168.42.31
|
| hackomat.local
| The [[hack-o-mat]] vending machine.
| [[User:Juul|juul]]
|-
| 192.168.42.42
|
| omnidoor.local
| Dell laptop controlling the main Omni door access.
| [[User:Juul|juul]]
|-
| 192.168.42.47
|
| spartacus.local
| Dell desktop proxy server, apt server, for setting up new computers
| [[User:biged|biged]]
|-
! 192.168.42.50 - 192.168.42.254
|
!colspan=3| '''DHCP'''
|}

== Wireless Access Points ==
{| class="wikitable blue_lines"
!SSID
!Security
!Key
!MAC
!IP
!Channel
!Location
!Hardware
!Who set it up?
|-
|sudomesh
|open
|''n/a''
|Find Me
|192.168.42.18
|11
|zip-tied near server rack
|Ubiquiti Nanostation M2 Loco
|[[User:Juul|juul]]
|-
|Omni Ballroom
|open
|''n/a''
|Find Me
|192.168.42.19
|11
|Ballroom near stage
|Ubiquiti Picostation 2
|[[User:Maxb|maxb]]
}

[[Category:Network]]