Path finding over lora mesh #466
-
Starting this thread to carry on the discussion about path requests not being re-broadcast over the same interface that they were received on. This presents a fundamental challenge of not being able to reliably perform path-finding over a LoRa mesh. This severely limits the usefulness of Reticulum over a mesh network since all destinations more than 1 hop away would essentially remain un-routable to any newly joining node.
I assume that by "an established transport node available nearby" you mean as a direct neighbor, right? What if your neighbor is not established either, or only semi-established? This would be the nature of a mesh in the real world (even if nodes are stationary), yes? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
The keys and path to a destination can be requested from any connected Transport Node if your node does not have an announce from that destination.
No. A transport is just any node that routes traffic and stores announces. By “established” Mark means that is has been on long enough to receive the announce for the destination you are trying to reach. This can actually be any transport node on the entire network, just as long as you’re able to connect to it. Please read this for more information: https://reticulum.network/manual/understanding.html |
Beta Was this translation helpful? Give feedback.
The keys and path to a destination can be requested from any connected Transport Node if your node does not have an announce from that destination.
No node has a map of the complete network it is connected to, instead simply storing the next hop to the destination for every endpoint.
No. A transport is just any node that routes traffic and stores announces. By “established” Mark means that is has been on long enough to receive the announce for the destination you are trying to reach. This can actually be any transport node on the entire network, just as long as you’re able to connect …