From: Andrew Lunn <andrew@lunn.ch>
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.] Modification of BATMAN IV's route selection algorithm
Date: Thu, 31 Mar 2011 08:08:40 +0200 [thread overview]
Message-ID: <20110331060840.GA19781@lunn.ch> (raw)
In-Reply-To: <006701cbef3f$b70d9590$2528c0b0$@britton@adelaide.edu.au>
On Thu, Mar 31, 2011 at 11:35:24AM +1030, Matthew Britton wrote:
> Hi,
>
> We have just completed a brief research project looking at the performance
> of BATMAN IV in a MANET with directional antennas. We've augmenting BATMAN's
> route selection algorithm with a simple hysteresis mechanism called
> "Batrytis" to reduce route-flapping in some circumstances. Please find
> attached an initial technical report describing our work. You are welcome to
> publish this on your site if you wish, and any feedback would also be
> welcome. We have as yet not published this work, although it may be modified
> into a conference paper later in the year. We probably will not have time to
> extend this work although there are clearly many issues that could be
> explored further.
Hi Matthew
Nice paper.
A few comments and questions....
I would probably remove the directional antenna text from the
paper. There is no real research results presented about the use of
them, they are just a tool to allow your semicircle test to be
made. The work presented here is about hysteresis, and the directional
antenna test in the paper does not really add any value.
Looking at the Batrytis algorithm, it is not clear to me what value of
TQ you put into the redistributed OGMs. Do you use TQ or TQc as the
basis, then add the hop penalty etc? In order to avoid routing loops,
the downstream node makes assumptions about what the upstream node
routing tables contains based on the OGMs it received. I'm wondering
if these assumptions have been invalidated by the hysteresis? Did you
analysis this to see if you had additional routing loops when using
Batrytis? For me this is an important point and if you did look at
this, it should be mentioned in the paper.
I don't know the BATMAN code too well, but in BATMAN-adv, the TQ value
put into the redistributed OGM is of the best link to the
originator. Does BATMAN have this feature? Did you use the best TQc or
the best TQ?
The outdoor test setup is a nice idea. I've always setup a chain of
devices to test handovers. You semi circle is much more compact. Does
the sports field you used also have a 70m circle marked out which you
can follow? It looks like there could be a 35m circle. What
directional antennas did you use? Are they COTS i can buy somewhere?
What i don't like about these outdoor results is that it appears you
did not reproduce the tests exactly. You went in opposite
directions. It would be nice to repeat this experiment a few times,
and always use the same direction.
Overall i like the idea, but i need convincing that it does not
introduce routing loops.
Andrew
next prev parent reply other threads:[~2011-03-31 6:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-31 1:05 [B.A.T.M.A.N.] Modification of BATMAN IV's route selection algorithm Matthew Britton
2011-03-31 6:08 ` Andrew Lunn [this message]
2011-03-31 7:20 ` Andrew Lunn
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=20110331060840.GA19781@lunn.ch \
--to=andrew@lunn.ch \
--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