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.] Improving the roaming procedure: multiple roaming within one orig interval
Date: Thu, 10 May 2012 21:12:37 +0800 [thread overview]
Message-ID: <201205102112.37690.lindner_marek@yahoo.de> (raw)
In-Reply-To: <20120504000852.GA29070@ritirata.org>
Hi,
> Right now I am working on a concept that would enable such possibility. I
> tried to summarise my ideas on the wiki as well[1] in order to share with
> you the solution I am thinking about.
>
> The document is still a draft and may not be 100% understandable. If you
> have time and you are curious enough to read the wiki, please drop me your
> feedback, it would really be appreciated :-)
if I understand the document correctly each mesh node a client connects to
will send a roaming advertisement back to the last known mesh node this client
was connected to. A few questions come to my mind:
* Does this already work with the current code ? If not what happens now ?
* How do all nodes get back in sync ? It sounds to me like for certain while
a number of nodes claim the same client, right ? Nobody tells the intermediate
mesh nodes that their client has moved.
* What if receiving a roaming advertisement triggered an immediate
(unscheduled) OGM broadcast ? That would potentially speed up the gap and also
address the "longer path" problem you outlined in the wikipage.
Regards,
Marek
next prev parent reply other threads:[~2012-05-10 13:12 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-05-04 0:08 [B.A.T.M.A.N.] Improving the roaming procedure: multiple roaming within one orig interval Antonio Quartulli
2012-05-10 13:12 ` Marek Lindner [this message]
2012-05-12 18:31 ` Antonio Quartulli
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=201205102112.37690.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