public inbox for b.a.t.m.a.n@lists.open-mesh.org
 help / color / mirror / Atom feed
From: Marek Lindner <lindner_marek@yahoo.de>
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.] Weighting the local packet count; Optimizations for multi-interface nodes
Date: Thu, 23 Dec 2010 13:22:49 +0100	[thread overview]
Message-ID: <201012231322.49591.lindner_marek@yahoo.de> (raw)
In-Reply-To: <AANLkTi=ORJ4Sz9nZT3rT9ofXHdtDVva1U4GQqD-p0ujO@mail.gmail.com>


Hi,

> "Note that, within a timeout, set by default to twice the OGM
> interval, nodes purge a neighbor from which OGMs are no longer
> received"
> 
> In fact the PURGE_TIMEOUT is set to a value of 200s so the problem
> described in the paper, in my opinion, comes from a wrong
> implementation of B.A.T.M.A.N. in the ns2 simulator used in the paper.

you are absolutely right. The authors assume the batman protocol is based on 
timeouts which leads to wrong results. Anyone interested to understand the 
PURGE_TIMEOUT can consult our FAQ.

During the WBMv3 we studied a paper called "Routing protocols for mesh 
networks with mobility support" which seems to have a similar content / same 
authors (?) and contacted the authors to let them know about their wrong 
assumption. Not sure in which manner these papers are related ...


> Furthermore in my opinion, is better that mobile nodes does not use
> B.A.T.M.A.N. but should act as mesh unaware nodes exploiting HNA. Mesh
> network are not MANET...

Agreed.

Cheers,
Marek

  reply	other threads:[~2010-12-23 12:22 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-22 21:10 [B.A.T.M.A.N.] Weighting the local packet count; Optimizations for multi-interface nodes Daniel Seither
2010-12-23 10:07 ` Daniele Furlan
2010-12-23 12:22   ` Marek Lindner [this message]
2011-01-29 16:48     ` Max
2011-02-04 14:21       ` 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=201012231322.49591.lindner_marek@yahoo.de \
    --to=lindner_marek@yahoo.de \
    --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