Skip to content

News

Please configure regions

Things are moving fast in the mesh, again!

A new regions proposal came out of MeshCore Canada. We think all repeaters in the Quebec province should adopt it to reduce cross-region flooding. It is a phased proposal that, at first, will not have significant impact on any user except for multi-city traffic, as it will separate Quebec from Montreal, unless a region is used on messages.

Ottawa has already started deploying this and has already separated themselves from the Montreal mesh through this mechanism.

For a repeater in the city, in or around Montreal, please perform the following configuration:

region def yul|* qc|* onqc|* can|* na
region allowf *
region default yul
region save

Other configurations are required for repeaters in Quebec, and edge repeaters between the cities.

See below for further examples and explanations!

New nodes showcase, mirrors, and theme

A quick word to announce the new nodes section which features repeaters. There is one page per operator, and currently only one operator, but more are welcome!

And speaking of which, a new set of mirrors has been opened. The source code for the site is visible at:

We prefer contributions to come in to Codeberg, but following our spirit of universality and reducing friction for contributions we also accept contributions from the other sites. A more detailed justification of the GitHub is visible here.

Finally, this was done by some work on the site's template, which was made possible by a switch from the old mkdocs-material to Zensical engine. This changed the theme header and some fonts, but the site is mostly similar. The only change is that the git-based change date has been removed while Zensical implements the missing functionality.

Please limit adverts, loops and floods

Things are moving fast in the mesh!

After discussion and testing with key operators in Montreal and its greater area, we strongly encourage you to make the following changes to your repeaters:

On the command-line, the equivalent is the following commands:

set loop.detect moderate
set advert.interval 240
set flood.advert.interval 47
set flood.max 16

For repeaters with many neighbors (30-50), we also advise raising txdelay

Equivalent commands:

set txdelay 1
set direct.txdelay 0.5

We do not currently have a recommendation on changing rxdelay.

Please use 3 bytes routing

In August, many repeater operators in the greater Montreal area started experimenting with multi-byte path routing. We now strongly recommend that you configure your repeaters (and companions) to use multi-byte routing, particularly if you have trouble with direct messages or remotely operating a repeater.

One-byte repeaters are also at risk of being dropped from the MeshMapper map. The new "Canada" preset should configure your devices correctly.

This announcement explains how to configure your devices and why we are making this change.

Fire hazard on the WisMesh Pocket

link text
A WisMesh Pocket V2
the bottom right of the perforated battery
Perforated battery pouch with a bulge

This is a public service announcement concerning the WisMesh Pocket V2 as sold by RAK Wireless. We have on-hands experience with two devices that exhibit premature wear and tear of the battery pouch due to what seems to be a design flaw.

Warning

We have reasons to believe WisMesh Pocket V2 devices present a fire hazard and need to be immediately inspected for internal damage.