Latest changes

Current settings

Summary of Meshpot settings to apply today. Repeater firmware ≥ 1.16.0 required.

Key points

• Allowed region tree (including neighbouring regions and countries)
• Repeater transmit scope: region default be
• Home: be-bru in Brussels; Walloon province (be-wlg…) in Wallonia
• Priority: unscoped flood still allowed (region allowf *); ceiling flood.max.unscoped 64 (default). No denyf *.
• 2-byte path hash (set path.hash.mode 1)

Companion

Radio preset

EU/UK (Narrow)

Regional channel

#brussels

Path hash size

2 bytes

App detail: Join · companion.

Repeater (CLI)

Enter each command one at a time. Wait for OK before the next.

Regions (CLI)

Firmware ≥ 1.16.0 required for region def. Transmit scope: region default be everywhere (Brussels and Wallonia). Home: be-bru in Brussels; province in Wallonia. The tree includes be-wal and be-vlg. Keep allowf *. Hainaut: see the #BEmesh configurator.

Local public channels: #brussels, #liege, #namur…

Companion setup · Advanced settings · Regional filtering

History

Milestones behind the recommendations above. Meshpot does not adopt every #BEmesh rule: some do not fit Brussels yet.

1. October 2026

   Meshpot now includes the Wallonia region (be-wal in the region def tree), with CLI tabs per province (home = province). Transmit scope stays region default be (Belgium): still the most effective in Brussels and Wallonia; switching to a region/province default comes later. See the Regions (CLI) tabs.

2. September 2026

   #BEmesh SYSOPS: initiative to involve repeater admins in config changes (mailing list, SYSOPS Discord for RRY members, info-only WhatsApp channel). Reminder: owner info filled in, firmware ≥ 1.16, 2-byte path hash, be scope on the #BEmesh side. Meshpot does not change its settings (unscoped / ceiling 64).

3. September 2026

   Liège Hackerspace wiki — MeshCore: local French-language documentation (config, web resources).

4. August 2026

   Fanjoe’s analysis: applying #BEmesh literally during the transition (repeaters without a region table + hardened unscoped) breaks reach. We mainly keep relaying unscoped traffic (allowf *, ceiling 64), while scoping repeaters to be.

5. August 2026

   In Brussels the mesh is still nascent: we build the region table, scope repeaters to be, and keep relaying unscoped traffic (region allowf *, ceiling 64). Repeater firmware ≥ 1.16.0 required.

6. 1 August 2026

   #BEmesh announces flood / regions / unscoped (Radio-Actief, guidance). We do not yet adopt denyf * or a low unscoped ceiling; we scope repeaters to be while keeping unscoped relay.

7. June 2026

   #BEmesh pushes 2-byte path hash, following the April firmware roll-out. Brussels adopts set path.hash.mode 1 (and the companion equivalent).

8. April 2026

   #BEmesh aligns repeaters on firmware ≥ 1.14 (multibyte path hashes). Prerequisite for the June 2-byte path hash move.

9. March 2026

   Alex documents early Belgian guidance to standardise regions (ISO 3166-1 / ISO 3166-2, aligned with NL). Cutting traffic without a region was still planned for later; he already insists on keeping unscoped flood (*^ F) while region tables roll out.