Initial Setup

This page walks you through downloading, flashing, and configuring the OpenMANET image on your Raspberry Pi HaLow HATs, plus initial mesh configuration tips and topology examples.

Setup Steps

  1. Download the latest OpenMANET image
    Go to the Releases section: 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:
    Raspberry Pi Getting Started Guide

  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: after running the initial wizard, you will use the password you set.

  4. Initial configuration
    Follow the steps in the Morse Micro EKH01 User Guide:
    MM6108-EKH01 User Guide 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.

    Reboot the Pi after flashing the image to fix multicast issues

  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.

  6. Optionally set up batman-adv
    batman-adv is a layer 2 mesh routing setup that is self-healing and optimizes connectivity between multiple mesh nodes and gateways.
    Setup batman-adv

Mesh Gate vs. Mesh Point

When configuring 802.11s with the Seeed HaLow HAT, there are two main node types:

Mesh Gate

Think of a Mesh Gate as the “hub” of your mesh. It’s 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.

Mesh Point

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.
Later, you can enable bridge mode so you’re on the same network as other EUDs.

Topology Examples (ASCII Diagrams)

A) Mesh Gate in BRIDGED Mode (extending an existing network/DHCP) 

             (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.

B) Mesh Gate in ROUTER Mode (own subnet, NAT to upstream, works offline) 

           (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.

Notes for Disconnected Environments

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. 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.

GPS Range Testing Script

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.

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.

Parts List

Item Link Optional
Wio WM6180 Wi-Fi HaLow mini PCIe Module https://www.seeedstudio.com/Wio-WM6180-Wi-Fi-HaLow-mini-PCIe-Module-p-6394.html No
WM1302 Pi Hat https://www.seeedstudio.com/WM1302-Pi-Hat-p-4897.html No
External Antenna 868/915 MHz 2 dBi SMA L195 mm Foldable https://www.seeedstudio.com/External-Antenna-868-915MHZ-2dBi-SMA-L195mm-Foldable-p-5863.html No
UF.L to SMA-K 1.13 mm 120 mm Cable https://www.seeedstudio.com/UF-L-SMA-K-1-13-120mm-p-5046.html No
Raspberry Pi 4 Computer Model B – 1 GB https://www.seeedstudio.com/Raspberry-Pi-4-Computer-Model-B-1GB-p-4078.html No
21700 Batteries https://www.amazon.com/dp/B0D3GX96H6?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_4 Yes
WaveShare UPS B https://www.amazon.com/gp/product/B0D39VDMDP/ref=ox_sc_saved_title_1?smid=A3B0XDFTVR980O&psc=1 Yes
Panda USB Wi-Fi Adapter (PAU06) https://www.amazon.com/dp/B00762YNMG?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_1 Yes
GPS USB Adapter https://www.amazon.com/dp/B01MTU9KTF?ref_=ppx_hzsearch_conn_dt_b_fed_asin_title_1 Yes

Project Photos

Setup photo 1
Setup photo 2
Setup photo 3
Setup photo 4