Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

OLSR Broadcast "Horizon" Enhancement? #18

Closed
Orv opened this issue Sep 7, 2019 · 2 comments
Closed

OLSR Broadcast "Horizon" Enhancement? #18

Orv opened this issue Sep 7, 2019 · 2 comments
Labels
enhancement New feature or request

Comments

@Orv
Copy link

Orv commented Sep 7, 2019

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.)?

@Orv Orv changed the title OLSR Broadcast "Horizon"? OLSR Broadcast "Horizon" Enhancement? Sep 9, 2019
@ae6xe
Copy link
Contributor

ae6xe commented Sep 13, 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.

What would be the limit to code in?

@Orv
Copy link
Author

Orv commented Sep 13, 2019

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.

@ae6xe ae6xe transferred this issue from aredn/aredn_ar71xx Dec 16, 2020
@ae6xe ae6xe added the enhancement New feature or request label Sep 11, 2021
@dman776 dman776 mentioned this issue Apr 27, 2022
@dman776 dman776 closed this as completed Jun 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants