This project is still in its early stages, but the goal is to build a Raspberry Pi based MANET (Mobile Ad-Hoc Network) radio using a Wi-Fi HaLow module from Seeed. It is designed around Morse Micro based Pi HATs and other compatible SDIO boards.

A number of optional components are listed in the parts list below. Currently, I am testing a WaveShare 1850 UPS for power. The build includes drivers for the Panda Wireless PAU06 USB Wi-Fi adapter. The onboard Wi-Fi on most Raspberry Pis cannot be used for client networking in this setup because it shares the same SDIO address as the HaLow boards. You can use either the USB WiFi or the ethernet adapter on the RPI4 to bridge connectivity.

• Enclosure design
• Step-by-step setup guide
• Investigate USB OTG/Ethernet Gadget mode to allow EUDs to connect without USB-to-Ethernet adapters
• Test B.A.T.M.A.N. mesh networking

• GPS-based range-testing script using GPSD, logging GPS location, RSSI, and SNR for analysis
• PTT (Push-to-Talk) application so the radio is functional without an EUD
• Support for Seeed and other SDIO-based boards
• Raspberry Pi 3B+ and 2W support

• The BCF file is different, so the power goes from 21 dBm to 27 dBm
• The build is newer than the Seeed image
• The build includes 802.11s support
• 📄 Range Testing Results

1. Download the latest OpenMANET image Go to the Releases section: https://github.com/OpenMANET/openwrt/releases and download the image.

2. Flash the image to an SD card Use the official Raspberry Pi guide for instructions on flashing the image: https://www.raspberrypi.com/documentation/computers/getting-started.html

3. Initial connection When first powered on, the Pi boots with a static IP of 10.42.0.1. Connect your computer directly via Ethernet and set your computer to obtain an IP automatically. Your computer should get an IP address in that range from the Pi and you will be able to access the Pi at 10.42.0.1 in a web browser. The default username is root, and the default password is blank. If your computer is connected to WiFi, you can plug the RPI into your ethernet adapter, and still stay connected to the internet at the same time. Note the username is still root after running the initial wizard, and you will use the password you set.

4. Initial configuration Follow the steps in the Morse Micro EKH01 User Guide: https://www.morsemicro.com/wp-content/uploads/2024/12/MM6108-EKH01-Eval-Kit-User-Guide-v18.pdf It is recommended to complete Section 3.1 “Initial Setup” first, then Section 3.9 “802.11s Mesh Configuration” to establish your initial mesh link.

5. Switch to DHCP for normal operation After completing the initial configuration, OpenWrt will set the nodes to use DHCP. This allows the Pi to automatically obtain an IP address from any connected network without manual configuration. If you are using these in a disconnected environment, it may make sense to set static IP addresses on the radios, and your EUDs. Tested with a local home network and with a Starlink Mini providing DHCP.

When configuring 802.11s with Morse Micro, there are two main node types:

Think of a Mesh Gate as the “hub” of your mesh. It is the point where your next-hop connection (like an upstream internet connection or Starlink Mini) is attached. Mesh Gates have two operating modes:

• Bridged Mode Ethernet and the HaLow mesh are bridged together. The same IP range and the same DHCP server as the Ethernet side are used. This is useful when you want to extend an existing network — e.g., your home network or a Starlink Mini router.

• Router Mode The Mesh Gate acts as its own NAT router. The mesh network gets its own subnet, and traffic is NAT’d to the upstream network. The Mesh Gate also runs DHCP and DNS, allowing your Raspberry Pis to resolve each other by hostname. This option is best for disconnected environments where there’s no upstream network or internet.

A Mesh Point is a node that connects to the 802.11s mesh. It can bridge its Ethernet or 2.4/5 GHz Wi-Fi interface into the HaLow mesh. Recommendation: For the first-time setup, do NOT enable bridging on the Mesh Point. This makes it easier to confirm connectivity by checking the Mesh Gate first. Once you verify the Mesh Point is joining the mesh, rerun the wizard and enable bridging. If your node does not connect over Halow, you will not be able to connect without connecting physically.

The Mesh Point you will want to use bridge mode as well, so that you are on the same network as the other EUDs.

         (Upstream Router / Starlink Mini)
                     |
                [ Ethernet ]
                     |
          +----------------------+
          |  Mesh Gate (BRIDGED)|
          |  br-ahwlan: eth0+ah |
          +----------------------+
                    ))))))  802.11s  ((((((
             ________/         |            \________
            /                  |                       \
   +----------------+   +----------------+      +----------------+
   | Mesh Point A   |   | Mesh Point B   |      | Mesh Point C   |
   | (no bridge 1st)|   | (bridge later) |      | (bridge later) |
   +----------------+   +----------------+      +----------------+
        |     \               |     \                   |     \
    [EUD A]  [WiFi AP]   [EUD B]  [WiFi AP]       [EUD C]  [WiFi AP]

Notes:

• Same IP range as the upstream router.
• Upstream router’s DHCP server hands out addresses to both Ethernet and 802.11s clients (via the bridge).
• Useful for extending home/office networks or using Starlink Mini as the router.

       (Optional Upstream Router / Internet)
                     |
                [ Ethernet ]
                     |
          +------------------------------------+
          |  Mesh Gate (ROUTER / NAT / DHCP/DNS|
          |  LAN = 802.11s mesh subnet         |
          +------------------------------------+
                    ))))))  802.11s  ((((((
             ________/         |            \________
            /                  |                       \
   +----------------+   +----------------+      +----------------+
   | Mesh Point A   |   | Mesh Point B   |      | Mesh Point C   |
   | (bridge later) |   | (bridge later) |      | (bridge later) |
   +----------------+   +----------------+      +----------------+
        |     \               |     \                   |     \
    [EUD A]  [WiFi AP]   [EUD B]  [WiFi AP]       [EUD C]  [WiFi AP]

Notes:

• Mesh Gate supplies DHCP/DNS on the mesh subnet.
• Traffic from mesh NATs to the upstream (if present).
• Works well in disconnected/off-grid scenarios; clients still have local name resolution and services.

In situations without DHCP, you can configure static IPs. The DHCP range is 192.168.12.100 to 192.168.12.255, so make sure you assign your IPs outside of this range. I would start with 192.168.12.2.

• On your EUD (end-user device), assign a static IP in the mesh subnet to avoid losing connectivity if DHCP isn’t available.
• On your Raspberry Pi radios, go to Quick Config in the UI, and set a static IP on the ahwlan interface. You can find the currently assigned IP from your DHCP server and then convert it to static.

A range-test script is included in the scripts folder. It uses the GPS module listed in the parts list to measure ping, RSSI, and SNR. You can use SCP to transfer the file to the pi.

To use it:

cp scripts/rangetest.sh /root/
chmod +x /root/rangetest.sh

It is recommended to run it inside tmux so it continues running even if you disconnect.