From: cmsv <cmsv@wirelesspt.net>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: [B.A.T.M.A.N.] batctl.8 suggested correction.
Date: Sun, 03 Mar 2013 15:20:54 -0500 [thread overview]
Message-ID: <5133B0A6.6010306@wirelesspt.net> (raw)
Having in mind that throughput and bandwidth are not the same and do not necessarily match; the use of the word "throughput" in batman-adv (Layer2)
is misleading and can cause confusion when in measuring the real throughput on layer3 with L3 software.
As far as i know; at the moment batman-adv (L2) has no way to know what is the real throughput that the announced gateway bandwidth (l3) actually allows therefore the "
throughput" should be changed to announced bandwidth.
Example:
If the node is a gateway client the parameter will decide which
criterias to consider when the batman-adv module has to choose
between different internet connections announced by the afore-
mentioned servers.
default: 20 -> late switch (TQ 20)
examples: 1 -> fast connection
consider the gateway's advertised
bandwidth as well as the link quality
towards the gateway and stick with the
selection until the gateway disappears
2 -> stable connection
chooses the gateway with the best link
quality and sticks with it (ignore the
advertised bandwidth)
3 -> fast switch connection
chooses the gateway with the best link
quality but switches to another gateway
as soon as a better one is found
XX -> late switch connection
chooses the gateway with the best link
quality but switches to another gateway
as soon as a better one is found which
is at least XX TQ better than the cur-
rently selected gateway (XX has to be a
number between 3 and 256).
--
Redes wireless
http://wirelesspt.net
next reply other threads:[~2013-03-03 20:20 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-03-03 20:20 cmsv [this message]
2013-03-03 21:03 ` [B.A.T.M.A.N.] batctl.8 suggested correction Antonio Quartulli
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=5133B0A6.6010306@wirelesspt.net \
--to=cmsv@wirelesspt.net \
--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.