The Seeed box showed up, the radios went on the HATs, and I now have a working two-node OpenMANET mesh on the bench with push-to-talk voice crossing the HaLow link. If you’re following along, this is where the phase 1 parts turn into an actual network. Notes below, including the dumb mistake.
Bringing up the OpenMANET mesh
Both nodes run OpenMANET 1.8.0. The setup wizard walks you through the HaLow settings, and you decide each node’s job:
- Node 1: mesh gate (router mode). It lands at
10.41.0.1and is the node that would NAT the mesh onto an uplink. - Node 2: bridge mode. A plain mesh node with its own access point and Ethernet.
The mesh settings have to match exactly on both nodes: mesh ID, channel, bandwidth and passphrase. If they don’t, nothing finds anything.
The ten-minute mistake
Node 2 came up, and its dashboard said 0 connected mesh nodes. I checked antennas. I re-read the wizard summary. I started comparing wireless settings.
Node 1 was turned off.
Powered it back on, waited two or three minutes, refreshed, and the counter went to 1. In my defense, there’s a real thing that makes this confusing: on a fresh install a node starts on a temporary address, picks a permanent one after about two minutes, and reboots. Sometimes the mesh link only comes up after that reboot. So give it a few minutes before you start troubleshooting. And make sure the other node is on.
How I knew it was really working
Laptop plugged into node 2’s Ethernet, browser pointed at http://10.41.0.1, node 1’s dashboard loads. Node 1’s own access point showed zero clients, so that page had to come across the radio: laptop → node 2 → HaLow → node 1. That’s the moment it stops being a pile of boards and becomes a network.
First link numbers
With the nodes a few feet apart, this is the bench baseline I’ll compare against once we go out for range testing:
| Measurement | Value |
|---|---|
| Signal | −36 dBm |
| Noise floor | −87 dBm |
| Margin | about 51 dB |
| Rate | MCS 7 at 2 MHz (top rate for that width) |
| Throughput shown | 7.5 Mbps |
| Encryption | WPA3-SAE |
Fifty-one dB of margin at arm’s length is exactly what you’d expect. The interesting number will be how fast that shrinks across the property.
Housekeeping before anything else
- Hostnames. I named them
manet01andmanet02. Node addresses move around while auto-addressing settles, so usemanet02.localinstead of chasing IPs. - Root passwords on both nodes: System → Administration. Different from the mesh and Wi-Fi passphrases.
- Replace the default mesh passphrase. This one has an order to it, because the moment one node changes its key it drops off the mesh.
Swapping the mesh passphrase without locking yourself out
Change the node you’re plugged into first, then reach the other node over its own Wi-Fi and change it. You’re always directly connected to the node you’re editing, so neither drops you mid-save.
- Turn on Advanced Config, go to Network → Wireless, and edit the HaLow Mesh Point entry (not the access point entry).
- On the Wireless Security tab, replace the key, then Save and Save & Apply. That node drops off the mesh, which is expected.
- Join the other node’s access point, browse to it, and repeat with the exact same passphrase.
- Wait a minute and check that the dashboard shows 1 connected mesh node again.
If LuCI warns it’s about to roll back because it lost contact, choose “Apply unchecked.” With this order you shouldn’t see it.
Push-to-talk across the OpenMANET mesh
This is the part I actually wanted. OpenMANET’s comms run Opus voice over multicast, organized into talk groups, and a phone’s web browser can act as the radio’s audio. No app to install.
The important bit: each device has to be on a different node, otherwise you’re just testing Wi-Fi in one box. My setup was the phone on node 1’s access point and the desktop on node 2’s Ethernet, so the audio has to ride HaLow.
- On each node, open the OpenMANET web app on port 8080 (separate from the LuCI pages), go to Settings → General, set Comms Radio to Enabled and Control Source to Web UI, and save. This is per node; it doesn’t carry over.
- On each device, open the HTTPS version on port 8081 and accept the self-signed certificate. Browsers only allow microphone access over HTTPS.
- Open the Comms page, allow the mic, and make sure both devices have RX and TX on for the same channel.
- Hold the big PTT button on one and talk.
It works. Voice out of the desktop, keyed from the phone, across the mesh.
Gotchas I hit
- Make sure the device is actually on the mesh. My desktop first reached node 1 through my home network (a
192.168.x.xaddress) instead of the mesh. You need a10.41.x.xaddress. Runipconfigand check. - If the mic meter doesn’t move when you talk, that browser doesn’t have mic access. Usually it’s because you’re on port 8080 instead of 8081.
- Separate the devices, or use earbuds on one, or you’ll get feedback squeal.
- While you’re in there, the Comms page has offline speech-to-text, and there’s a Topology page that draws the mesh.
What’s next
- A real channel knob. The five channels on the Comms page are talk groups, each with its own send/receive switch, and openmanetd lets other programs flip them through its API. I want a detented rotary switch (a binary-coded one only needs 3–4 wires) wired straight to the Pi’s GPIO, with a small service that turns “position 3” into “talk and listen on channel 3.” The catch is the WM1302 HAT covers the 40-pin header, so that means a stacking header and checking which pins are free. Long term, the knob, PTT and audio go on the CM4 carrier as the radio’s front panel.
- ATAK. The data side clearly works, so position sharing and map markers are next.
- Batteries and a range walk, then the 5 GHz dual-band experiment.
Two nodes on a bench isn’t a tactical radio yet. But it’s a real mesh, it carries voice, and every node I build from here has to keep doing exactly this.
The OpenMANET build log
- Part 1: What OpenMANET is (and why I’m building one)
- Part 2: The dual-band, CM4 and handheld plan
- Part 3: Phase 1 parts list
- Part 4: Two-node mesh up, push-to-talk working (you are here)
- Part 5: The handheld, rendered
- Part 6: A printable Pi 4 test stand
- Part 7: 5 GHz on the mesh
References
—
TL;DR: Two Pi 4 nodes, one HaLow mesh at −36 dBm with a 51 dB margin, WPA3 encrypted, and browser push-to-talk working across it. Give new nodes a few minutes to settle, change the mesh passphrase in the right order, and make sure both nodes are actually turned on.


Pingback: OpenMANET: A Wi-Fi HaLow Mesh Radio Worth Building | Signals & StaticSignals & Static
Pingback: The OpenMANET Handheld, Rendered: A CM4 Concept in FreeCAD | Signals & StaticSignals & Static