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.] BATMAN routing
Date: Tue, 30 Nov 2010 18:26:58 +0100 [thread overview]
Message-ID: <201011301826.58467.lindner_marek@yahoo.de> (raw)
In-Reply-To: <AANLkTinFgQ+Z4OsvyHTMNhy11=SrEz0Xu+YU2iZcdcwZ@mail.gmail.com>
Hi,
> The idea is to prioritize recently received OGM's thus giving them
> more weight for the routing decisions. This is because they give a
> precise indication of the status of current situation of the link.
> BATMAN algorithm currently counts the number of received OGM's in a
> current sliding window and the link with the most OGM's becomes the
> best next-hop towards a that destination. A lot can happen within a
> second in an ad hoc wireless network. if a lot of OGM's where recorded
> at the beginning of the window range and less towards the end which be
> that the link was better at the beginning not at the end of the
> sliding window (current). This could be selected as the best as
> opposed to the one that recorded a lot of OGM's towards the end but
> less in total. e.g. suppose you have sliding window of 10, link 1
> records [1111100000]= 5 and link 2 [0000001111] = 4. link 1 will be
> chosen and as it stands the current best would have been link 2.
> The proposed concept prioritizes the recently received OGM's by giving
> them more weight. Thus we want to add the indexes of which an OGM was
> received in that interval. from the example above we would have link
> 1+2+3+4+5+6= 21 and link 2 7+8+9+10 = 34.
your idea makes perfect sense. As a next step we want to split the OGM packet
into 2 distinct types to increase efficiency. We are heavily discussing your
concept in our IRC channel. You should drop in if you have the time or attend
the discussion next weekend.
Cheers,
Marek
next prev parent reply other threads:[~2010-11-30 17:26 UTC|newest]
Thread overview: 30+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <mailman.14.1290812292.944.b.a.t.m.a.n@lists.open-mesh.org>
[not found] ` <AANLkTimR7VU95r3C-=C9rn5ftZahKkNTu3-cU-Vft+VZ@mail.gmail.com>
2010-11-28 22:01 ` [B.A.T.M.A.N.] Fwd: BATMAN routing hlabishi kobo
2010-11-29 20:13 ` Linus Lüssing
2010-11-29 22:23 ` Linus Lüssing
2010-11-29 22:31 ` [B.A.T.M.A.N.] " hlabishi kobo
2010-11-30 17:26 ` Marek Lindner [this message]
2010-12-01 9:46 ` hlabishi kobo
2010-12-01 12:30 ` Marek Lindner
2010-12-02 10:27 ` Linus Lüssing
2010-12-02 12:02 ` Antonio Quartulli
2010-12-06 10:40 ` Daniele Furlan
2010-12-06 16:20 ` Marek Lindner
2010-12-06 17:06 ` Daniele Furlan
2010-12-07 10:09 ` Linus Lüssing
2010-12-11 9:51 ` hlabishi kobo
2010-12-20 9:05 ` Linus Lüssing
2011-02-24 9:58 ` hlabishi kobo
2011-02-24 10:23 ` Sven Eckelmann
2011-02-28 10:46 ` hlabishi kobo
2011-02-28 12:03 ` Sven Eckelmann
[not found] ` <AANLkTinja_Hq4ze-fOFbHRK-iDzzA3Tk0oAsJ+CB=M2S@mail.gmail.com>
2011-02-28 19:29 ` Sven Eckelmann
[not found] ` <AANLkTikj8oj26P_F1LTiGWnt2R=29VESfpD1ZsfeL4X0@mail.gmail.com>
2011-03-08 9:52 ` Sven Eckelmann
2011-03-17 22:40 ` hlabishi kobo
2011-03-18 11:18 ` Sven Eckelmann
2011-03-21 22:40 ` hlabishi kobo
2011-03-21 23:01 ` Sven Eckelmann
2011-04-03 21:10 ` hlabishi kobo
2011-04-03 21:25 ` Sven Eckelmann
2011-04-19 10:21 ` hlabishi kobo
2010-11-29 22:31 ` [B.A.T.M.A.N.] Fwd: " Chris Lang
2010-11-28 21:28 [B.A.T.M.A.N.] " hlabishi kobo
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=201011301826.58467.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