public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Henning Rogge <hrogge@googlemail.com>
To: Chun-Ping Wang <jerryw@uow.edu.au>
Cc: "olsr-users@lists.olsr.org" <olsr-users@lists.olsr.org>,
	"b.a.t.m.a.n@lists.open-mesh.net"
	<b.a.t.m.a.n@lists.open-mesh.net>,
	Brett Hegelstein <brett.hagelstein@gmail.com>,
	"justin.lipman@gmail.com" <justin.lipman@gmail.com>,
	Juliusz Chroboczek <jch@pps.jussieu.fr>,
	"babel-users@lists.alioth.debian.org"
	<babel-users@lists.alioth.debian.org>,
	Brett Hagelstein <bretth@uow.edu.au>,
	Mehran Abolhasan <mehrana@uow.edu.au>
Subject: Re: [B.A.T.M.A.N.] [Babel-users] A peer-reviewed assessment of OLSR, BATMAN and Babel
Date: Mon, 9 Nov 2009 16:22:21 +0100	[thread overview]
Message-ID: <200911091622.26778.hrogge@googlemail.com> (raw)
In-Reply-To: <BD0FE81CE135624188025441BB9CB99138F599F20A@EXCMS01.ad.uow.edu.au>

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

Am Montag 09 November 2009 14:00:24 schrieb Chun-Ping Wang:
> Hi all,
> 
> Many thanks for all your feedbacks.  It will definately help us to improve
>  our work. However, I think there is quite a bit of confusions at very
>  beginning.  So I would like to make some clarifications for this paper.
> 
> As it has been mentioned earlier, this paper was to study all the protocols
>  in their default setting.  In term of "default setting" for OLSR, we used
>  original config file shipped in olsr v0.5.5.  As far as I know, this
>  config file is based on the LQ mode of OLSR  (i.e. olsrd.conf.default.lq
>  ).  So, correct me if I am wrong, we have been using OLSR with ETX to
>  begin with. We only modified the HELLO and TC interval to improve static
>  node performance. The results shown in our paper is actually the
>  performance of OLSR with ETX.
Hmm... olsrd.conf.default.lq should be with ETX...

> You may also aware the protocols that we used are already out-dated.  This
>  is because this work was done back in 2008.  We are more than happy to
>  undergo another study with more recent protocols.
The implementation was outdated, not the protocol... but the protocol does 
only mention hopcount, so most people just use "RFC compatible" OLSR.

I would be interested what config file you used for the test. If you plan to 
redo the test we (the olsr.org team) would be very interested in getting 
feedback what kind of problems you have so that we can improve our software.

Henning Rogge

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

  reply	other threads:[~2009-11-09 15:22 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-09 13:00 [B.A.T.M.A.N.] [Babel-users] A peer-reviewed assessment of OLSR, BATMAN and Babel Chun-Ping Wang
2009-11-09 15:22 ` Henning Rogge [this message]
  -- strict thread matches above, loose matches on Subject: below --
2009-11-06 19:05 [B.A.T.M.A.N.] " Juliusz Chroboczek
2009-11-06 22:55 ` [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

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=200911091622.26778.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@gmail.com \
    --cc=bretth@uow.edu.au \
    --cc=jch@pps.jussieu.fr \
    --cc=jerryw@uow.edu.au \
    --cc=justin.lipman@gmail.com \
    --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