You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In in /www/cgi-bin/mesh, you can set the maximum ETX displayed on the mesh page. The default is 50, which is pretty useless, given current network capabilities.
But there's doesn't appear to be any limit to the max ETX that is actually broadcast via OLSR
In the spiriting of limiting the population of unreachable nodes and routes in the route tables (and thereby maybe deferring future OLSR route instabilities), would it be possible to implement such a limit so as to "trim" routes? Would this have any adverse affects in routing (route flapping, etc.)?
The text was updated successfully, but these errors were encountered:
Orv
changed the title
OLSR Broadcast "Horizon"?
OLSR Broadcast "Horizon" Enhancement?
Sep 9, 2019
It is possible to have a 50 ETX of 50 perfect quality links. Such a network would be usable from end-to-end. Over time, backbone and other links evolve and can improve. The usable reach measured by ETX can increase.
Ideally it would be configurable, with a default of maybe 20? As of right now, from my QTH in eastern Ventura County, I can't ping anything with an ETX larger than about 12.
Over multiple hops, are ETX numbers additive or multiplicative? I can't wrap my head around the (seemingly simple) formula. Your comment implies additive.
In in /www/cgi-bin/mesh, you can set the maximum ETX displayed on the mesh page. The default is 50, which is pretty useless, given current network capabilities.
But there's doesn't appear to be any limit to the max ETX that is actually broadcast via OLSR
In the spiriting of limiting the population of unreachable nodes and routes in the route tables (and thereby maybe deferring future OLSR route instabilities), would it be possible to implement such a limit so as to "trim" routes? Would this have any adverse affects in routing (route flapping, etc.)?
The text was updated successfully, but these errors were encountered: