Ah, okay understood. Thank you for the explanation.
My focus currently is on batman-adv over ethernet.
I will get around to see how this works out
On Thu, Jun 25, 2020 at 2:23 PM Simon Wunderlich <sw(a)simonwunderlich.de> wrote:
> On Thursday, June 25, 2020 2:14:06 PM CEST Mark Birss wrote:
> > Hi
> > With reference to the wiki topic at
> > https://www.open-mesh.org/projects/batman-adv/wiki/Tweaking
> > bonding
> > Available since: batman-adv 2010.1.0
> > When running the mesh over multiple WiFi interfaces per node
> > batman-adv is capable of optimizing the traffic flow to gain maximum
> > performance. Per default it operates in the "interface alternating"
> > mode (which is suitable for most situations) that switches the WiFi
> > interface with each hop to avoid store & forward. Alternatively,
> > batman-adv can be switched into "bonding mode" in which batman-adv is
> > using all interfaces at the same time to send & receive data. However,
> > this mode is only recommended in special one-hop cases. You can read
> > about our alternatebonding test results to see what suits you best.
> > The wiki shows that this is the only change required on both nodes to
> > use it in default interface alternating mode
> > batctl meshif bat0 bonding enabled
> > The wiki does not say how the throughput was measured after bonding was
> > enabled
> > Will batctl tp be ok?
> Hi Mark,
> bonding was measured on 802.11a/g routers (yes, before there was 11n) back in
> the day using iperf. There was no throughput meter at this point, but it might
> work just as well. In general, there were many situations where bonding
> actually decreased the throughput because the buffers of the radios were not
> synchronized, causing packet re-ordering on the receiver which TCP is very
> sensitive to. In general, I can't really recommend to activate bonding at this
> point, but you can enable it and see if it helps you.