Hi Brian,
I've checked it out and can confirm your issues. The bonding code as currently implemented is trying to use a different router from each routing table towards the same originator[1]. However, with 1-hop Ethernet links those routers are always the same in all the routing tables. With WiFi that would be a bit different (I've commented out the WiFi penalty check), but even then it only alternates between two of the three interfaces.
At this point I don't have a straight forward fix for this. Will you use three Ethernet devices in your later deployment, or will those be WiFi interfaces? Also, would it be useful for you to consider bonding/teams interfaces of the Linux kernel to bond the link, and give that to batman-adv?
Cheers, Simon
[1] https://www.open-mesh.org/projects/batman-adv/wiki/Network-wide-multi-link-o...
On Wednesday, September 15, 2021 4:58:58 PM CEST Edmisten, Brian wrote:
Simon,
Thank you. I appreciate you looking at this.
Regards, Brian Edmisten
-----Original Message----- From: Simon Wunderlich [mailto:sw@simonwunderlich.de] Sent: Wednesday, September 15, 2021 12:26 AM To: b.a.t.m.a.n@lists.open-mesh.org; Edmisten, Brian Brian.Edmisten@viasat.com Subject: Re: Bonding Alternating
Hi Brian,
hmm, I see. I will try to set up this scenario over the next few days and let you know. I haven't used bonding for quite a while now, but I also don't think that we had changes in the code which would break it.
Anyway, will test and let you know.
Cheers, Simon
On Tuesday, September 14, 2021 6:57:37 PM CEST Edmisten, Brian wrote:
Simon,
I did check again. batctl bonding responds with enabled.
Cheers, Brian Edmisten