Differences

This shows you the differences between two versions of the page.

--- ham_radio:aredn_-_mesh_networking [2019/05/21 22:40] – [Mikrotik] localadmin
+++ ham_radio:aredn_-_mesh_networking [2022/03/18 13:51] (current) – jon
@@ Line 3: / Line 3: @@
 ===== Overview =====
+AREDN Mesh Networking evolved out of Broadband Hamnet, which was the originator of this concept. Everything is based off of the OpenWRT platform, which supercharges your basic commercial wireless router.
+There is a variant called HamWAN that started up in the Seattle-Tacoma area.
+Hams have access to:
+  * 2.300-2.310 GHz
+  * 2.390-2.450 GHz
+  * 3.300-3.500 GHz
+  * 5.650-5.925 GHz
+  * And much higher frequencies
+In the 2.4 Ghz range, amateur use bleeds into the commercial channels 1-6, but power usage can be more than what commercial part 15 devices can transmit. With AREDN, you can also have access to channels -1 and -2 which bring the center frequency below the commercial spectrum to avoid interference.
+Line of sight is crucial in these applications. The Fresnel zone will be the determining factor of making a connection to another station.
+Several companies make devices that operate in these frequencies, but custom firmware is used to make the device custom-tailored to amateur use.
 ===== Recommended Gear =====
+A good starting point would be AREDN's recommended device list here: https://www.arednmesh.org/content/supported-platform-matrix
+Predominantly, Ubiquiti, Mikrotik, and TP-Link devices are compatible.
 ===== Setup - Flashing Devices =====
@@ Line 20: / Line 39: @@
   - Within the folder where you have installed the pxe server, open the config.ini file into notepad. Underneath the line that says {dhcp} add a line as follows: <code>RFC951=1</code>
   - Save and close the config.ini file
-  - From the following link, download the following two files:<code>aredn-556-d188fcf-mikrotik-vmlinux-initramfs.elf</code> and the file the firmware file appropriate to your device which in this case will have 'AC' in it. <code>aredn-556-d188fcf-mikrotik-rb-nor-flash-16M-ac-sysupgrade.bin</code>
+  - [[http://downloads.arednmesh.org/snapshots/trunk/targets/ar71xx/mikrotik/|From the following link]], download the following two files:<code>aredn-xxx-xxxxxxx-mikrotik-vmlinux-initramfs.elf</code> and the file the firmware file appropriate to your device which in this case will have 'AC' in it. <code>aredn-xxx-xxxxxxx-mikrotik-rb-nor-flash-16M-ac-sysupgrade.bin</code>
   - Save these files into a folder named firmware on your desktop so that you know where to find them later.
   - Configure computer’s Ethernet device: <code>IP - 192.168.1.10</code> <code>Subnet Mask - 255.255.255.0</code>
@@ Line 47: / Line 66: @@
 Default credentials are root/hsmm - https://www.arednmesh.org/content/default-username-password
+===== Software to add to Mesh Network =====
+==== MeshChat ====
+Software and details can be found here:
+http://www.trevorsbench.com/meshchat-messaging-for-mesh-networks
+You can install on a node, such as the hAP AC Lite, but it's preferable to install on a Debian Linux-based device, such as a Raspberry pi, or a converted thin client, such as a Dell Wyse 3040. After installing the software package, you will need to modify the systemd startup for apache2, so that the /tmp folder is not set to private for use with apache. If the systemd file is not in /etc/systemd/system, copy it over from /lib/systemd/system and change the PrivateTmp property to 'false' instead of 'true'. Furthermore if you have issues, open up the permissions on /tmp/meshchat/lock from 640 to 666.
+<note important>Don't forget, when you modify a systemd file, you will need to run systemctl daemon-reload to have the changes take effect</note>
+Source:
+https://www.arednmesh.org/content/pi-meshchat-error-sending-message