From: Marek Lindner <lindner_marek@yahoo.de>
To: b.a.t.m.a.n@open-mesh.net
Subject: Re: [B.A.T.M.A.N.] protocol performance
Date: Tue, 13 Mar 2007 14:34:58 +0100 [thread overview]
Message-ID: <200703131434.58305.lindner_marek@yahoo.de> (raw)
In-Reply-To: <45F69EA5.6020505@gmx.net>
Hi,
> After studying the source code, I understand that HNA information is
> included in every originator message. Isn't such excessive amount of
> routing information bad for typically limited-capacity wireless links?
> And if you concerned about its performance, too - have you considered using
> Fish-eye to improve the algorithm?
Please keep in mind that you will experience packet loss. After 2-3 hops only
a few packets get rebroacasted.
In other words: B.A.T.M.A.N. already has Fish-eye because only the direct
neighbours get most of the packets. With each hop the numbers of retramsitted
packets decreases due to packet loss.
> > And, finally, what exactly is batman-experimental?
>
> Basically Batman with layer 2.5 routing. The very first implementation
> is already available in SVN. It will use algorithm mark IV. Mark IV
> will also be available for layer 3.
batman-experimental is a testbed for future improvements of the B.A.T.M.A.N.
protocol. Here we experiment with certain ideas. Do not use it in a
production environment.
batman is the implemantation of B.A.T.M.A.N. on layer 3. It is pretty stable
and usable.
batman-advanced is B.A.T.M.A.N.on layer 2. Its code is based on batman but it
is fairly new. Expect heavy developement in this branch.
Regards,
Marek
prev parent reply other threads:[~2007-03-13 13:34 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-03-13 9:45 [B.A.T.M.A.N.] protocol performance Atis
2007-03-13 12:52 ` elektra
2007-03-13 13:34 ` Marek Lindner [this message]
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=200703131434.58305.lindner_marek@yahoo.de \
--to=lindner_marek@yahoo.de \
--cc=b.a.t.m.a.n@open-mesh.net \
/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