From: Simon Wunderlich <sw@simonwunderlich.de>
To: "b.a.t.m.a.n@lists.open-mesh.org"
<b.a.t.m.a.n@lists.open-mesh.org>,
"Edmisten, Brian" <Brian.Edmisten@viasat.com>
Subject: Re: Bonding Alternating
Date: Tue, 21 Sep 2021 16:16:27 +0200 [thread overview]
Message-ID: <4948508.lctyQggAPn@prime> (raw)
In-Reply-To: <7e8fe0e7bf7b42baac350b20f2a0846a@viasat.com>
[-- Attachment #1: Type: text/plain, Size: 1773 bytes --]
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-optimization
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
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2021-09-21 14:16 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-09-09 20:09 Bonding Alternating brian.edmisten
2021-09-10 7:15 ` Simon Wunderlich
2021-09-10 17:59 ` brian.edmisten
2021-09-13 13:40 ` Simon Wunderlich
2021-09-14 16:57 ` Edmisten, Brian
2021-09-15 7:26 ` Simon Wunderlich
2021-09-15 14:58 ` Edmisten, Brian
2021-09-21 14:16 ` Simon Wunderlich [this message]
2021-09-21 15:41 ` Edmisten, Brian
2021-09-22 7:55 ` Simon Wunderlich
2021-09-22 15:10 ` Edmisten, Brian
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=4948508.lctyQggAPn@prime \
--to=sw@simonwunderlich.de \
--cc=Brian.Edmisten@viasat.com \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.