MeshCore Western Australia

Community-run off-grid messaging network for WA.

⚠️ Network Migration: 2-Byte Prefix Change

Effective Date: 21st of June 2026

As the Meshcore Western Australia network scales, we are transitioning to a 2-byte prefix structure to expand our available address space, improve routing efficiency, and prevent node ID collisions.

Configuring 2-Byte Path Hash

To set the path hash mode to 2 bytes on your repeater, execute the following CLI command:

set path.hash.mode 1

📱 Companion Device Notice: Ensure your companion applications, client nodes, and administration tools are updated to support 2-byte prefix decoding before the migration date to maintain visibility and connection to updated hardware.

Note: Remember to commit your changes, restart your node, do a time sync and do a flood advert prior to June 21st to ensure uninterrupted connectivity with the WA mesh.

Current MeshCore Settings

🔧 Initial Repeater Configuration

Setting up a new Western Australia Meshcore repeater? Connect to your node via your serial console or administration interface and follow this guide to apply optimal network settings.

1. One-Time Node Configuration

Copy and paste this block into your CLI terminal. This enables power management, optimizes beacon intervals, and enforces the required 2-byte path hash mode:

powersaving on
set advert.interval 60
set flood.advert.interval 12
set path.hash.mode 1
reboot

Note: The reboot command is required to commit these settings to persistent memory. Default parameters (such as 0.5s TX delays, 600s AGC intervals, and hardware RX gain) are omitted here for simplicity as they are active by default in the firmware.

2. Clock Synchronization (Mandatory After Reboot)

Upon rebooting, your hardware clock will reset to firmware defaults. Because network advertisements will fail if your clock is wrong, you must synchronize it to UTC:

clock
clock sync

Verify that the output of clock sync displays the current correct date and time (UTC).

3. Network Verification & Diagnostics

Once configured and synced, broadcast your presence to neighboring nodes and verify your connection to the WA mesh topology:

advert
advert.local
discover.neighbors
neighbors

4. Companion App Setup

If you connect a phone or client device to your node via Bluetooth or web interface, you must configure the companion software environment to align with 2-byte routing parameters:

Quick links

Status

This site is under construction. Community volunteers welcome.