Hi,

> Batman doesn't seem to calculate throughput properly

please provide details about what you mean? What is the expected vs
calculated throughput and how have you determined the calculation is wrong?


> so we set it manually with throughput override, but then even when actual
> throughput of the active interface decreases, it doesn't switch to the other
> interface because it only considers the overriden value.

Please describe the steps how this problem can be reproduced.


> Batman already has a tool called throughout meter, shouldn't it be used to
> continuously check the value?

A number of patches were proposed to integrate the throughput meter as
fallback when the throughput can not be determined via other means:

https://lists.open-mesh.org/mailman3/hyperkitty/list/[email protected]/thread/AJYTJOONPCJ2GSPSTOFTTO5TZQKYJGOZ/

There were a few open issues that require further work. If you are interested
in spending time on this subject, I am happy to provide assistance.

Cheers,
Marek



Reply via email to