2020-09-14T20:26:13Z

Stephen304:

[[Category:Devices]]
[[Category:Ubiquiti]]
[[File:Ubnt-ns-5ac-loco.png|thumb|NanoStation 5AC Loco]]

The NanoStation 5AC Loco is a directional, weather resistant, PoE powered radio with a beam width of 90 degrees and a secondary omnidirectional radio. This makes it useful for simultaneously meshing on one radio while providing an access point for client devices on the other.

{{ Warning| This is a PoE device. Never connect your computer directly to the PoE injector's red port!!!}}

{{Note| The Nanostation's architecture is '''MIPS 24KC.'''}}

{{ Warning| As of January 1, 2020, brand new Nanostations do not support downgrading the Ubiquiti AirOS firmware. (Even with the patch.) Instead, you must [[#Flash using serial header access|Flash using serial header access]]}}

== Files ==
[https://dl.ubnt.com/firmwares/XC-fw/v8.5.0/WA.v8.5.0.36727.180118.1314.bin Stock Firmware v8.5.0.36727]

[https://github.com/MassMesh/meta-imagebuilder-artifacts/raw/master/massmesh/meshradio/ubnt_nanostation-ac-loco/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin MassMesh Firmware (Factory) (Latest)]

[https://github.com/MassMesh/meta-imagebuilder-artifacts/raw/master/massmesh/meshradio/ubnt_nanostation-ac-loco/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-sysupgrade.bin MassMesh Firmware (Sysupgrade) (Latest)]

== Flashing ==

=== From OpenWrt ===
{{Note|Mass Mesh mesh radios have a static IP of 192.168.2.1. To access the admin UI, set your computer's ip/netmask to 192.168.2.10/24, then browse to http://192.168.2.1/ in your favorite web browser.}}
# Download the latest [https://github.com/MassMesh/meta-imagebuilder-artifacts/raw/master/massmesh/meshradio/ubnt_nanostation-ac-loco/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-sysupgrade.bin MassMesh sysupgrade firmware.]
# Connect to the Nanostation and enter its IP address into your favorite web browser.
## If you are using another version of OpenWrt, please refer to its documentation for details about its IP address.
# Navigate to System → Backup / Flash Firmware → Actions: '''Flash new firmware image.'''
# Choose the sysupgrade file previously downloaded and click '''Flash'''
# Wait for the device to complete and reboot (This can take up to 5 minutes.)

=== From Stock Firmware (Ubiquiti AirOS)===

==== Downgrade Ubiquiti AirOS via Web UI ====

# Download the [https://dl.ubnt.com/firmwares/XC-fw/v8.5.0/WA.v8.5.0.36727.180118.1314.bin Stock Firmware Image v8.5.0.36727].
# Power on the Nanostation via a PoE injector. (This is the **red** ethernet port on your injector.)
# Connect the LAN side of the PoE injector to a computer.
# Assign a static IP/netmask of <code>192.168.1.25/24</code> to the computer
## <code>sudo ip addr add 192.168.1.25/24 dev eth0</code>
# Use a browser to visit http://192.168.1.20/
# Login using the set password or default credentials <code>ubnt / ubnt</code>
# Navigate to settings and downgrade the stock firmware to v8.5.0.36727 using the downloaded image file

{{Note|Newer versions of the NanoStation 5AC Loco block downgrading the firmware to 8.5.0. If you encounter this error, you will need to open up the radio and use the [[#Downgrade Ubiquiti AirOS With An External Programmer|Pomona clip method]] or the [[#Flash using serial header access|serial flashing method]].}}

==== Downgrade Ubiquiti AirOS via TFTP ====

<pre>
wget https://dl.ubnt.com/firmwares/XC-fw/v8.5.0/WA.v8.5.0.36727.180118.1314.bin
cp https://dl.ubnt.com/firmwares/XC-fw/v8.5.0/WA.v8.5.0.36727.180118.1314.bin firmware.bin
sudo apt install tftp
tftp
tftp> connect 192.168.1.20
tftp> rexmt 1
tftp> timeout 60
tftp> binary
tftp> put firmware.bin
</pre>

No re-boot is necessary. You should be able to access the router at 192.168.1.20 after a couple of minutes.

{{Note|Newer versions of the NanoStation 5AC Loco block downgrading the firmware to 8.5.0. If you encounter an "Initialization Error" after flashing, you will need to open up the radio and use the [[#Downgrade Ubiquiti AirOS With An External Programmer|Pomona clip method]] or the [[#Flash using serial header access|serial flashing method]].}}

==== Install The Mass Mesh OpenWrt Image ====

{{ Note| Additional instructions are available [https://openwrt.org/toh/ubiquiti/ubiquiti_nanostation_ac_loco on OpenWrt's website]. The "factory" image should be chosen for this step.}}
# Download the latest Mass Mesh firmware [https://github.com/MassMesh/meta-imagebuilder-artifacts/raw/master/massmesh/meshradio/ubnt_nanostation-ac-loco/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin here].
# Copy the firmware onto the nanostation. (We like to put it in the <code>/tmp/</code> directory.)
# Open a secure shell on the Nanostation. <code>ssh ubnt@192.168.1.20</code>
# Patch the fwupdate.real binary a la the instructions [https://openwrt.org/toh/ubiquiti/ubiquiti_nanostation_ac_loco here.]
# <code>/tmp/fwupdate.real -m /tmp/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin</code>

== Advanced Flashing Techniques ==

=== Downgrade Ubiquiti AirOS With An External Programmer===

When your nanostation is bricked, or if the stock firmware won't let you flash our custom firmware, you can use the '''In-System Programming''' (ISP) technique to reflash the device (see also the [https://www.flashrom.org/ISP Flashrom wiki]. You're going to need:

# a Pomona 5252 test clip (https://www.digikey.com/product-detail/en/pomona-electronics/5252/501-2059-ND/745103), ~$16
# a raspberry pi (e.g. a zero w) ~$10
# some header pins and prototyping wires to connect everything

The Nanostation has a Macronix MX25L12835F rom chip ([https://www.macronix.com/Lists/Datasheet/Attachments/7397/MX25L12835F,%203V,%20128Mb,%20v1.6.pdf datasheet]), which is an SPI chip with 16 connectors good for 128 Mbit of storage.

We can use [https://flashrom.org Flashrom] running on a raspberry pi to read and write that chip, if we hook up the Pomona 5252 test clip to the MX25L12835F and connect it to the correct [https://pinout.xyz/pinout/spi SPI pins] on the pi:

[[File:raspberry-pi-pinout.png|inline|raspberry pi GPIO pinout]]

(note: the SPI1 CE0/CE1 pins are not labeled on this image)

==== Pinouts (please proceed with caution!) ====

The Raspberry Pi has 2 SPI interfaces, SPI0 and SPI1.

On the Raspberry Pi boot partition, make sure to update config.txt and uncomment the line that reads

dtparam=spi=on

After a reboot, you should see the spi device files:

root@raspberrypi:/home/pi# ls -laF /dev/spidev0.*
crw-rw---- 1 root spi 153, 0 Jan 7 01:44 /dev/spidev0.0
crw-rw---- 1 root spi 153, 1 Jan 7 01:44 /dev/spidev0.1

Now connect the Raspberry Pi to the Pomona clip. Choose either SPI0 or SPI1. We're going to leave the VCC pin on the flash chip disconnected. We are however going to connect a few other pins to our 3.3V source from the raspberry pi, to pull them up.

{| class="wikitable"
|-
!colspan="2"|RPi SPI0!!colspan="2"|RPi SPI1!!colspan="2"|Pomona Clip!!Notes!!Color in picture below
|-
|17||3.3V
|17||3.3V
|1||SIO3
|''we do not use this pin, so we pull it up''
|red
|-
|17||3.3V
|17||3.3V
|9||WP#SIO2
|''put the chip in read/write mode''
|red
|-
|19||SPI0 MOSI
|38||SPI1 MOSI
|15||SI
|
|blue
|-
|21||SPI0 MISO
|35||SPI1 MISO
|8||SO
|
|orange
|-
|23||SPI0 SCLK
|40||SPI1 SCLK
|16||SCLK
|
|green
|-
|25||GND
|25||GND
|10||GND
|
|brown
|-
|24||SPI0 CE0
|12||SPI1 CE0
|7||CS
|
|yellow
|}

[[File:20200127-raspberry-pi-zero-w-with-pomona-clip.jpg|thumb|A Raspberry Pi Zero W with wires connected to the SPI0 pins. There is an unused 3.3V wire visible.]]

==== Reading the chip with flashrom ====

Once the pomona is connected to the raspberry pi, make sure the nanostation is disconnected from power/ethernet. Then clip on the pomona.

Flashrom on the raspberry pi requires us to specify the spi speed for the operation. We also need to specify the exact rom chip model, because there are two models that match:

$ flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=30000 -r proprietary.rom
flashrom on Linux 4.19.75+ (armv6l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Macronix flash chip "MX25L12805D" (16384 kB, SPI) on linux_spi.
Found Macronix flash chip "MX25L12835F/MX25L12845E/MX25L12865E" (16384 kB, SPI) on linux_spi.
Multiple flash chip definitions match the detected chip(s): "MX25L12805D", "MX25L12835F/MX25L12845E/MX25L12865E"
Please specify which chip definition to use with the -c <chipname> option.

So here's the final command to read out the chip:

$ flashrom -c "MX25L12835F/MX25L12845E/MX25L12865E" -p linux_spi:dev=/dev/spidev0.0,spispeed=30000 -r proprietary.rom
flashrom on Linux 4.19.75+ (armv6l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Macronix flash chip "MX25L12835F/MX25L12845E/MX25L12865E" (16384 kB, SPI) on linux_spi.
Reading flash... done.

It's easy to verify that if the reading worked. If you were reading out the original firmware, binwalk would print something like this:

$ binwalk proprietary.rom

DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
115152 0x1C1D0 Certificate in DER format (x509 v3), header length: 4, sequence length: 64
142896 0x22E30 U-Boot version string, "U-Boot 1.1.4-s1100 (Sep 5 2018 - 17:53:00)"
143184 0x22F50 CRC32 polynomial table, big endian
224396 0x36C8C CRC32 polynomial table, big endian
226924 0x3766C Ubiquiti end header, header size: 12 bytes, cumulative ~CRC32: 0x454E442E
231856 0x389B0 Ubiquiti partition header, header size: 56 bytes, name: "PARTkernel", base address: 0x00000001, data size: -2147475456 bytes
231920 0x389F0 uImage header, header size: 64 bytes, header CRC: 0xE75790E0, created: 2018-11-13 14:36:59, image size: 998847 bytes, Data
Address: 0x80002000, Entry Point: 0x80002000, data CRC: 0xAAECA664, OS: Linux, CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: "MIPS Ubiquiti Linux-2.6.32.68"
327680 0x50000 uImage header, header size: 64 bytes, header CRC: 0x22425505, created: 2019-02-13 09:09:52, image size: 990770 bytes, Data Address: 0x80002000, Entry Point: 0x80002000, data CRC: 0x8F3B71D3, OS: Linux, CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: "MIPS Ubiquiti Linux-2.6.32.68"
327744 0x50040 LZMA compressed data, properties: 0x5D, dictionary size: 8388608 bytes, uncompressed size: 2836596 bytes
1318514 0x141E72 Ubiquiti partition header, header size: 56 bytes, name: "PARTrootfs", base address: 0x00000002, data size: 0 bytes
1318578 0x141EB2 Squashfs filesystem, little endian, version 4.0, compression:lzma, size: 7203018 bytes, 956 inodes, blocksize: 262144 bytes, created: 2019-02-13 09:09:54

Useful resources:
* [https://www.flashrom.org/RaspberryPi Flashrom page on using the Raspberry Pi as a flashing tool]

==== Writing to the chip with flashrom ====

pi@raspberrypi:~ $ flashrom -c "MX25L12835F/MX25L12845E/MX25L12865E" -p linux_spi:dev=/dev/spidev0.0,spispeed=30000 -w read1-10000-openwrt.bin
flashrom on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Macronix flash chip "MX25L12835F/MX25L12845E/MX25L12865E" (16384 kB, SPI) on linux_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.

=== Flash using serial header access ===
Direct serial access allows temporarily running OpenWRT in memory and using the temporary environment to flash a full image to the radio's memory.

[[File:Ubnt_ns5acl_serial.jpg|thumb|Click to enlarge pinout]]
# Using your thumb or a small tool, push the tab in the slot located on the lower rear of the radio and slide the bottom half out of the enclosure
# Looking at the rear of the board (where all the components are on the opposite side as the antenna), locate the serial headers on the middle left side of the board
# Solder at least the top 3 pins shown in the picture. The pins from left to right (starting with the square shaped pad that is unpopulated in the image) are 3.3V, RX, TX, and GND. 3.3V is not needed here
# Connect GND on the board to GND on your FTDI adapter, TX on the board to RX on the FTDI adapter, and RX on the board to TX on the FTDI adapter
# Make sure your FTDI adapter is in 3.3V mode and attached to your computer, then open the serial port on your computer (ex. <code>minicom -D /dev/ttyUSB0</code>). Use 115200 8N1 in your terminal settings.
# Connect the NanoStation and press enter in the console when it says <code>Hit any key to stop autoboot:</code>. You should be left at a <code>ar7240> </code> prompt.
# Connect your laptop to the LAN port of the PoE injector powering the NanoStation and assign a static IP of <code>192.168.1.254</code>
# Install a TFTP server and place [https://downloads.openwrt.org/releases/19.07.0/targets/ath79/generic/openwrt-19.07.0-ath79-generic-ubnt_nanostation-ac-loco-initramfs-kernel.bin openwrt-19.07.0-ath79-generic-ubnt_nanostation-ac-loco-initramfs-kernel.bin] in the root folder of the TFTP server (<code>/srv/tftp</code> for tftp-hpa on Arch).
# Rename the initramfs-kernel.bin file to <code>1401A8C0.img</code> and ensure the tftp server / service is started
# Run <code>tftpboot</code> in the serial console and wait for it to complete
# Run <code>bootm</code> in the serial console to boot the initramfs
# Once OpenWRT has booted, you can press Enter to enable shell access
# Ensure you have an IP address in the 192.168.1.x subnet and use scp to transfer the sysupgrade firmware you wish to flash
# Flash the full firmware to the radio's storage using <code>mtd -r write /tmp/sysupgrade.bin firmware</code>, replacing <code>sysupgrade.bin</code> with the full filename of the firmware you are flashing

== Condensed Command-list ==
=== Flash The Stock Ubiquiti Firmware via TFTP ===
<pre>
wget https://dl.ubnt.com/firmwares/XC-fw/v8.5.0/WA.v8.5.0.36727.180118.1314.bin
cp https://dl.ubnt.com/firmwares/XC-fw/v8.5.0/WA.v8.5.0.36727.180118.1314.bin firmware.bin
sudo apt install tftp
tftp
tftp> connect 192.168.1.20
tftp> rexmt 1
tftp> timeout 60
tftp> binary
tftp> put firmware.bin
</pre>

No re-boot is necessary. You should be able to access the router at 192.168.1.20 after a couple of minutes.

=== Flash The Mass Mesh Firmware ===
<pre>
wget https://github.com/MassMesh/meta-imagebuilder-artifacts/raw/master/massmesh/meshradio/ubnt_nanostation-ac-loco/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin
scp openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin ubnt@192.168.1.20:/tmp
ssh ubnt@192.168.1.20
hexdump -Cv /bin/ubntbox | sed 's/14 40 fe fe/00 00 00 00/g' | hexdump -R > /tmp/fwupdate.real
chmod +x /tmp/fwupdate.real
/tmp/fwupdate.real -m /tmp/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin
</pre>

Public Gateways

2020-09-14T03:42:24Z

Stephen304:

Public Gateways

2020-09-14T03:37:58Z

Stephen304:

2020-09-13T07:49:09Z

Stephen304: /* Tests */

== EspressoBin v5 ==
=== No Yggdrasil ===
<nowiki>Connecting to host 10.0.0.1, port 5201
[ 5] local 10.0.0.106 port 58198 connected to 10.0.0.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 49.2 MBytes 413 Mbits/sec 27 532 KBytes
[ 5] 1.00-2.00 sec 44.8 MBytes 376 Mbits/sec 0 592 KBytes
[ 5] 2.00-3.00 sec 44.8 MBytes 376 Mbits/sec 0 643 KBytes
[ 5] 3.00-4.00 sec 44.9 MBytes 376 Mbits/sec 1 519 KBytes
[ 5] 4.00-5.00 sec 46.1 MBytes 387 Mbits/sec 0 581 KBytes
[ 5] 5.00-6.00 sec 44.8 MBytes 376 Mbits/sec 0 639 KBytes
[ 5] 6.00-7.00 sec 46.1 MBytes 387 Mbits/sec 1 516 KBytes
[ 5] 7.00-8.00 sec 43.6 MBytes 366 Mbits/sec 374 346 KBytes
[ 5] 8.00-9.00 sec 44.9 MBytes 377 Mbits/sec 0 434 KBytes
[ 5] 9.00-10.00 sec 46.1 MBytes 387 Mbits/sec 0 509 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 455 MBytes 382 Mbits/sec 403 sender
[ 5] 0.00-10.05 sec 452 MBytes 377 Mbits/sec receiver

iperf Done.</nowiki>
=== Yggdrasil ===
<nowiki>Connecting to host 201:f06b:1827:4e45:90fa:554e:ace5:27c7, port 5201
[ 5] local 201:28ab:ee79:77d4:192e:1366:8b79:4980 port 33776 connected to 201:f06b:1827:4e45:90fa:554e:ace5:27c7 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 17.4 MBytes 146 Mbits/sec 26 1.50 MBytes
[ 5] 1.00-2.00 sec 16.2 MBytes 136 Mbits/sec 20 1.31 MBytes
[ 5] 2.00-3.00 sec 15.0 MBytes 126 Mbits/sec 56 959 KBytes
[ 5] 3.00-4.00 sec 13.8 MBytes 115 Mbits/sec 31 767 KBytes
[ 5] 4.00-5.00 sec 13.8 MBytes 115 Mbits/sec 20 831 KBytes
[ 5] 5.00-6.00 sec 15.0 MBytes 126 Mbits/sec 2 1.25 MBytes
[ 5] 6.00-7.00 sec 17.5 MBytes 147 Mbits/sec 23 1.37 MBytes
[ 5] 7.00-8.00 sec 17.5 MBytes 147 Mbits/sec 1 1.62 MBytes
[ 5] 8.00-9.00 sec 15.0 MBytes 126 Mbits/sec 5 1.62 MBytes
[ 5] 9.00-10.00 sec 17.5 MBytes 147 Mbits/sec 6 1.62 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 159 MBytes 133 Mbits/sec 190 sender
[ 5] 0.00-10.09 sec 157 MBytes 130 Mbits/sec receiver

iperf Done.</nowiki>

== Raspberry Pi 3B+ ==
=== Yggdrasil ===
<nowiki>[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.41 sec 37.3 MBytes 30.1 Mbits/sec receiver
[ 8] 0.00-10.41 sec 36.6 MBytes 29.5 Mbits/sec receiver
[ 10] 0.00-10.41 sec 36.6 MBytes 29.5 Mbits/sec receiver
[ 12] 0.00-10.41 sec 38.0 MBytes 30.6 Mbits/sec receiver
[SUM] 0.00-10.41 sec 149 MBytes 120 Mbits/sec receiver</nowiki>

== Tests ==

=== VPS Benchmark ===
Environment: Laptop, Rpi4, DO Droplet, mullvad

Fully wired, rpi connected via autoygg to droplet, which routes traffic out through mullvad

{| class="wikitable"
|+ Benchmarked VPS
! Size !! Download !! Upload !! Notes
|-
| $5 Basic || 55 Mbit/s || 30 Mbit/s || Tested steam downloads as well as speedtest.net. Maxed out CPU
|-
| $15 Basic || 53 Mbit/s || 47 Mbit/s || Tested speedtest.net, CPU at ~50%
|-
| $40 Basic || 65 Mbit/s || 55 Mbit/s || Tested speedtest.net, low resource utilization overall
|}

Benchmarks

2020-09-13T07:44:18Z

Stephen304: /* VPS Benchmark */

Benchmarks

2020-09-13T07:42:38Z

Stephen304: /* VPS Benchmark */

== EspressoBin v5 ==
=== No Yggdrasil ===
<nowiki>Connecting to host 10.0.0.1, port 5201
[ 5] local 10.0.0.106 port 58198 connected to 10.0.0.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 49.2 MBytes 413 Mbits/sec 27 532 KBytes
[ 5] 1.00-2.00 sec 44.8 MBytes 376 Mbits/sec 0 592 KBytes
[ 5] 2.00-3.00 sec 44.8 MBytes 376 Mbits/sec 0 643 KBytes
[ 5] 3.00-4.00 sec 44.9 MBytes 376 Mbits/sec 1 519 KBytes
[ 5] 4.00-5.00 sec 46.1 MBytes 387 Mbits/sec 0 581 KBytes
[ 5] 5.00-6.00 sec 44.8 MBytes 376 Mbits/sec 0 639 KBytes
[ 5] 6.00-7.00 sec 46.1 MBytes 387 Mbits/sec 1 516 KBytes
[ 5] 7.00-8.00 sec 43.6 MBytes 366 Mbits/sec 374 346 KBytes
[ 5] 8.00-9.00 sec 44.9 MBytes 377 Mbits/sec 0 434 KBytes
[ 5] 9.00-10.00 sec 46.1 MBytes 387 Mbits/sec 0 509 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 455 MBytes 382 Mbits/sec 403 sender
[ 5] 0.00-10.05 sec 452 MBytes 377 Mbits/sec receiver

iperf Done.</nowiki>
=== Yggdrasil ===
<nowiki>Connecting to host 201:f06b:1827:4e45:90fa:554e:ace5:27c7, port 5201
[ 5] local 201:28ab:ee79:77d4:192e:1366:8b79:4980 port 33776 connected to 201:f06b:1827:4e45:90fa:554e:ace5:27c7 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 17.4 MBytes 146 Mbits/sec 26 1.50 MBytes
[ 5] 1.00-2.00 sec 16.2 MBytes 136 Mbits/sec 20 1.31 MBytes
[ 5] 2.00-3.00 sec 15.0 MBytes 126 Mbits/sec 56 959 KBytes
[ 5] 3.00-4.00 sec 13.8 MBytes 115 Mbits/sec 31 767 KBytes
[ 5] 4.00-5.00 sec 13.8 MBytes 115 Mbits/sec 20 831 KBytes
[ 5] 5.00-6.00 sec 15.0 MBytes 126 Mbits/sec 2 1.25 MBytes
[ 5] 6.00-7.00 sec 17.5 MBytes 147 Mbits/sec 23 1.37 MBytes
[ 5] 7.00-8.00 sec 17.5 MBytes 147 Mbits/sec 1 1.62 MBytes
[ 5] 8.00-9.00 sec 15.0 MBytes 126 Mbits/sec 5 1.62 MBytes
[ 5] 9.00-10.00 sec 17.5 MBytes 147 Mbits/sec 6 1.62 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 159 MBytes 133 Mbits/sec 190 sender
[ 5] 0.00-10.09 sec 157 MBytes 130 Mbits/sec receiver

iperf Done.</nowiki>

== Raspberry Pi 3B+ ==
=== Yggdrasil ===
<nowiki>[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.41 sec 37.3 MBytes 30.1 Mbits/sec receiver
[ 8] 0.00-10.41 sec 36.6 MBytes 29.5 Mbits/sec receiver
[ 10] 0.00-10.41 sec 36.6 MBytes 29.5 Mbits/sec receiver
[ 12] 0.00-10.41 sec 38.0 MBytes 30.6 Mbits/sec receiver
[SUM] 0.00-10.41 sec 149 MBytes 120 Mbits/sec receiver</nowiki>

== Tests ==

=== VPS Benchmark ===
Environment: Laptop, Rpi4, DO Droplet, mullvad

Fully wired, rpi connected via autoygg to droplet, which routes traffic out through mullvad

{| class="wikitable"
|+ Benchmarked VPS
! Size !! Download !! Upload !! Notes
|-
| $5 General || 55 Mbit/s || 30 Mbit/s || Tested steam downloads as well as speedtest.net
| $15 General || 53 Mbit/s || 47 Mbit/s || Tested speedtest.net
|-
|}

Benchmarks

2020-09-13T06:42:33Z

Stephen304:

== EspressoBin v5 ==
=== No Yggdrasil ===
<nowiki>Connecting to host 10.0.0.1, port 5201
[ 5] local 10.0.0.106 port 58198 connected to 10.0.0.1 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 49.2 MBytes 413 Mbits/sec 27 532 KBytes
[ 5] 1.00-2.00 sec 44.8 MBytes 376 Mbits/sec 0 592 KBytes
[ 5] 2.00-3.00 sec 44.8 MBytes 376 Mbits/sec 0 643 KBytes
[ 5] 3.00-4.00 sec 44.9 MBytes 376 Mbits/sec 1 519 KBytes
[ 5] 4.00-5.00 sec 46.1 MBytes 387 Mbits/sec 0 581 KBytes
[ 5] 5.00-6.00 sec 44.8 MBytes 376 Mbits/sec 0 639 KBytes
[ 5] 6.00-7.00 sec 46.1 MBytes 387 Mbits/sec 1 516 KBytes
[ 5] 7.00-8.00 sec 43.6 MBytes 366 Mbits/sec 374 346 KBytes
[ 5] 8.00-9.00 sec 44.9 MBytes 377 Mbits/sec 0 434 KBytes
[ 5] 9.00-10.00 sec 46.1 MBytes 387 Mbits/sec 0 509 KBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 455 MBytes 382 Mbits/sec 403 sender
[ 5] 0.00-10.05 sec 452 MBytes 377 Mbits/sec receiver

iperf Done.</nowiki>
=== Yggdrasil ===
<nowiki>Connecting to host 201:f06b:1827:4e45:90fa:554e:ace5:27c7, port 5201
[ 5] local 201:28ab:ee79:77d4:192e:1366:8b79:4980 port 33776 connected to 201:f06b:1827:4e45:90fa:554e:ace5:27c7 port 5201
[ ID] Interval Transfer Bitrate Retr Cwnd
[ 5] 0.00-1.00 sec 17.4 MBytes 146 Mbits/sec 26 1.50 MBytes
[ 5] 1.00-2.00 sec 16.2 MBytes 136 Mbits/sec 20 1.31 MBytes
[ 5] 2.00-3.00 sec 15.0 MBytes 126 Mbits/sec 56 959 KBytes
[ 5] 3.00-4.00 sec 13.8 MBytes 115 Mbits/sec 31 767 KBytes
[ 5] 4.00-5.00 sec 13.8 MBytes 115 Mbits/sec 20 831 KBytes
[ 5] 5.00-6.00 sec 15.0 MBytes 126 Mbits/sec 2 1.25 MBytes
[ 5] 6.00-7.00 sec 17.5 MBytes 147 Mbits/sec 23 1.37 MBytes
[ 5] 7.00-8.00 sec 17.5 MBytes 147 Mbits/sec 1 1.62 MBytes
[ 5] 8.00-9.00 sec 15.0 MBytes 126 Mbits/sec 5 1.62 MBytes
[ 5] 9.00-10.00 sec 17.5 MBytes 147 Mbits/sec 6 1.62 MBytes
- - - - - - - - - - - - - - - - - - - - - - - - -
[ ID] Interval Transfer Bitrate Retr
[ 5] 0.00-10.00 sec 159 MBytes 133 Mbits/sec 190 sender
[ 5] 0.00-10.09 sec 157 MBytes 130 Mbits/sec receiver

iperf Done.</nowiki>

== Raspberry Pi 3B+ ==
=== Yggdrasil ===
<nowiki>[ ID] Interval Transfer Bitrate
[ 5] 0.00-10.41 sec 37.3 MBytes 30.1 Mbits/sec receiver
[ 8] 0.00-10.41 sec 36.6 MBytes 29.5 Mbits/sec receiver
[ 10] 0.00-10.41 sec 36.6 MBytes 29.5 Mbits/sec receiver
[ 12] 0.00-10.41 sec 38.0 MBytes 30.6 Mbits/sec receiver
[SUM] 0.00-10.41 sec 149 MBytes 120 Mbits/sec receiver</nowiki>

== Tests ==

=== VPS Benchmark ===
Environment: Laptop, Rpi4, DO Droplet, mullvad

Fully wired, rpi connected via autoygg to droplet, which routes traffic out through mullvad

{| class="wikitable"
|+ Benchmarked VPS
! Size !! Download !! Upload !! Notes
|-
| $5 General || 55 Mbit/s || 30 Mbit/s || Tested steam downloads as well as speedtest.net
|-
|}

USB Ethernet Adapters

2020-09-05T04:00:37Z

Stephen304:

This page documents USB Ethernet Adapters that may be compatible with the MassMesh Mesh Node.

{| class="wikitable"
|+ USB Ethernet Adapter Comparison
! Brand !! Model !! Supported<sup>1</sup> !! Driver Required !! Links
|-
| Amazon Basics || USB 3.0 to 10/100/1000 Gigabit Ethernet Adapter || Yes || kmod-usb-net-asix-ax88179 || [https://www.amazon.com/dp/B00M77HMU0/ Amazon]
|-
| Anker || USB 3.0 Unibody Aluminum Gigabit Ethernet Adapter || Yes || kmod-usb-net-rtl8152 || [https://www.amazon.com/gp/product/B00PC0H9IE/ Amazon] [https://www.newegg.com/p/1B4-065J-001A0 Newegg]
|-
| Inland || USB 3.0 to Gigabit Ethernet Adapter || Likely || kmod-usb-net-asix-ax88179 ? || [https://www.microcenter.com/product/485118/USB_30_to_Gigabit_Ethernet_Adapter Micro Center]
|-
| TP-Link || TL-UE300 || Yes || kmod-usb-net-rtl8152 || [https://www.amazon.com/TP-Link-Foldable-Gigabit-Ethernet-Compatible/dp/B00YUU3KC6/ Amazon] [https://www.microcenter.com/product/496684/tp-link-usb-30-to-gigabit-ethernet-network-adapter Micro Center] [https://www.newegg.com/tp-link-ue300/p/N82E16833704260 Newegg]
|}

<sup>1</sup> For the purposes of this comparison, supported means that it works as intended out of the box<br/>

USB Ethernet Adapters

2020-09-05T03:51:24Z

Stephen304:

This page documents USB Ethernet Adapters that may be compatible with the MassMesh Mesh Node.

{| class="wikitable"
|+ USB Ethernet Adapter Comparison
! Brand !! Model !! Supported<sup>1</sup> !! Driver Required !! Links
|-
| Amazon Basics || USB 3.0 to 10/100/1000 Gigabit Ethernet Adapter || Yes || kmod-usb-net-asix-ax88179 || [https://www.amazon.com/dp/B00M77HMU0/ Amazon]
|-
| Anker || USB 3.0 Unibody Aluminum Gigabit Ethernet Adapter || Yes || kmod-usb-net-rtl8152 || [https://www.amazon.com/gp/product/B00PC0H9IE/ Amazon]
|-
| Inland || USB 3.0 to Gigabit Ethernet Adapter || Likely || kmod-usb-net-asix-ax88179 ? || [https://www.microcenter.com/product/485118/USB_30_to_Gigabit_Ethernet_Adapter Micro Center]
|-
| TP-Link || TL-UE300 || Yes || kmod-usb-net-rtl8152 || [https://www.amazon.com/TP-Link-Foldable-Gigabit-Ethernet-Compatible/dp/B00YUU3KC6/ Amazon] [https://www.microcenter.com/product/496684/tp-link-usb-30-to-gigabit-ethernet-network-adapter Micro Center]
|}

<sup>1</sup> For the purposes of this comparison, supported means that it works as intended out of the box<br/>

USB Ethernet Adapters

2020-09-03T17:16:17Z

Stephen304: Created page with "This page documents USB Ethernet Adapters that may be compatible with the MassMesh Mesh Node. {| class="wikitable" |+ USB Ethernet Adapter Comparison ! Brand !! Model !! Sup..."

Node Setup

2020-08-11T23:56:25Z

Stephen304: /* Install the Mass Mesh Firmware */

In these instructions, we will cover how to deploy a mesh node that is privacy-enabled by default, and allows you to share an Internet connection with your neighbors. The whole setup process takes about 2 hours from start to finish. The necessary hardware is listed below, and instructions for everything from flashing the firmware to placing the antenna are covered.

= Definitions =
* '''Mesh Node:''' A ''mesh node'' is the smallest unit on a mesh network. Every ''mesh node'' is a ''router'', and is critical for delivering the online traffic of its neighbors. For more details about how mesh networks and neighborhood networks work internally, please see the [[Network Architecture]] page.
* '''Firmware:''' Firmware is the first thing that you will install on your mesh node. ''Firmware'' is just like the operating system on your computer (Linux, Windows, Mac, etc.) ''Firmware'' is what allows us to install applications, manage users, and all the other things you can do on a functioning computer. The firmware that we use on our network is a customized version of [https://openwrt.org OpenWrt].
* '''Antenna/Radio:''' The ''antenna'' (or ''radio'') is what allows your mesh node to communicate with other mesh nodes. Our ''antennas'' communicate in [https://en.wikipedia.org/wiki/Open_spectrum free spectrum] at 2.4Ghz and 5Ghz -- just like the wi-fi in your home or workplace.
* '''Router:''' A ''router'' is any computer that is responsible for "routing" information on a network. All the ''mesh nodes'' on our network can also be called ''routers.''
* '''Gateway:''' A ''gateway'' or ''gateway server'' is a computer (usually a big one) that acts as a bridge between two networks. In order to provide a high level of security on our network, all of our ''mesh nodes'' reach the Internet through a ''gateway server.'' For more details about how mesh networks and neighborhood networks work internally, please see the [[Network Architecture]] page.

= Preparation =

{{Note|Set yourself up for success, and '''[https://riot.im/app/#/group/+massmesh:matrix.org introduce yourself in one of our chat rooms] before you begin.''' Something will go wrong during the setup process, and it's best to have experienced friends ready to help when it does.}}

== Considerations ==

* '''Time:''' about 2 hours
* '''Cost:''' about $150
* '''Internet Access:''' If you do not already have Internet access, you will need to find a neighbor (on your same street) who is willing to set up a mesh node at their home too, and work out a deal to share their Internet connection fairly.
* '''Difficulty:''' The instructions contained on this website are quite technical, and may be incomplete in some places. Most of these instructions were written with Linux users in mind. If you are using another operating system (like Windows or Mac,) some "[https://ddg.gg googling]" may be necessary to get through them. As stated above, it's good to have friends. [https://riot.im/app/#/group/+massmesh:matrix.org Introduce yourself in any of our chat channels] if you want some help getting started!

== Materials ==

=== Standard Mesh Node ===
To set up a standard mesh node that broadcasts a secure Internet connection in all directions, you will need to obtain the following equipment:
<gallery>
File:Rpf-raspberry-pi-4-model-b.png | '''[[RPF Raspberry Pi 4 Model B]]'''
File:Pi_power_supply.jpg | '''Official Raspberry Pi 4 Power Supply'''
File:MicroSD_card.jpg | '''microSD Card''' (4GB+)
File:Ethernet.jpg | '''Ethernet Cable (3x)''' (Three sections, cut to length)
File:usb_to_eth.png | '''USB to Ethernet Adapter (1+)'''
</gallery>
<gallery>
File:Ubnt-uap-ac-m.png | '''[[Ubiquiti UAP AC Mesh]]'''
File:Poe.jpg | '''PoE Injector''' (One should come with the UAP AC Mesh if you buy it new)
File:Paperclip.jpg | '''One Paperclip''' (Seriously, these come in handy)
</gallery>

=== Custom Mesh Nodes ===
If you know what kind of hardware you want, and this 'aint it, please see the recommended [[Hardware Bundles]], or browse the full list of [[:Category:Devices|Devices]].

= Firmware Installation =

If you prefer, bring your hardware to one of our weekly [https://massmesh.org/wiki/index.php?title=Contact_and_Meeting_Info meetups], and we will be happy to flash it for you!

== Raspberry Pi 4 ==

=== Materials & Software ===
{{Warning|Download and install the appropriate version of the [https://www.raspberrypi.org/downloads/ Raspberry Pi Imager] for your computer before continuing.}}
<gallery>
File:Rpf-raspberry-pi-4-model-b.png | '''[[RPF Raspberry Pi 4 Model B]]'''
File:MicroSD_card.jpg | '''microSD Card''' (4GB+)
File:Ethernet.jpg | '''Ethernet Cable (1x)'''
</gallery>

=== Install the Firmware ===
# Download the latest stable version of Mass Mesh's free firmware [https://downloads.massmesh.net/snapshots/images/meshnode/rpi-4/openwrt-massmesh-meshnode-bcm27xx-bcm2711-rpi-4-ext4-sysupgrade.img.gz here]
# Open the Raspberry Pi Imager (Download and install it from [https://www.raspberrypi.org/downloads/ here] if you haven't yet.)
# Select "Choose OS"
## [[File:RPI_Imager_Main_Screen.png|frameless|Select "Choose OS"]]
# Scroll to the bottom of the list, and select "Use Custom"
## [[File:RPI_Imager_Use_Custom.png|frameless|Scroll to the bottom of the list, and select "Use Custom"]]
# Find the Mass Mesh firmware you just downloaded, and select it from the filesystem.
# Once you have selected the appropriate firmware, select "Choose SD Card"
## [[File:RPI_Imager_Main_Screen.png|frameless|Once you have selected the appropriate firmware, select "Choose SD Card"]]
# You should see something like the following. Go ahead and select that card. (You probably only see one, but use the size of the card as a hint if you see several.)
## [[File:RPI_Imager_Select_SD_Card.png|frameless|Go ahead and select that card. (You probably only see one, but use the size of the card as a hint if you see several.)]]
# Once you have selected the OS and the SD Card, select "Write." You will see a warning like the one shown below... Go ahead and select "Yes."
## [[File:RPI_Imager_Write.png|frameless|Once you have selected the OS and the SD Card, select "Write."]]
## [[File:RPI_Imager_Warning.png|frameless|You will see a warning like this... Go ahead and select "Yes."]]
# You should see a screen like the following. Click "Continue," and remove the SD card from your computer.
## [[File:RPI_Imager_Success.png|frameless|Click "Continue," and remove the SD card from your computer.]]
# Plug the micro SD card into your Raspberry Pi 4.

'''Congratulations!!!''' You have successfully prepared your Raspberry Pi 4b to act as a secure mesh node. Set it aside for now while we prepare the other hardware. We will assemble it at the end in [[#Assembly]].

== UAP AC Mesh ==

=== Materials ===

<gallery>
File:Ubnt-uap-ac-m.png | '''[[Ubiquiti UAP AC Mesh]]'''
File:Ethernet.jpg | '''Ethernet Cable (2x)'''
File:Poe.jpg | '''PoE Injector''' (One should come with the UAP AC Mesh if you buy it new)
File:Paperclip.jpg | '''One Paperclip''' (Seriously, these come in handy)
</gallery>

=== Install the Firmware ===

The steps to install firmware on the antenna are a bit different than they were for the Raspberry Pi. For one thing, the antenna does not have an SD card. So, we will have to install the firmware by connecting to the antenna with our laptop. Please see page 6 of the "Node Installation Guide" for instructions on plugging in the antenna. After you have followed the instructions there, connect your computer to the port marked "LAN" on your PoE injector. We are now ready to begin installing the firmware.

==== Enter Factory Reset Mode ====

# Put the antenna into factory reset mode
## Unplug the ethernet from the antenna
## Use a paper clip to hold in the reset button
## Plug the ethernet back in to the antenna, holding the paperclip steady as you do
## Continue holding the paper clip until the light on the side of your UAP AC Mesh starts blinking OFF/WHITE/BLUE (should take about 30 seconds)

==== Set Up a Static IP Address ====

# Assign your computer a static IP address of 192.168.1.25/24
## '''Windows:''' [https://winaero.com/blog/set-static-ip-address-windows-10/ Setting a static IP address in Windows 10]
## '''Mac:''' [https://osxdaily.com/2010/12/17/set-static-ip-address-mac/ Setting a static IP address in OSX]
## '''Linux:''' [https://linuxize.com/post/how-to-configure-static-ip-address-on-ubuntu-18-04/#configuring-static-ip-address-on-ubuntu-desktop Setting a static IP address in Ubuntu 18.04 desktop]
# Open a command prompt/terminal, and type <pre>ping 192.168.1.20</pre>

You should see something like this: (Hit Ctrl + c to stop the output)

<pre>
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=63 time=3.37 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=63 time=1.36 ms
64 bytes from 192.168.1.20: icmp_seq=3 ttl=63 time=0.995 ms
64 bytes from 192.168.1.20: icmp_seq=4 ttl=63 time=1.81 ms
</pre>

* If you don't see something like what's shown above, go back and make sure that the light on the side of your UAP AC Mesh is blinking in the pattern indicated above. If not, start again from [[#Enter Factory Reset Mode]]
* If the light is blinking properly and you still can't ping the device, make sure that your static IP address was assigned properly. If not, start again from [[#Set Up a Static IP Address]]
* If you are still having trouble pinging the device, reach out for help in the chatroom. Someone will help you get unstuck.

==== Downgrade Ubiquiti AirOS ====

Because we are "jailbreaking" the Ubiquiti router, we have to downgrade to an older version of their proprietary firmware first. Using a tool called TFTP, we can do this quite simply.

# Download [https://dl.ui.com/unifi/firmware/U7PG2/3.7.58.6385/BZ.qca956x.v3.7.58.6385.170508.0957.bin version 3.7 of Ubiquiti's AirOS]
# Rename the firmware file to <code>firmware.bin</code>, as the device will look for this file name
# Use TFTP to flash the firmware onto the device:
<pre>
tftp> connect 192.168.1.20
tftp> binary
tftp> rexmt 1
tftp> timeout 60
tftp> put firmware.bin
Sent x bytes in x seconds
</pre>
The LED will flash at varying speeds, then it will turn solid when complete.

==== Install the Mass Mesh Firmware ====
Get the firmware [https://downloads.massmesh.net/snapshots/images/meshradio/ubnt_unifiac-mesh/openwrt-massmesh-meshradio-ath79-generic-ubnt_unifiac-mesh-squashfs-sysupgrade.bin here.]

In the stock firmware, the access point will have the default user/pass <code>ubnt / ubnt</code>. If there is no DHCP server, it will assign itself the IP address <code>192.168.1.20</code>.

<ol>
<li>Statically assign your computer the IP address <code>192.168.1.25</code></li>
<li>Power on the device and plug it into your computer's ethernet port</li>
<li>Copy the firmware you want to flash to the device:</li>
<pre>scp openwrt-ar71xx-generic-ubnt-unifiac-lite-squashfs-sysupgrade.bin ubnt@192.168.1.20:/tmp/</pre>
<li>SSH into the device and log in with the default username and password <code>ubnt / ubnt</code></li>
<pre>ssh ubnt@192.168.1.20</pre>
<li>Then write the firmware to <code>kernel0</code> and <code>kernel1</code></li>
<pre>
BZ.v3.7.40# mtd write /tmp/openwrt-ar71xx-generic-ubnt-unifiac-lite-squashfs-sysupgrade.bin kernel0
Unlocking kernel0 ...
Erasing kernel0 ...
Writing from /tmp/openwrt-ar71xx-generic-ubnt-unifiac-lite-squashfs-sysupgrade.bin to kernel0 ... [e/w]

BZ.v3.7.40# mtd -r write /tmp/openwrt-ar71xx-generic-ubnt-unifiac-lite-squashfs-sysupgrade.bin kernel1
Unlocking kernel1 ...
Erasing kernel1 ...
Writing from /tmp/openwrt-ar71xx-generic-ubnt-unifiac-lite-squashfs-sysupgrade.bin to kernel1 ... [e/w]
</pre>
</ol>

After writing the firmware and giving the radio a <code>reboot</code> please wait upwards of 5+ minutes during this "first boot" process. Soon you'll be able to access to device over WiFi (or Ethernet) in order to set a new admin password. (192.168.2.1)

'''Congratulations!''' You have now installed all the firmware you need.

= Assembly =

To assemble your mesh node, please follow this PDF guide. It can be downloaded for your convenience.

<pdf>File:New_Node_Install_Guide.pdf</pdf>

= Next Steps =

{{Note|You still have to do [[Gateway Configuration]] in order to access the Internet.}}

# [[First Time Setup]]
# [[Gateway Configuration]]

Node Setup

2020-08-11T23:51:36Z

Stephen304: /* Downgrade Ubiquiti AirOS */

In these instructions, we will cover how to deploy a mesh node that is privacy-enabled by default, and allows you to share an Internet connection with your neighbors. The whole setup process takes about 2 hours from start to finish. The necessary hardware is listed below, and instructions for everything from flashing the firmware to placing the antenna are covered.

= Definitions =
* '''Mesh Node:''' A ''mesh node'' is the smallest unit on a mesh network. Every ''mesh node'' is a ''router'', and is critical for delivering the online traffic of its neighbors. For more details about how mesh networks and neighborhood networks work internally, please see the [[Network Architecture]] page.
* '''Firmware:''' Firmware is the first thing that you will install on your mesh node. ''Firmware'' is just like the operating system on your computer (Linux, Windows, Mac, etc.) ''Firmware'' is what allows us to install applications, manage users, and all the other things you can do on a functioning computer. The firmware that we use on our network is a customized version of [https://openwrt.org OpenWrt].
* '''Antenna/Radio:''' The ''antenna'' (or ''radio'') is what allows your mesh node to communicate with other mesh nodes. Our ''antennas'' communicate in [https://en.wikipedia.org/wiki/Open_spectrum free spectrum] at 2.4Ghz and 5Ghz -- just like the wi-fi in your home or workplace.
* '''Router:''' A ''router'' is any computer that is responsible for "routing" information on a network. All the ''mesh nodes'' on our network can also be called ''routers.''
* '''Gateway:''' A ''gateway'' or ''gateway server'' is a computer (usually a big one) that acts as a bridge between two networks. In order to provide a high level of security on our network, all of our ''mesh nodes'' reach the Internet through a ''gateway server.'' For more details about how mesh networks and neighborhood networks work internally, please see the [[Network Architecture]] page.

= Preparation =

{{Note|Set yourself up for success, and '''[https://riot.im/app/#/group/+massmesh:matrix.org introduce yourself in one of our chat rooms] before you begin.''' Something will go wrong during the setup process, and it's best to have experienced friends ready to help when it does.}}

== Considerations ==

* '''Time:''' about 2 hours
* '''Cost:''' about $150
* '''Internet Access:''' If you do not already have Internet access, you will need to find a neighbor (on your same street) who is willing to set up a mesh node at their home too, and work out a deal to share their Internet connection fairly.
* '''Difficulty:''' The instructions contained on this website are quite technical, and may be incomplete in some places. Most of these instructions were written with Linux users in mind. If you are using another operating system (like Windows or Mac,) some "[https://ddg.gg googling]" may be necessary to get through them. As stated above, it's good to have friends. [https://riot.im/app/#/group/+massmesh:matrix.org Introduce yourself in any of our chat channels] if you want some help getting started!

== Materials ==

=== Standard Mesh Node ===
To set up a standard mesh node that broadcasts a secure Internet connection in all directions, you will need to obtain the following equipment:
<gallery>
File:Rpf-raspberry-pi-4-model-b.png | '''[[RPF Raspberry Pi 4 Model B]]'''
File:Pi_power_supply.jpg | '''Official Raspberry Pi 4 Power Supply'''
File:MicroSD_card.jpg | '''microSD Card''' (4GB+)
File:Ethernet.jpg | '''Ethernet Cable (3x)''' (Three sections, cut to length)
File:usb_to_eth.png | '''USB to Ethernet Adapter (1+)'''
</gallery>
<gallery>
File:Ubnt-uap-ac-m.png | '''[[Ubiquiti UAP AC Mesh]]'''
File:Poe.jpg | '''PoE Injector''' (One should come with the UAP AC Mesh if you buy it new)
File:Paperclip.jpg | '''One Paperclip''' (Seriously, these come in handy)
</gallery>

=== Custom Mesh Nodes ===
If you know what kind of hardware you want, and this 'aint it, please see the recommended [[Hardware Bundles]], or browse the full list of [[:Category:Devices|Devices]].

= Firmware Installation =

If you prefer, bring your hardware to one of our weekly [https://massmesh.org/wiki/index.php?title=Contact_and_Meeting_Info meetups], and we will be happy to flash it for you!

== Raspberry Pi 4 ==

=== Materials & Software ===
{{Warning|Download and install the appropriate version of the [https://www.raspberrypi.org/downloads/ Raspberry Pi Imager] for your computer before continuing.}}
<gallery>
File:Rpf-raspberry-pi-4-model-b.png | '''[[RPF Raspberry Pi 4 Model B]]'''
File:MicroSD_card.jpg | '''microSD Card''' (4GB+)
File:Ethernet.jpg | '''Ethernet Cable (1x)'''
</gallery>

=== Install the Firmware ===
# Download the latest stable version of Mass Mesh's free firmware [https://downloads.massmesh.net/snapshots/images/meshnode/rpi-4/openwrt-massmesh-meshnode-bcm27xx-bcm2711-rpi-4-ext4-sysupgrade.img.gz here]
# Open the Raspberry Pi Imager (Download and install it from [https://www.raspberrypi.org/downloads/ here] if you haven't yet.)
# Select "Choose OS"
## [[File:RPI_Imager_Main_Screen.png|frameless|Select "Choose OS"]]
# Scroll to the bottom of the list, and select "Use Custom"
## [[File:RPI_Imager_Use_Custom.png|frameless|Scroll to the bottom of the list, and select "Use Custom"]]
# Find the Mass Mesh firmware you just downloaded, and select it from the filesystem.
# Once you have selected the appropriate firmware, select "Choose SD Card"
## [[File:RPI_Imager_Main_Screen.png|frameless|Once you have selected the appropriate firmware, select "Choose SD Card"]]
# You should see something like the following. Go ahead and select that card. (You probably only see one, but use the size of the card as a hint if you see several.)
## [[File:RPI_Imager_Select_SD_Card.png|frameless|Go ahead and select that card. (You probably only see one, but use the size of the card as a hint if you see several.)]]
# Once you have selected the OS and the SD Card, select "Write." You will see a warning like the one shown below... Go ahead and select "Yes."
## [[File:RPI_Imager_Write.png|frameless|Once you have selected the OS and the SD Card, select "Write."]]
## [[File:RPI_Imager_Warning.png|frameless|You will see a warning like this... Go ahead and select "Yes."]]
# You should see a screen like the following. Click "Continue," and remove the SD card from your computer.
## [[File:RPI_Imager_Success.png|frameless|Click "Continue," and remove the SD card from your computer.]]
# Plug the micro SD card into your Raspberry Pi 4.

'''Congratulations!!!''' You have successfully prepared your Raspberry Pi 4b to act as a secure mesh node. Set it aside for now while we prepare the other hardware. We will assemble it at the end in [[#Assembly]].

== UAP AC Mesh ==

=== Materials ===

<gallery>
File:Ubnt-uap-ac-m.png | '''[[Ubiquiti UAP AC Mesh]]'''
File:Ethernet.jpg | '''Ethernet Cable (2x)'''
File:Poe.jpg | '''PoE Injector''' (One should come with the UAP AC Mesh if you buy it new)
File:Paperclip.jpg | '''One Paperclip''' (Seriously, these come in handy)
</gallery>

=== Install the Firmware ===

The steps to install firmware on the antenna are a bit different than they were for the Raspberry Pi. For one thing, the antenna does not have an SD card. So, we will have to install the firmware by connecting to the antenna with our laptop. Please see page 6 of the "Node Installation Guide" for instructions on plugging in the antenna. After you have followed the instructions there, connect your computer to the port marked "LAN" on your PoE injector. We are now ready to begin installing the firmware.

==== Enter Factory Reset Mode ====

# Put the antenna into factory reset mode
## Unplug the ethernet from the antenna
## Use a paper clip to hold in the reset button
## Plug the ethernet back in to the antenna, holding the paperclip steady as you do
## Continue holding the paper clip until the light on the side of your UAP AC Mesh starts blinking OFF/WHITE/BLUE (should take about 30 seconds)

==== Set Up a Static IP Address ====

# Assign your computer a static IP address of 192.168.1.25/24
## '''Windows:''' [https://winaero.com/blog/set-static-ip-address-windows-10/ Setting a static IP address in Windows 10]
## '''Mac:''' [https://osxdaily.com/2010/12/17/set-static-ip-address-mac/ Setting a static IP address in OSX]
## '''Linux:''' [https://linuxize.com/post/how-to-configure-static-ip-address-on-ubuntu-18-04/#configuring-static-ip-address-on-ubuntu-desktop Setting a static IP address in Ubuntu 18.04 desktop]
# Open a command prompt/terminal, and type <pre>ping 192.168.1.20</pre>

You should see something like this: (Hit Ctrl + c to stop the output)

<pre>
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=63 time=3.37 ms
64 bytes from 192.168.1.20: icmp_seq=2 ttl=63 time=1.36 ms
64 bytes from 192.168.1.20: icmp_seq=3 ttl=63 time=0.995 ms
64 bytes from 192.168.1.20: icmp_seq=4 ttl=63 time=1.81 ms
</pre>

* If you don't see something like what's shown above, go back and make sure that the light on the side of your UAP AC Mesh is blinking in the pattern indicated above. If not, start again from [[#Enter Factory Reset Mode]]
* If the light is blinking properly and you still can't ping the device, make sure that your static IP address was assigned properly. If not, start again from [[#Set Up a Static IP Address]]
* If you are still having trouble pinging the device, reach out for help in the chatroom. Someone will help you get unstuck.

==== Downgrade Ubiquiti AirOS ====

Because we are "jailbreaking" the Ubiquiti router, we have to downgrade to an older version of their proprietary firmware first. Using a tool called TFTP, we can do this quite simply.

# Download [https://dl.ui.com/unifi/firmware/U7PG2/3.7.58.6385/BZ.qca956x.v3.7.58.6385.170508.0957.bin version 3.7 of Ubiquiti's AirOS]
# Rename the firmware file to <code>firmware.bin</code>, as the device will look for this file name
# Use TFTP to flash the firmware onto the device:
<pre>
tftp> connect 192.168.1.20
tftp> binary
tftp> rexmt 1
tftp> timeout 60
tftp> put firmware.bin
Sent x bytes in x seconds
</pre>
The LED will flash at varying speeds, then it will turn solid when complete.

==== Install the Mass Mesh Firmware ====
# scp the firmware onto the device
# Write the firmware to the device using MTD

'''Congratulations!''' You have now installed all the firmware you need.

= Assembly =

To assemble your mesh node, please follow this PDF guide. It can be downloaded for your convenience.

<pdf>File:New_Node_Install_Guide.pdf</pdf>

= Next Steps =

{{Note|You still have to do [[Gateway Configuration]] in order to access the Internet.}}

# [[First Time Setup]]
# [[Gateway Configuration]]

Category:Devices

2020-02-05T23:54:25Z

Stephen304: Add 60g radio

__FORCETOC__
In order to mesh with other mesh nodes in your neighborhood network, you will require two main components: a device to run the Mass Mesh firmware and a radio so that you can communicate with other nodes.
{{Note|We also maintain a helpful list of [[Hardware Bundles]] for your convenience.}}
{{Warning|Always check the openwrt wiki *and* techdata *and* commit before buying a new device. Flashing OpenWRT can be very difficult on certain routers.}}

== Mesh Node Devices ==
These are devices that can run the meshing protocol (Yggdrasil.) Once they have the Mass Mesh firmware flashed, you can connect to them for access to the mesh via wifi and/or ethernet. They will also automatically discover and connect to nearby mesh nodes via their [[#Mesh Radio Devices|connected mesh radio]].

{| class="wikitable"
|+ Supported Devices
! Brand !! Model !! Vendor Materials !! Yggdrasil Speed !! Mesh Exit Capable !! Built-in Wifi !! Outdoor !! Year !! MSRP
|-
| [[:Category:Raspberry Pi Foundation|Raspberry Pi Foundation]] || [[RPF Raspberry Pi 4 Model B|Raspberry Pi 4 Model B]] || [https://www.raspberrypi.org/documentation/hardware/raspberrypi/README.md Hardware Specifications] || 450 Mbit/s || No<sup>3</sup> || Yes || No<sup>2</sup> || 2019 || $35.00
|-
| PC Engines || [[PC Engines APU2|APU2]] || [https://pcengines.ch/pdf/apu2.pdf Owner's Manual], [https://pcengines.ch/apu2c4.htm Product File] || 950 Mbit/s || Yes || No<sup>1</sup> || No<sup>2</sup> || 2016 || $115.00
|-
|}

<sup>1</sup> USB and 2 mini-pcie interfaces available to add one or more wifi interfaces<br/>
<sup>2</sup> Possible with outdoor case<br/>
<sup>3</sup> Possible with additional adapters<br/>

== Mesh Radio Devices ==

{| class="wikitable"
|+ Supported Point-To-Multi-Point (PTMP) Radios
! Brand !! Model !! Vendor Materials !! Outdoor !! Year !! MSRP
|-
| [[:Category:Ubiquiti|Ubiquiti]] || [[Ubiquiti NanoStation 5AC Loco|NanoStation 5AC Loco]] || [https://dl.ubnt.com/guides/NanoStation_ac/NS-5ACL_QSG.pdf Quick Start Guide], [https://dl.ubnt.com/datasheets/NanoStation_AC/NanoStation_AC_DS.pdf Data Sheet] || Yes || ? || $60.00
|-
| [[:Category:Ubiquiti|Ubiquiti]] || [[Ubiquiti UAP AC Mesh|UAP AC Mesh]] || [http://dl-origin.ubnt.com/guides/UniFi/UniFi_AP-AC-M_QSG.pdf Quick Start Guide], [http://dl-origin.ubnt.com/datasheets/unifi/UniFi_AC_Mesh_DS.pdf Data Sheet] || Yes || 2016 || $120.00
|-
|}

== Point-To-Point Radio Devices ==
PTP radios are devices that provide a direct link between 2 locations, usually over a long range. There is no need for custom firmware on these radios. Simply configure both ends of the link with matching settings and provide line-of-sight between them to connect.

{| class="wikitable"
|+ Supported Point-To-Point (PTP) Radios
! Brand !! Model !! Vendor Materials !! Outdoor !! Year !! MSRP
|-
| [[:Category:MikroTik|MikroTik]] || [[MikroTik wAP 60G]] || [https://i.mt.lv/cdn/rb_files/1542446763RBwAPG-60ad-h.pdf Quick Start Guide] || Yes || ? || $99
|-
| [[:Category:Ubiquiti|Ubiquiti]] || [[Ubiquiti LiteBeam 5AC Gen2|LiteBeam 5AC Gen2]] || [https://dl.ubnt.com/guides/LiteBeam_Gen2/LiteBeam_5AC-Gen2_QSG.pdf Quick Start Guide], [https://dl.ubnt.com/datasheets/LiteBeam/LiteBeam_AC_Gen2_DS.pdf Data Sheet] || Yes || ? || ?
|-
| [[:Category:Ubiquiti|Ubiquiti]] || [[Ubiquiti NanoBeam 5AC 16|NanoBeam 5AC 16]] || [https://dl.ubnt.com/guides/NanoBeam_ac/NanoBeam_NBE-5AC-16_QSG.pdf Quick Start Guide], [https://dl.ubnt.com/datasheets/NanoBeam_ac/NanoBeam_ac_DS.pdf Data Sheet] || Yes || ? || ?
|-
|}

== Work In Progress Devices ==
{{Warning| The following devices are unsupported. '''If you are looking to host a node, we recommend that you buy one of the supported devices,''' as it's guaranteed that they will work in the mesh.}}
{{Note| A great way to help the tech team is to work with us to add support for the WIP devices.}}

{| class="wikitable"
|+ Work In Progress (WIP) Devices
! Brand !! Model !! Yggdrasil Speed !! Mesh Exit Capable !! Built-in Wifi !! Outdoor !! Year !! MSRP !! Notes
|-
| [[:Category:Globalscale|Globalscale]] || [[Globalscale ESPRESSObin v5|Espressobin v5]] || 300 Mbit/s || Yes || No<sup>1</sup> || No || 2017 || $49.00 || Fails to boot, no longer available for purchase
|-
| [[:Category:Linksys|Linksys]] || [[Linksys WRT1900AC|WRT1900AC]] || ? || Yes || Yes || No || 2014 || $149.99 ||
|-
| [[:Category:TP-Link|TP-Link]] || [[TP-Link Archer C7 AC1750|Archer C7 AC1750]] || ? || Yes || Yes || No || 2013 || $99.99 ||
|-
| [[:Category:TP-Link|TP-Link]] || [[TL-WDR3500]] || ? || Yes || Yes || No || 2012 || $44.99 ||
|-
| [[:Category:TP-Link|TP-Link]] || [[TL-WDR4300]] || ? || Yes || Yes || No || 2012 || $109.99 ||
|-
| [[:Category:Xiaomi|Xiaomi]] || [[Xiaomi Mi Router 3|Mi Router 3]] || ? || Yes || Yes || No || ? || $30.00 ||
|-
| [[:Category:Aerohive|Aerohive]] || [[Aerohive AP330|AP330]] || ? || ? || Yes || No || 2013 || ? || Must flash Open WRT [https://git.openwrt.org/?p=openwrt/openwrt.git;a=commit;h=f2b7d9dc1ca3d33f14961cf2885639f4f9e8965e via UART.]
|-
|}

<sup>1</sup> USB and mini-pcie interfaces available to add a wifi interface<br/>

Ubiquiti NanoStation 5AC Loco

2020-01-29T02:00:57Z

Stephen304: /* Downgrade Ubiquiti AirOS With An External Programmer */

[[Category:Devices]]
[[Category:Ubiquiti]]
[[File:Ubnt-ns-5ac-loco.png|thumb|NanoStation 5AC Loco]]

The NanoStation 5AC Loco is a directional, weather resistant, PoE powered radio with a beam width of 90 degrees and a secondary omnidirectional radio. This makes it useful for simultaneously meshing on one radio while providing an access point for client devices on the other.

{{ Warning| This is a PoE device. Never connect your computer directly to the PoE injector's red port!!!}}

{{Note| The Nanostation's architecture is '''MIPS 24KC.'''}}

{{ Warning| As of January 1, 2020, brand new Nanostations do not support downgrading the Ubiquiti AirOS firmware. (Even with the patch.)}}

== Files ==
[https://dl.ubnt.com/firmwares/XC-fw/v8.5.0/WA.v8.5.0.36727.180118.1314.bin Stock Firmware v8.5.0.36727]

[https://github.com/MassMesh/meta-imagebuilder-artifacts/raw/master/massmesh/meshradio/ubnt_nanostation-ac-loco/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin MassMesh Firmware (Factory) (Latest)]

[https://github.com/MassMesh/meta-imagebuilder-artifacts/raw/master/massmesh/meshradio/ubnt_nanostation-ac-loco/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-sysupgrade.bin MassMesh Firmware (Sysupgrade) (Latest)]

== Flashing ==

=== From OpenWrt ===
{{Note|Mass Mesh mesh radios have a static IP of 192.168.2.1. To access the admin UI, set your computer's ip/netmask to 192.168.2.10/24, then browse to http://192.168.2.1/ in your favorite web browser.}}
# Download the latest [https://github.com/MassMesh/meta-imagebuilder-artifacts/raw/master/massmesh/meshradio/ubnt_nanostation-ac-loco/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-sysupgrade.bin MassMesh sysupgrade firmware.]
# Connect to the Nanostation and enter its IP address into your favorite web browser.
## If you are using another version of OpenWrt, please refer to its documentation for details about its IP address.
# Navigate to System → Backup / Flash Firmware → Actions: '''Flash new firmware image.'''
# Choose the sysupgrade file previously downloaded and click '''Flash'''
# Wait for the device to complete and reboot (This can take up to 5 minutes.)

=== From Stock Firmware (Ubiquiti AirOS)===

==== Downgrade Ubiquiti AirOS ====

# Download the [https://dl.ubnt.com/firmwares/XC-fw/v8.5.0/WA.v8.5.0.36727.180118.1314.bin Stock Firmware Image v8.5.0.36727].
# Power on the Nanostation via a PoE injector. (This is the **red** ethernet port on your injector.)
# Connect the LAN side of the PoE injector to a computer.
# Assign a static IP/netmask of <code>192.168.1.25/24</code> to the computer
## <code>sudo ip addr add 192.168.1.25/24 dev eth0</code>
# Use a browser to visit http://192.168.1.20/
# Login using the set password or default credentials <code>ubnt / ubnt</code>
# Navigate to settings and downgrade the stock firmware to v8.5.0.36727 using the downloaded image file

==== Install The Mass Mesh OpenWrt Image ====

{{ Note| Additional instructions are available [https://openwrt.org/toh/ubiquiti/ubiquiti_nanostation_ac_loco on OpenWrt's website].}}
# Download the latest Mass Mesh firmware [https://github.com/MassMesh/meta-imagebuilder-artifacts/raw/master/massmesh/meshradio/ubnt_nanostation-ac-loco/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin here].
# Copy the firmware onto the nanostation. (We like to put it in the <code>/tmp/</code> directory.)
# Open a secure shell on the Nanostation. <code>ssh ubnt@192.168.1.20</code>
# Patch the fwupdate.real binary a la the instructions [https://openwrt.org/toh/ubiquiti/ubiquiti_nanostation_ac_loco here.]
# <code>/tmp/fwupdate.real -m /tmp/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin</code>

=== Downgrade Ubiquiti AirOS With An External Programmer===

When your nanostation is bricked, or if the stock firmware won't let you flash our custom firmware, you can use the '''In-System Programming''' (ISP) technique to reflash the device (see also the [https://www.flashrom.org/ISP Flashrom wiki]. You're going to need:

# a Pomona 5252 test clip (https://www.digikey.com/product-detail/en/pomona-electronics/5252/501-2059-ND/745103), ~$16
# a raspberry pi (e.g. a zero w) ~$10
# some header pins and prototyping wires to connect everything

The Nanostation has a Macronix MX25L12835F rom chip ([https://www.macronix.com/Lists/Datasheet/Attachments/7397/MX25L12835F,%203V,%20128Mb,%20v1.6.pdf datasheet]), which is an SPI chip with 16 connectors good for 128 Mbit of storage.

We can use [https://flashrom.org Flashrom] running on a raspberry pi to read and write that chip, if we hook up the Pomona 5252 test clip to the MX25L12835F and connect it to the correct [https://pinout.xyz/pinout/spi SPI pins] on the pi:

[[File:raspberry-pi-pinout.png|inline|raspberry pi GPIO pinout]]

(note: the SPI1 CE0/CE1 pins are not labeled on this image)

==== Pinouts (please proceed with caution!) ====

The Raspberry Pi has 2 SPI interfaces, SPI0 and SPI1.

On the Raspberry Pi boot partition, make sure to update config.txt and uncomment the line that reads

dtparam=spi=on

After a reboot, you should see the spi device files:

root@raspberrypi:/home/pi# ls -laF /dev/spidev0.*
crw-rw---- 1 root spi 153, 0 Jan 7 01:44 /dev/spidev0.0
crw-rw---- 1 root spi 153, 1 Jan 7 01:44 /dev/spidev0.1

Now connect the Raspberry Pi to the Pomona clip. Choose either SPI0 or SPI1. We're going to leave the VCC pin on the flash chip disconnected. We are however going to connect a few other pins to our 3.3V source from the raspberry pi, to pull them up.

{| class="wikitable"
|-
!colspan="2"|RPi SPI0!!colspan="2"|RPi SPI1!!colspan="2"|Pomona Clip!!Notes!!Color in picture below
|-
|17||3.3V
|17||3.3V
|1||SIO3
|''we do not use this pin, so we pull it up''
|red
|-
|17||3.3V
|17||3.3V
|9||WP#SIO2
|''put the chip in read/write mode''
|red
|-
|19||SPI0 MOSI
|38||SPI1 MOSI
|15||SI
|
|blue
|-
|21||SPI0 MISO
|35||SPI1 MISO
|8||SO
|
|orange
|-
|23||SPI0 SCLK
|40||SPI1 SCLK
|16||SCLK
|
|green
|-
|25||GND
|25||GND
|10||GND
|
|brown
|-
|24||SPI0 CE0
|12||SPI1 CE0
|7||CS
|
|yellow
|}

[[File:20200127-raspberry-pi-zero-w-with-pomona-clip.jpg|thumb|A Raspberry Pi Zero W with wires connected to the SPI0 pins. There is an unused 3.3V wire visible.]]

==== Reading the chip with flashrom ====

Once the pomona is connected to the raspberry pi, make sure the nanostation is disconnected from power/ethernet. Then clip on the pomona.

Flashrom on the raspberry pi requires us to specify the spi speed for the operation. We also need to specify the exact rom chip model, because there are two models that match:

$ flashrom -p linux_spi:dev=/dev/spidev0.0,spispeed=30000 -r proprietary.rom
flashrom on Linux 4.19.75+ (armv6l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Macronix flash chip "MX25L12805D" (16384 kB, SPI) on linux_spi.
Found Macronix flash chip "MX25L12835F/MX25L12845E/MX25L12865E" (16384 kB, SPI) on linux_spi.
Multiple flash chip definitions match the detected chip(s): "MX25L12805D", "MX25L12835F/MX25L12845E/MX25L12865E"
Please specify which chip definition to use with the -c <chipname> option.

So here's the final command to read out the chip:

$ flashrom -c "MX25L12835F/MX25L12845E/MX25L12865E" -p linux_spi:dev=/dev/spidev0.0,spispeed=30000 -r proprietary.rom
flashrom on Linux 4.19.75+ (armv6l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Macronix flash chip "MX25L12835F/MX25L12845E/MX25L12865E" (16384 kB, SPI) on linux_spi.
Reading flash... done.

It's easy to verify that if the reading worked. If you were reading out the original firmware, binwalk would print something like this:

$ binwalk proprietary.rom

DECIMAL HEXADECIMAL DESCRIPTION
--------------------------------------------------------------------------------
115152 0x1C1D0 Certificate in DER format (x509 v3), header length: 4, sequence length: 64
142896 0x22E30 U-Boot version string, "U-Boot 1.1.4-s1100 (Sep 5 2018 - 17:53:00)"
143184 0x22F50 CRC32 polynomial table, big endian
224396 0x36C8C CRC32 polynomial table, big endian
226924 0x3766C Ubiquiti end header, header size: 12 bytes, cumulative ~CRC32: 0x454E442E
231856 0x389B0 Ubiquiti partition header, header size: 56 bytes, name: "PARTkernel", base address: 0x00000001, data size: -2147475456 bytes
231920 0x389F0 uImage header, header size: 64 bytes, header CRC: 0xE75790E0, created: 2018-11-13 14:36:59, image size: 998847 bytes, Data
Address: 0x80002000, Entry Point: 0x80002000, data CRC: 0xAAECA664, OS: Linux, CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: "MIPS Ubiquiti Linux-2.6.32.68"
327680 0x50000 uImage header, header size: 64 bytes, header CRC: 0x22425505, created: 2019-02-13 09:09:52, image size: 990770 bytes, Data Address: 0x80002000, Entry Point: 0x80002000, data CRC: 0x8F3B71D3, OS: Linux, CPU: MIPS, image type: OS Kernel Image, compression type: lzma, image name: "MIPS Ubiquiti Linux-2.6.32.68"
327744 0x50040 LZMA compressed data, properties: 0x5D, dictionary size: 8388608 bytes, uncompressed size: 2836596 bytes
1318514 0x141E72 Ubiquiti partition header, header size: 56 bytes, name: "PARTrootfs", base address: 0x00000002, data size: 0 bytes
1318578 0x141EB2 Squashfs filesystem, little endian, version 4.0, compression:lzma, size: 7203018 bytes, 956 inodes, blocksize: 262144 bytes, created: 2019-02-13 09:09:54

Useful resources:
* [https://www.flashrom.org/RaspberryPi Flashrom page on using the Raspberry Pi as a flashing tool]

==== Writing to the chip with flashrom ====

pi@raspberrypi:~ $ flashrom -c "MX25L12835F/MX25L12845E/MX25L12865E" -p linux_spi:dev=/dev/spidev0.0,spispeed=30000 -w read1-10000-openwrt.bin
flashrom on Linux 4.19.75-v7l+ (armv7l)
flashrom is free software, get the source code at https://flashrom.org

Using clock_gettime for delay loops (clk_id: 1, resolution: 1ns).
Found Macronix flash chip "MX25L12835F/MX25L12845E/MX25L12865E" (16384 kB, SPI) on linux_spi.
Reading old flash chip contents... done.
Erasing and writing flash chip... Erase/write done.
Verifying flash... VERIFIED.

=== Flash using serial header access ===
Using small modifications to the radio, direct serial access allows temporarily running OpenWRT in memory and using the temporary environment to flash a full image to the radio's memory.

[[File:Ubnt_ns5acl_serial.jpg|thumb|Click to enlarge pinout]]
# Using your thumb or a small tool, push the tab in the slot located on the lower rear of the radio and slide the bottom half out of the enclosure
# Looking at the rear of the board (where all the components are on the opposite side as the antenna), locate the serial headers on the middle left side of the board
# Solder at least the top 3 pins shown in the picture. The pins from left to right (starting with the square shaped pad that is unpopulated in the image) are 3.3V, RX, TX, and GND. 3.3V is not needed here
# Connect GND on the board to GND on your FTDI adapter, TX on the board to RX on the FTDI adapter, and RX on the board to TX on the FTDI adapter
# Make sure your FTDI adapter is in 3.3V mode and attached to your computer, then open the serial port on your computer (ex. <code>minicom -D /dev/ttyUSB0</code>). Use 115200 8N1 in your terminal settings.
# Connect the NanoStation and press enter in the console when it says <code>Hit any key to stop autoboot:</code>. You should be left at a <code>ar7240> </code> prompt.
# Connect your laptop to the LAN port of the PoE injector powering the NanoStation and assign a static IP of <code>192.168.1.254</code>
# Install a TFTP server and place [https://downloads.openwrt.org/releases/19.07.0/targets/ath79/generic/openwrt-19.07.0-ath79-generic-ubnt_nanostation-ac-loco-initramfs-kernel.bin openwrt-19.07.0-ath79-generic-ubnt_nanostation-ac-loco-initramfs-kernel.bin] in the root folder of the TFTP server (<code>/srv/tftp</code> for tftp-hpa on Arch).
# Rename the initramfs-kernel.bin file to <code>1401A8C0.img</code> and ensure the tftp server / service is started
# Run <code>tftpboot</code> in the serial console and wait for it to complete
# Run <code>bootm</code> in the serial console to boot the initramfs
# Once OpenWRT has booted, you can press Enter to enable shell access
# Ensure you have an IP address in the 192.168.1.x subnet and use scp to transfer the sysupgrade firmware you wish to flash
# Flash the full firmware to the radio's storage using <code>mtd -r write /tmp/sysupgrade.bin firmware</code>, replacing <code>sysupgrade.bin</code> with the full filename of the firmware you are flashing

== Condensed Command-list ==
=== Flash The Stock Ubiquiti Firmware via TFTP ===
<pre>
wget https://dl.ubnt.com/firmwares/XC-fw/v8.5.0/WA.v8.5.0.36727.180118.1314.bin
cp https://dl.ubnt.com/firmwares/XC-fw/v8.5.0/WA.v8.5.0.36727.180118.1314.bin firmware.bin
sudo apt install tftp
tftp
tftp> connect 192.168.1.20
tftp> rexmt 1
tftp> timeout 60
tftp> binary
tftp> put firmware.bin
</pre>
=== Flash The Mass Mesh Firmware ===
<pre>
wget https://github.com/MassMesh/meta-imagebuilder-artifacts/raw/master/massmesh/meshradio/ubnt_nanostation-ac-loco/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin
scp openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin ubnt@192.168.1.20:/tmp
ssh ubnt@192.168.1.20
hexdump -Cv /bin/ubntbox | sed 's/14 40 fe fe/00 00 00 00/g' | hexdump -R > /tmp/fwupdate.real
chmod +x /tmp/fwupdate.real
/tmp/fwupdate.real -m /tmp/openwrt-massmesh-meshradio-ath79-generic-ubnt_nanostation-ac-loco-squashfs-factory.bin
</pre>

Ubiquiti NanoStation 5AC Loco

2020-01-27T06:42:32Z

Stephen304: Add serial console flash method

File:Ubnt ns5acl serial.jpg

2020-01-27T06:35:20Z

Stephen304:

Glossary Of Terms

2020-01-16T17:04:50Z

Stephen304: /* T */

= Glossary Of Terms =
== A ==
== B ==
== C ==
== D ==
== E ==
== F ==
* '''Firmware''' The software that runs on a specific piece of hardware is called firmware. Both the Mesh Node and Mesh Radio have a custom firmware that performs specific tasks and contains other software. Firmware commonly refers to the entire set of software running on a device, as opposed to one piece of it.
* '''Flash(ing)''' Refers to the process of writing a new firmware to a device. The process can be simple or complex depending on the manufacturer of the hardware.

== G ==
== H ==
== I ==
== J ==
== K ==
== L ==
* '''LAN:''' See Wikipedia: [https://en.wikipedia.org/wiki/Local_area_network Local Area Network]

== M ==
* '''Mesh Mode''' Refers to a mode of operation for wifi devices known as 802.11s that allows devices to talk directly to each other without an access point. This is similar to Ad-Hoc mode and allows devices to come in and out of range with each other while still allowing any device to talk to any other device.
* '''Mesh Network:''' A mesh network is a peer-to-peer network where there are multiple links between each Mesh Node.
* '''Mesh Node:''' Think of a mesh network as a graph. A mesh node is one 'vertex' on that graph. It's the combination of radios and single-board-computers you keep in your home in order to participate in your neighborhood network.
* '''Mesh Radio''' Each mesh node uses one or more mesh radios to communicate with other mesh nodes. For simplicity, the radio will sometimes be omitted from diagrams despite being a separate piece of hardware. The job of the mesh radio is to relay traffic between the ethernet plug on the mesh node and a meshing wifi signal.

== N ==
== O ==
== P ==
* '''Peer-to-Peer:''' Peer-to-peer computing or networking is a distributed application architecture that partitions tasks or workloads between peers. Peers are equally privileged, equipotent participants in the application. They are said to form a peer-to-peer network of nodes.
== Q ==
== R ==
== S ==
* '''Stock''' or '''Stock Firmware''' is used to describe the preloaded software that comes on a device when purchased from a store. Not all devices have a stock firmware, but it's important to be aware of those that do because flashing steps for our custom firmware can differ depending on whether a device is running stock or has already been flashed to our firmware.

== T ==
* '''TFTP''' Is a method of transferring files that is used by certain devices to receive firmware files.
* '''TFTP Mode''' Many devices feature a recovery mode that can be used to re-flash the device firmware. The software for this mode is separate from the firmware, so even when the device software breaks, TFTP Mode can usually be used to reset the main firmware. This mode is used for several devices for the flashing process.

== U ==
== V ==
== W ==
* '''WAN:''' See Wikipedia: [https://en.wikipedia.org/wiki/Wide_area_network Wide Area Network]

== X ==
== Y ==
* '''Yggdrasil''' The software and protocol we use for forming our mesh. To learn more, visit the [https://yggdrasil-network.github.io/ Yggdrasil Website]

== Z ==

Glossary Of Terms

2020-01-16T16:58:33Z

Stephen304: /* M */

= Glossary Of Terms =
== A ==
== B ==
== C ==
== D ==
== E ==
== F ==
* '''Firmware''' The software that runs on a specific piece of hardware is called firmware. Both the Mesh Node and Mesh Radio have a custom firmware that performs specific tasks and contains other software. Firmware commonly refers to the entire set of software running on a device, as opposed to one piece of it.
* '''Flash(ing)''' Refers to the process of writing a new firmware to a device. The process can be simple or complex depending on the manufacturer of the hardware.

== G ==
== H ==
== I ==
== J ==
== K ==
== L ==
* '''LAN:''' See Wikipedia: [https://en.wikipedia.org/wiki/Local_area_network Local Area Network]

== M ==
* '''Mesh Mode''' Refers to a mode of operation for wifi devices known as 802.11s that allows devices to talk directly to each other without an access point. This is similar to Ad-Hoc mode and allows devices to come in and out of range with each other while still allowing any device to talk to any other device.
* '''Mesh Network:''' A mesh network is a peer-to-peer network where there are multiple links between each Mesh Node.
* '''Mesh Node:''' Think of a mesh network as a graph. A mesh node is one 'vertex' on that graph. It's the combination of radios and single-board-computers you keep in your home in order to participate in your neighborhood network.
* '''Mesh Radio''' Each mesh node uses one or more mesh radios to communicate with other mesh nodes. For simplicity, the radio will sometimes be omitted from diagrams despite being a separate piece of hardware. The job of the mesh radio is to relay traffic between the ethernet plug on the mesh node and a meshing wifi signal.

== N ==
== O ==
== P ==
* '''Peer-to-Peer:''' Peer-to-peer computing or networking is a distributed application architecture that partitions tasks or workloads between peers. Peers are equally privileged, equipotent participants in the application. They are said to form a peer-to-peer network of nodes.
== Q ==
== R ==
== S ==
* '''Stock''' or '''Stock Firmware''' is used to describe the preloaded software that comes on a device when purchased from a store. Not all devices have a stock firmware, but it's important to be aware of those that do because flashing steps for our custom firmware can differ depending on whether a device is running stock or has already been flashed to our firmware.

== T ==
== U ==
== V ==
== W ==
* '''WAN:''' See Wikipedia: [https://en.wikipedia.org/wiki/Wide_area_network Wide Area Network]

== X ==
== Y ==
* '''Yggdrasil''' The software and protocol we use for forming our mesh. To learn more, visit the [https://yggdrasil-network.github.io/ Yggdrasil Website]

== Z ==