From: Henning Rogge <hrogge@googlemail.com>
To: babel-users@lists.alioth.debian.org
Cc: olsr list users mailing <olsr-users@lists.olsr.org>,
The Ad-hoc Networking list for a Better Approach To Mobile
<b.a.t.m.a.n@lists.open-mesh.net>,
jerryw@uow.edu.au,
Juliusz Chroboczek <Juliusz.Chroboczek@pps.jussieu.fr>,
brett_hagelstein@uow.edu.au, mehrana@uow.edu.au
Subject: Re: [B.A.T.M.A.N.] [Babel-users] [Olsr-users] A peer-reviewed assessment of OLSR, BATMAN and Babel
Date: Sun, 8 Nov 2009 09:15:08 +0100 [thread overview]
Message-ID: <200911080915.12794.hrogge@googlemail.com> (raw)
In-Reply-To: <7i4op5lt5r.fsf@lanthane.pps.jussieu.fr>
[-- Attachment #1: Type: Text/Plain, Size: 981 bytes --]
Am Sonntag 08 November 2009 02:08:48 schrieb Juliusz Chroboczek:
> > I would have liked to see a comparison with OLSR.org default settings
> > (ETX metric) instead of hopcount metric.
>
> Agreed.
>
> Note however that this doesn't entirely explain why OLSR collapsed in
> their tests. If you look at table I, you'll notice that in the case of
> node Babel did choose the shortest hop-count route, and Babel and OLSR
> exhibited similar levels of route flapping; in other words, in this
> particular test ETX and shortest-hop coincide. However, Figure 2
> indicates that OLSR's throughput was half that of Babel, and in
> Figure 3, OLSR's packet delivery ratio was just 75%.
Good question. Maybe they activated an agressive MPR setting and hit a known
bug in the dijkstra algorithm that can create problems with MPR settings (the
bug is fixed in the development tree and the current 0.5.6 displays an error
message with the not-working settings).
Henning
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
next prev parent reply other threads:[~2009-11-08 8:15 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-06 19:05 [B.A.T.M.A.N.] A peer-reviewed assessment of OLSR, BATMAN and Babel Juliusz Chroboczek
2009-11-06 22:55 ` [B.A.T.M.A.N.] [Babel-users] " Henning Rogge
2009-11-07 10:42 ` [B.A.T.M.A.N.] " Marek Lindner
2009-11-07 16:42 ` [B.A.T.M.A.N.] [Olsr-users] " Juliusz Chroboczek
2009-11-07 23:35 ` L. Aaron Kaplan
2009-11-08 1:08 ` Juliusz Chroboczek
2009-11-08 8:15 ` Henning Rogge [this message]
2009-11-09 4:46 ` [B.A.T.M.A.N.] " Dr. Mehran Abolhasan
2009-11-09 9:07 ` [B.A.T.M.A.N.] [Babel-users] " Henning Rogge
2009-11-09 17:06 ` [B.A.T.M.A.N.] " Juliusz Chroboczek
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=200911080915.12794.hrogge@googlemail.com \
--to=hrogge@googlemail.com \
--cc=Juliusz.Chroboczek@pps.jussieu.fr \
--cc=b.a.t.m.a.n@lists.open-mesh.net \
--cc=babel-users@lists.alioth.debian.org \
--cc=brett_hagelstein@uow.edu.au \
--cc=jerryw@uow.edu.au \
--cc=mehrana@uow.edu.au \
--cc=olsr-users@lists.olsr.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