From: Marek Lindner <lindner_marek@yahoo.de>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@lists.open-mesh.org>
Subject: Re: [B.A.T.M.A.N.] Problem to find better Route
Date: Tue, 15 Nov 2011 09:40:36 +0800 [thread overview]
Message-ID: <201111150940.36605.lindner_marek@yahoo.de> (raw)
In-Reply-To: <4EC171B2.9070605@inti.gob.ar>
Hi,
> With a dinstance of about 20 meters between A and B, and the same
> distance between B and C. The problem is that sometimes, A and C get
> connected directly in terms of batman-adv protocol (checked with batctl
> o), and when that happens, the bitrates are very poor (less than 1Mbps),
> like if B wasn't there. In fact we disconnected B and obtained very
> similar results.
would you mind sharing the orignator tables of the involved nodes ?
> Then we reduced tx power settings on A and C, forcing the B hop between
> them, and we got much better speeds (~20Mbps). We've read about ELP and
> think that maybe simple OGM messages are not good to measure link
> quility between A and C in this example, could that be the problem? In
> that case is there a way to fix this with actual batman-adv algorithms?
You can play with the hop penalty parameter to encourage batman to use fewer
or more hops (depending on your needs).
Regards,
Marek
next prev parent reply other threads:[~2011-11-15 1:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.5.1321268402.29081.b.a.t.m.a.n@lists.open-mesh.org>
2011-11-14 19:53 ` [B.A.T.M.A.N.] Problem to find better Route gtolon
2011-11-14 23:43 ` Antonio Quartulli
2011-11-15 1:40 ` Marek Lindner [this message]
[not found] <mailman.3.1321354802.20324.b.a.t.m.a.n@lists.open-mesh.org>
2011-11-15 17:59 ` gtolon
2011-11-16 3:30 ` Marek Lindner
2011-11-16 8:32 ` Antonio Quartulli
2011-11-16 8:49 ` Marek Lindner
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=201111150940.36605.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox