How Messages Move

When a message is sent across a Meshtastic network, it usually travels entirely over radio, hopping from node to node without any central server. There are no traditional routing tables and no guaranteed path. Instead, messages spread outward according to a small set of rules that decide who repeats them and when. If MQTT is enabled, internet-connected nodes can bridge radio traffic between distant regions, but once a message enters a local mesh it still follows the same rebroadcast behavior. Understanding these rules explains why a message might travel five hops and 169 miles, why some packets disappear, and why router placement, hop limits, and antenna upgrades matter.

Here’s what you actually need to understand.

1. Hop Limit

You’ve already played with this.

If hop limit is 5:

A message can be repeated up to 5 times.

More hops = more reach

More hops = more congestion

You set λlambda-base to 5 hops.

That affects network behavior.

⸻

2. Rebroadcast Delay

Nodes don’t all repeat instantly.

They wait random milliseconds.

Stronger signal nodes often win.

Weaker ones cancel their repeat if they hear it first.

This prevents echo storms.

⸻

3. Message IDs

Every message has a unique ID.

Nodes remember IDs briefly so they don’t rebroadcast the same message twice.

That’s why flooding is “managed.”

⸻

4. Router vs Client Roles

Your Heltec is a ROUTER.

Routers:

• Stay awake
• Repeat aggressively
• Strengthen the mesh

Your T-Beam:

• May sleep
• Is mobile
• Not meant to be backbone

That role distinction directly interacts with the mesh algorithm.

⸻

5. Time To Live (TTL)

Every message carries a counter.

Each time it’s repeated:

That counter decreases.

When it hits zero:

The message dies.

That’s how the network prevents messages from circulating forever.

Hop limit defines the ceiling.

TTL enforces it in practice.

⸻

6. Airtime & Congestion

LoRa is slow compared to Wi-Fi.

More hops means:

• More airtime used
• More channel occupation
• Higher chance of collisions

If too many nodes transmit at once:

Packets collide.

Some messages are lost.

More power is not always better.

More hops is not always better.

⸻

7. Node Memory Window

Nodes remember recently seen message IDs for a short period.

If they hear the same ID again:

They ignore it.

That memory window is temporary.

After it expires, the node forgets.

Sometimes delayed repeats won’t propagate.

Sometimes stale nodes behave oddly.