From: Sven Eckelmann <sven@narfation.org>
To: Rob Cowart <rob.cowart@xecoenergy.com>
Cc: b.a.t.m.a.n@lists.open-mesh.org
Subject: Re: batadv gw_mode client 0?
Date: Wed, 24 Jun 2020 23:12:18 +0200 [thread overview]
Message-ID: <3573996.TXEB8fxZsQ@sven-edge> (raw)
In-Reply-To: <FE41926B-5684-45D8-B9AE-17D46DA1C8C7@xecoenergy.com>
[-- Attachment #1: Type: text/plain, Size: 1335 bytes --]
On Wednesday, 24 June 2020 22:37:29 CEST Rob Cowart wrote:
> Are there any docs that talk about what B.A.T.M.A.N. V vs B.A.T.M.A.N. IV is good for? The decision to upgrade was made before I got here, I'm not sure anyone understood that IV would still be supported/expected to be used.
There is a summary page about B.A.T.M.A.N. V [1] which you should read first.
And you should definitely not use B.A.T.M.A.N. V when the "throughput based
metric" is not able to retrieve any meaningful values for your link partners
and you are not able to give the routing protocol anything useful to work with.
And B.A.T.M.A.N. IV is still the default and cannot be compiled out. And the
configuration option for B.A.T.M.A.N. V still has following sentence at the
end:
B.A.T.M.A.N. V is currently considered experimental and not
compatible to B.A.T.M.A.N. IV networks.
So while it is definitely less experimental than some years ago, it tends to
still have problems to get useful throughput information from the drivers of
the lower device(s).
But both protocol versions have their Pros and Cons - but with your current
setup (with your current drivers), I have have big doubts that B.A.T.M.A.N. V
has any benefits for you. But I could be wrong.
Kind regards,
Sven
[1] https://www.open-mesh.org/projects/batman-adv/wiki/BATMAN_V
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-06-24 21:12 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-15 20:45 batadv gw_mode client 0? Rob Cowart
2020-06-16 7:01 ` Sven Eckelmann
[not found] ` <3DDDEFCA-57DC-43E1-8534-F816F872CD2B@xecoenergy.com>
2020-06-24 19:36 ` Sven Eckelmann
[not found] ` <9543BE37-DB78-4DC6-A674-F6460D5665BF@xecoenergy.com>
2020-06-24 19:54 ` Sven Eckelmann
[not found] ` <E3FD8A72-966A-4CBB-A036-8C0A4152983D@xecoenergy.com>
2020-06-24 20:13 ` Sven Eckelmann
2020-06-24 20:37 ` Rob Cowart
2020-06-24 21:01 ` Mark Birss
2020-06-24 21:07 ` Sven Eckelmann
2020-06-24 21:12 ` Sven Eckelmann [this message]
[not found] ` <1C0C87FF-C97B-4118-BCC6-DF1163BAB05F@xecoenergy.com>
2020-07-28 5:06 ` Sven Eckelmann
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=3573996.TXEB8fxZsQ@sven-edge \
--to=sven@narfation.org \
--cc=b.a.t.m.a.n@lists.open-mesh.org \
--cc=rob.cowart@xecoenergy.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox