All of lore.kernel.org
 help / color / mirror / Atom feed
From: Henning Rogge <hrogge@googlemail.com>
To: babel-users@lists.alioth.debian.org
Cc: olsr-users@lists.olsr.org, b.a.t.m.a.n@lists.open-mesh.net,
	jerryw@uow.edu.au, Juliusz Chroboczek <jch@pps.jussieu.fr>,
	brett_hagelstein@uow.edu.au, mehrana@uow.edu.au
Subject: Re: [B.A.T.M.A.N.] [Babel-users] A peer-reviewed assessment of OLSR, BATMAN and Babel
Date: Fri, 6 Nov 2009 23:55:38 +0100	[thread overview]
Message-ID: <200911062355.43624.hrogge@googlemail.com> (raw)
In-Reply-To: <871vkbzd6s.fsf@trurl.pps.jussieu.fr>

[-- Attachment #1: Type: Text/Plain, Size: 1079 bytes --]

Am Freitag 06 November 2009 20:05:31 schrieb Juliusz Chroboczek:
> I've just come upon an interesting paper that experimentally compares
> the performance of OLSR, BATMAN and Babel.
> 
>     Real-world Performance of Current Proactive Multi-hop Mesh
>     Protocols.  M. Abolhasan, B. Hagelstein, J. C.-P. Wang.
>    
>  http://ro.uow.edu.au/cgi/viewcontent.cgi?article=1747&context=infopapers
Interesting link Juliusz, thank you.
 
> Short summary: see Table II on the last page.
> 
> 
> A few comments on the paper:
> 
> 1. Section II (the informal description of the protocols) doesn't make
>    much sense.  Ignore it.
> 
> 2. They evaluated original OLSR, not OLSR-ETX as used by our friends in
>    Vienna and Berlin.
This is the bane of the OLSR protocol. Most people not doing mesh-research 
just "use the RFC compatible OLSR" to compare it with anything else... and 
discover (as we all know) that hopcount metric does not work. I'm fighting for 
including a simple ETX implementation into the coming OLSRv2 RFC at the 
moment.

Henning Rogge

[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]

  reply	other threads:[~2009-11-06 22:55 UTC|newest]

Thread overview: 12+ 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 ` Henning Rogge [this message]
2009-11-07 10:42 ` 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         ` [B.A.T.M.A.N.] [Babel-users] " Henning Rogge
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
  -- strict thread matches above, loose matches on Subject: below --
2009-11-09 13:00 [B.A.T.M.A.N.] [Babel-users] " Chun-Ping Wang
2009-11-09 15:22 ` Henning Rogge

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=200911062355.43624.hrogge@googlemail.com \
    --to=hrogge@googlemail.com \
    --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=jch@pps.jussieu.fr \
    --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 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.