From: gtolon@inti.gob.ar
To: b.a.t.m.a.n@lists.open-mesh.org
Subject: [B.A.T.M.A.N.] Problem to find better Route
Date: Mon, 14 Nov 2011 16:53:22 -0300 [thread overview]
Message-ID: <4EC171B2.9070605@inti.gob.ar> (raw)
In-Reply-To: <mailman.5.1321268402.29081.b.a.t.m.a.n@lists.open-mesh.org>
Hi. We are using batman-adv 2011.2.0 with Openwrt Backfire-rc6 on D-Link
routers, and we're making some tests with iperf to measure bitrate
capabilities between nodes. When we put three nodes aligned we notice
that the obtained bitrate between the extreme nodes strongly depends on
the batman path between them. To make it clear, we have:
A ---------- B ---------- C
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.
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?
Thanks in advance!
Gabriel
El 14/11/2011 08:00 a.m., b.a.t.m.a.n-request@lists.open-mesh.org escribió:
> Send B.A.T.M.A.N mailing list submissions to
> b.a.t.m.a.n@lists.open-mesh.org
>
> To subscribe or unsubscribe via the World Wide Web, visit
> https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n
> or, via email, send a message with subject or body 'help' to
> b.a.t.m.a.n-request@lists.open-mesh.org
>
> You can reach the person managing the list at
> b.a.t.m.a.n-owner@lists.open-mesh.org
>
> When replying, please edit your Subject line so it is more specific
> than "Re: Contents of B.A.T.M.A.N digest..."
>
>
> Today's Topics:
>
> 1. Re: [PATCH] add make install (Sven Eckelmann)
> 2. Re: [PATCH] add make install (Sven Eckelmann)
> 3. Re: [PATCH] add make install (Alexey Fisher)
>
>
> ----------------------------------------------------------------------
>
> Message: 1
> Date: Mon, 14 Nov 2011 11:21:12 +0100
> From: Sven Eckelmann<sven@narfation.org>
> To: b.a.t.m.a.n@lists.open-mesh.org
> Cc: lindner_marek@yahoo.de
> Subject: Re: [B.A.T.M.A.N.] [PATCH] add make install
> Message-ID:<1428522.agqKBYpyMC@sven-laptop.home.narfation.org>
> Content-Type: text/plain; charset="iso-8859-1"
>
> On Monday 14 November 2011 10:38:07 Sven Eckelmann wrote:
>> On Monday 14 November 2011 10:11:32 Alexey Fisher wrote:
>>> Signed-off-by: Alexey Fisher<bug-track@fisher-privat.net>
>>> ---
>>>
>>> Makefile | 3 +++
>>> 1 files changed, 3 insertions(+), 0 deletions(-)
> [...]
>> NAck: Sven Eckelmann<sven@narfation.org>
> And also "Nack" for not updating the README [1]
>
> Kind regards,
> Sven
>
> [1] http://www.open-mesh.org/wiki/open-mesh/Contribute#Submitting-patches
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 836 bytes
> Desc: This is a digitally signed message part.
> URL:<http://lists.open-mesh.org/pipermail/b.a.t.m.a.n/attachments/20111114/850391c0/attachment-0001.pgp>
>
> ------------------------------
>
> Message: 2
> Date: Mon, 14 Nov 2011 11:29:36 +0100
> From: Sven Eckelmann<sven@narfation.org>
> To: Alexey Fisher<bug-track@fisher-privat.net>
> Cc: b.a.t.m.a.n@lists.open-mesh.org, lindner_marek@yahoo.de
> Subject: Re: [B.A.T.M.A.N.] [PATCH] add make install
> Message-ID:<1956205.mQFSXpQuIf@sven-laptop.home.narfation.org>
> Content-Type: text/plain; charset="utf-8"
>
> On Monday 14 November 2011 11:19:19 Alexey Fisher wrote:
> [...]
>> Thank you,
>> so you will send your patch? I prefer last version, to make testing easier.
> I personally don't care. Feel free to fix your patch and send a new version
> (but think about adding the ":" after "install" -- the character magically
> disappeared when I wrote the mail).
>
> And don't forget the documentation part as it is always hard to remember
> everything on the day the release is made, but easy when you just made the
> patch. :)
>
> Thanks,
> Sven
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: signature.asc
> Type: application/pgp-signature
> Size: 836 bytes
> Desc: This is a digitally signed message part.
> URL:<http://lists.open-mesh.org/pipermail/b.a.t.m.a.n/attachments/20111114/329c477e/attachment-0001.pgp>
>
> ------------------------------
>
> Message: 3
> Date: Mon, 14 Nov 2011 11:37:55 +0100
> From: Alexey Fisher<bug-track@fisher-privat.net>
> To: Sven Eckelmann<sven@narfation.org>
> Cc: b.a.t.m.a.n@lists.open-mesh.org, lindner_marek@yahoo.de
> Subject: Re: [B.A.T.M.A.N.] [PATCH] add make install
> Message-ID:<4EC0EF83.2060602@fisher-privat.net>
> Content-Type: text/plain; charset="utf-8"
>
> On 14.11.2011 11:29, Sven Eckelmann wrote:
>> On Monday 14 November 2011 11:19:19 Alexey Fisher wrote:
>> [...]
>>> Thank you,
>>> so you will send your patch? I prefer last version, to make testing easier.
>> I personally don't care. Feel free to fix your patch and send a new version
>> (but think about adding the ":" after "install" -- the character magically
>> disappeared when I wrote the mail).
>>
>> And don't forget the documentation part as it is always hard to remember
>> everything on the day the release is made, but easy when you just made the
>> patch. :)
> Corrected.
> -------------- next part --------------
> A non-text attachment was scrubbed...
> Name: 0001-add-make-install-option.patch
> Type: text/x-patch
> Size: 959 bytes
> Desc: not available
> URL:<http://lists.open-mesh.org/pipermail/b.a.t.m.a.n/attachments/20111114/969101dd/attachment-0001.bin>
>
> ------------------------------
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N@lists.open-mesh.org
> https://lists.open-mesh.org/mm/listinfo/b.a.t.m.a.n
>
>
> End of B.A.T.M.A.N Digest, Vol 59, Issue 19
> *******************************************
>
next parent reply other threads:[~2011-11-14 19:53 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 ` gtolon [this message]
2011-11-14 23:43 ` [B.A.T.M.A.N.] Problem to find better Route Antonio Quartulli
2011-11-15 1:40 ` Marek Lindner
[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=4EC171B2.9070605@inti.gob.ar \
--to=gtolon@inti.gob.ar \
--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