Yes, in real world I set throughput overriode for each interface, but in my example only one interface configured in batman network and if it works as you said there are several questions: - Why direct connections work properly (I mean connections Node1-Node2 and Node2-Node3 ) even with this throughput? - Why this scheme works then all nodes had seen originators before throughput overrided? - If I override throughput to 10000, for example, will it work properly?
вс, 24 мая 2020 г., 18:29 Marek Lindner mareklindner@neomailbox.ch:
On Sunday, 24 May 2020 16:43:55 CEST Alexey Ermakov wrote:
[B.A.T.M.A.N. adv 2020.1, MainIF/MAC: eth0/00:04:23:dc:3b:01 (bat0/62:7f:0f:87:43:78 BATMAN_V)] Originator last-seen ( throughput) Nexthop [outgoingIF]
- 00:04:23:dc:3b:10 0.580s ( 0.1) 00:04:23:dc:3b:10 [ eth0]
BATMAN V chooses routes based on link throughput. If the throughput drops below a certain value the route is dropped. As you can imagine, a throughput of 0.1 is pretty close to non-usable.
BATMAN V attempts to auto-detect the throughput using various methods which does not work in a virtualized environment. I suggest you go with the per- interace /sys/class/net/<iface>/batman-adv/throughput_override setting.
Kind regards, Marek Lindner