AREDN: Difference between revisions
Brian Wilson (talk | contribs) mNo edit summary |
Brian Wilson (talk | contribs) mNo edit summary |
||
| Line 3: | Line 3: | ||
Main page is at https://arednmesh.org/ | Main page is at https://arednmesh.org/ | ||
The nearest neighbor for me is the Willamette Valley Mesh Network. | The nearest neighbor for me is the [https://willamettevalleymesh.net/ Willamette Valley Mesh Network]. | ||
== Building an Internet-only node == | |||
=== on a Virtual Machine === | |||
Officially they support ProxMox (don't have one), VMWare ($) and QEMU. Setting up to run in VirtualBox was easy enough, now I just have to sort the networking out. | |||
2024-12-07 | 2024-12-07 | ||
* Downloaded the x86 version from https://downloads.arednmesh.org/afs/www/ ( | * Installed VirtualBox on [[Murre]]. | ||
* Converted the img file to a vdi using VboxManage. Takes about a second. | * Downloaded the x86 version from https://downloads.arednmesh.org/afs/www/ (look for "x86" in Model) | ||
* Converted the img file to a vdi using VboxManage. Takes about a second with this command. | |||
VBoxManage convertfromraw --format VDI aredn-3.24.10.0-x86-64-generic-ext4-combined.img aredn-3.24.10.0-x86-64-generic-ext4-combined.vdi | VBoxManage convertfromraw --format VDI aredn-3.24.10.0-x86-64-generic-ext4-combined.img aredn-3.24.10.0-x86-64-generic-ext4-combined.vdi | ||
Converting from raw image file="aredn-3.24.10.0-x86-64-generic-ext4-combined.img" to file="aredn-3.24.10.0-x86-64-generic-ext4-combined.vdi"... | Converting from raw image file="aredn-3.24.10.0-x86-64-generic-ext4-combined.img" to file="aredn-3.24.10.0-x86-64-generic-ext4-combined.vdi"... | ||
| Line 23: | Line 29: | ||
* Rebooted. Now there are services on port 80 and 8080 but not reachable (?). | * Rebooted. Now there are services on port 80 and 8080 but not reachable (?). | ||
==== Sorting out the networking ==== | |||
Documentation on the network interfaces is here. [https://docs.arednmesh.org/en/latest/arednHow-toGuides/home-router-connection.html How to guides: Home Router] | |||
The crucial part I missed is that it sets up its '''WAN port''' as the place it will connect to your network. From its perspective this makes perfect sense. The AREDN network is the LAN and the outside world is the WAN. Well maybe that makes sense. I mean, my network is how it will reach the Internet. If I put a radio on one of its LAN ports, that's where the mesh network would be. | |||
Out of the (virtual!) box it has DHCP enabled on WAN. | |||
== Build your own == | == Build your own == | ||
| Line 28: | Line 41: | ||
I installed docker on [[Murre]] for this. | I installed docker on [[Murre]] for this. | ||
== Resources == | |||
Go to https://arednmesh.org/ for information on the big project; if you accidentally go to https://aredn.org/ you will see a long manifesto about trademarks, whew. Glad I missed all that. | |||
[[Category: Network]] | [[Category: Network]] | ||
[[Category: Wireless]] | [[Category: Wireless]] | ||
Revision as of 00:35, 12 December 2024
"Amateur Radio Emergency Digital Network" or some such. They pronounce this "ARRR DIN" like a pirate. I want to call it "ARR-AH-DIN". Too bad for me.
Main page is at https://arednmesh.org/
The nearest neighbor for me is the Willamette Valley Mesh Network.
Building an Internet-only node
on a Virtual Machine
Officially they support ProxMox (don't have one), VMWare ($) and QEMU. Setting up to run in VirtualBox was easy enough, now I just have to sort the networking out.
2024-12-07
- Installed VirtualBox on Murre.
- Downloaded the x86 version from https://downloads.arednmesh.org/afs/www/ (look for "x86" in Model)
- Converted the img file to a vdi using VboxManage. Takes about a second with this command.
VBoxManage convertfromraw --format VDI aredn-3.24.10.0-x86-64-generic-ext4-combined.img aredn-3.24.10.0-x86-64-generic-ext4-combined.vdi Converting from raw image file="aredn-3.24.10.0-x86-64-generic-ext4-combined.img" to file="aredn-3.24.10.0-x86-64-generic-ext4-combined.vdi"... Creating dynamic image with size 126353408 bytes (121MB)...
- Create in a vbox machine (128MB RAM, 2 CPUs), remove the IDE controller, and add a second network adapter and set it to Bridged mode
- Launch the machine.
- It shows a hostname of NOCALL, it is possible to set a hostname using "W6GKD-astoria", like this, but this is the wrong thing. Instead run "/usr/local/bin/firstuse-setup W6GKD-astoria" and that will set the hostname and do other as-yet unspecified stuff. I chose the name based on their rules which say make the callsign all caps.
uci set system.@system[0].hostname='W6GKD-astoria' uci commit system /etc/init.d/system reload
- Reboot. This gets me some IP addresses in /etc/hosts. Funky ones.
- In the console, entered commands to set br-lan to DHCP and rebooted. That got me a usable IP address on my lan.
- Connected with password "hsmm" using ssh -p 2222 [email protected]
- Rebooted. Now there are services on port 80 and 8080 but not reachable (?).
Sorting out the networking
Documentation on the network interfaces is here. How to guides: Home Router
The crucial part I missed is that it sets up its WAN port as the place it will connect to your network. From its perspective this makes perfect sense. The AREDN network is the LAN and the outside world is the WAN. Well maybe that makes sense. I mean, my network is how it will reach the Internet. If I put a radio on one of its LAN ports, that's where the mesh network would be.
Out of the (virtual!) box it has DHCP enabled on WAN.
Build your own
Source code is in github https://github.com/aredn/aredn
I installed docker on Murre for this.
Resources
Go to https://arednmesh.org/ for information on the big project; if you accidentally go to https://aredn.org/ you will see a long manifesto about trademarks, whew. Glad I missed all that.
