Getting into AREDN is easier than it used to be, but there are still enough small choices and gotchas that a practical checklist is useful. This is based on getting a node connected to the JFMDNA mesh in the Montgomery County area.
Hardware choices
AREDN supports a range of Ubiquiti and Mikrotik hardware. For a first node, the most commonly recommended starting points:
- Mikrotik hAP ac lite — inexpensive indoor unit, useful as a “tunnel node” or for connecting local devices to the mesh at a fixed site. Not for outdoor RF links.
- Ubiquiti NanoStation M5 or AC — the workhorse outdoor unit for neighborhood-scale links. Good for paths up to a mile or two with reasonable line-of-sight.
- Ubiquiti Rocket M5 with a sector or dish — for backbone links or connecting over longer distances. What the anchor sites in the JFMDNA mesh use.
Before buying anything, check the live mesh map to see where existing nodes are. Your hardware choice depends on what you can reach from your location and at what distance.
Flashing AREDN firmware
- Download the correct firmware image for your specific hardware model from arednmesh.org/content/downloads — model variants matter, the wrong image bricks the device.
- Follow the AREDN flashing guide for your hardware. Ubiquiti devices can usually be flashed through the stock web UI if they’re on older firmware, or via TFTP if needed. The AREDN docs cover both paths.
- After flashing, the node comes up on 192.168.1.1. Configure node name (use your callsign — e.g., WB3CQK-NODE1), channel, and mesh SSID. For the JFMDNA area, coordinate channel selection with other local node owners to avoid interference.
Joining the JFMDNA mesh
Once your node is on the air, getting it connected to the five-county mesh is a matter of either:
- Direct RF link — if you can see another mesh node from your location (check the map, run a path analysis with the AREDN link calculator), a direct RF connection is always preferred over a tunnel
- AREDN tunnel — if you don’t have RF line-of-sight to any existing node, AREDN supports tunneling over a regular internet connection. It’s not ideal (the whole point of AREDN is infrastructure independence) but it gets your node participating in the mesh and its services while you work toward an RF link
Reach out through jfmdna.org to connect with local mesh members who can help with channel coordination, tunnel setup, and site surveys for RF links.
Before your first activation
A mesh node you’ve never tested under load in field conditions is a liability, not an asset. Run a drill on your setup before you count on it: deploy the node in field conditions (battery power, outdoor enclosure, portable mast), connect a service (even just MeshChat), and push actual traffic through the link. The things that go wrong during drills are much cheaper than the things that go wrong during activations.