On Tuesday, 16 March 2021 14:17:50 CET oytunyapar@hotmail.com wrote:

Do you suggest, batman-adv, for speeds like 2.4kbit/s (very slow networks)?

No, the discovery and link quality propagation packets can easily consume more bandwidth than you have here. Of course, this depends highly on your setup and configuration. For B.A.T.M.A.N. IV, there is at least a chance to support it because it has no idea about the throughput. But B.A.T.M.A.N. V's throughput metric is not made for such a slow link speed.

Is there any way, feeding neighbor information to batman-adv externally (etc. using DLEP protocol, as an external link monitor)?

No, not at the moment. And you also have to be very careful not to introduce bogus TQs or throughput values when doing things like this.

But in theory, you could write something to inject such information via some new netlink based "protocol".

Kind regards, Sven

On Tue, Mar 16, 2021 at 01:17:50PM -0000, oytunyapar@hotmail.com wrote:

Hi everybody,

I have some questions about batman-adv.
Do you suggest, batman-adv, for speeds like 2.4kbit/s (very slow networks)? I tried to use batctl throughput_override, for such a setup. It seems at least 100kbit/s speed is valid for this utility.
Is there any way, feeding neighbor information to batman-adv externally (etc. using DLEP protocol, as an external link monitor)?
Thank you in advance.

If you use throughput override on all devices, you could also just shift the value equally on all devices. For instance just set 24 Mbit/s instead for a 2.4 kbit/s link.

BATMAN V algorithm itself at the moment does not care about the actual accuracy of the unit. As long as the values are not too small or too large. And as long as it's the same baseline on all devices.

Regards, Linus