Anyone,
I don't understand how routing occurs between AREDN nodes.
Example -- Nodes online and stable for a day
Route NOT selected by originating node: Node A <---Tunnel---> Node B <-----Dtd----> Node C <---RF---> Node D Total time ~50 ms to destination
Route selected by originating node: Node A <----RF----> Node B <---Dtd---> Node C <----RF----> Node D <----RF----> Node E <----RF---> Node F <--- and so on for a total of 9 nodes Total time ~700 - 1000 ms to destination
Why does a node not select the fastest route; it seems to be beyond all logic?
73,
Tom - KB7HTA
I don't understand how routing occurs between AREDN nodes.
Example -- Nodes online and stable for a day
Route NOT selected by originating node: Node A <---Tunnel---> Node B <-----Dtd----> Node C <---RF---> Node D Total time ~50 ms to destination
Route selected by originating node: Node A <----RF----> Node B <---Dtd---> Node C <----RF----> Node D <----RF----> Node E <----RF---> Node F <--- and so on for a total of 9 nodes Total time ~700 - 1000 ms to destination
Why does a node not select the fastest route; it seems to be beyond all logic?
73,
Tom - KB7HTA
I think:
Each link has a value:
Wire or internet connections have a value 0.1.
RF has a value 1.0.
The route chosen is the path with the lowest sum of values.
73, Chuck
DtD links have a static weight of 0.1
RF links are dynamic.
For the sake of argument, let's give all the RF links a value of 1, excellent links.
The first example would have an ETX of 2.1
The second example would have an ETX of 8 or 9. Connections should have gone out the first example, but don't.
Prometheus / Grafana shows your tunnel is not stable, going off line quite often. Prometheus / Grafana polls every 60 seconds, so it's possible you're off line more often. My guess would be your tunnels erratic behavior is messing up your routing.
Richard ko0ooo