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@open-mesh.net>
Subject: [B.A.T.M.A.N.] get the branches explained
Date: Mon, 4 Feb 2008 23:25:02 +0800	[thread overview]
Message-ID: <200802042325.02853.lindner_marek@yahoo.de> (raw)


Hi,

in the last months many new branches were created and many numbers are 
floating around which caused much confusion. Here comes a brief summary why 
these branches and numbers were created, what they are good for and who is 
behind it:

Whenever we mention Roman numerals (as II or III) we speak of B.A.T.M.A.N.'s 
routing algorithm version. It describes how the routing information are 
flooded and how they are handled to make the best routing decission possible.

Arabic numerals are used to distinguish the version of our implementation. 
Next to the routing algorithm many features and goodies are added to simplify 
the users life.

Example: batman 0.2 uses the B.A.T.M.A.N. III routing algorithm.


=== batman-0.2 ===
[Maintainer: Marek Lindner, Axel Neumann]

- 0.2 stable was created last summer and represents our implementation of the
BATMAN III routing algorithm. It works quite well and stable but has a major
flaw while routing strong asymetric links. That is why we began working on
a new algorithm - 0.2 is to be deprecated soon.

=== batman-0.3 ===
[Maintainer: Marek Lindner, Andreas Langer]

- The 0.3 branch brought a bunch of new features and updates to 0.2,
especially a newly designed routing algorithm. It seems rather stable but
needs some more testing before replacing the current stable version.

=== batman-experimental (aka bmx) ===
[Maintainer: Axel Neumann]

- This branch kept the 0.2 routing algorithm and tried to overcome its flaws
by extending it.
Despite its name it is neither specifically unstable nor contains the latest
features for the 0.3 branch (we are not debian ;-) ). Under the hood it
shares much code with 0.3 - not more or less.

=== batman-advanced (aka batman-adv aka batman-adv-userspace) ===
[Maintainer: Simon Wunderlich, Marek Lindner]

- In April 2007 batman advanced (residing in user space) came to light. It was
a layer 2 implementation of batman 0.2. Since then it was continuously worked
on and uses the batman 0.3 routing algorithm today. It builds a switch of all
your nodes and enables you to ran any protocol (IPv4, IPv6, ..) on top of it.

=== batman-saxnet (merged back into batman-adv-userspace) ===
[Maintainer: www.saxnet.de]

- In autumn 2007 Saxnet (a German company) wanted to use our layer 2
implementation for their products. They tested, fixed and improved our layer
2 implementation. Therefore they got an extra branch which was merged back
into our batman advanced userspace branch.

=== batman-adv-kernelland ===
[Maintainer: Marek Lindner]

- Due to the testing we realized that the layer 2 implementation in user space
suffered from many performance problems. In late 2007 we ported our layer 2
implementation to kernel space in form of a kernel modul. At the moment it is
heavily worked on and a release is to be expected in the coming weeks.

=== battools ===
[Maintainer: Andreas Langer]

- The battools are a set of debugging tools which work together with our layer
2 implementation (user space and kernel land). You can use them to debug the
mesh which proved to be difficult without them.


Regards,
Marek


             reply	other threads:[~2008-02-04 15:25 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-02-04 15:25 Marek Lindner [this message]
2008-02-05 10:34 ` [B.A.T.M.A.N.] get the branches explained Holger Levsen
2008-02-05 22:51   ` Marek Lindner
2008-02-06  9:17     ` Holger Levsen

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=200802042325.02853.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