Reticulum Transport & Routing FAQs

Question 1

What is the difference between a Reticulum Instance and a Transport Node?

Accepted Answer

A standard Reticulum Instance can send and receive packets but does not forward traffic. A Transport Node has transport enabled, allowing it to forward packets and announces for other nodes, acting as a router.

Question 2

How does Reticulum handle path resolution for unknown destinations?

Accepted Answer

When a destination is not in the path table, the node broadcasts a path request. Transport nodes with knowledge of that path respond with an announce, allowing the requestor to update its local path table.

Question 3

What are the limitations on hop counts in Reticulum?

Accepted Answer

Reticulum uses the PATHFINDER_M constant, which defaults to 128 hops. This is the absolute maximum a packet can traverse before being dropped, preventing infinite loops and bounding convergence time.

Question 4

How does the transport layer manage bandwidth for announces?

Accepted Answer

Each interface typically allocates a small percentage (default 2%) of bandwidth for announce processing, prioritizing local (low hop count) announces and using queuing to manage high traffic.

Reticulum Transport & Routing

Key Features

Use Cases

Reticulum Transport & Routing

Key Features

Use Cases