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.] 0.3 final released
Date: Mon, 5 May 2008 19:54:19 +0800 [thread overview]
Message-ID: <200805051954.19727.lindner_marek@yahoo.de> (raw)
Hello everybody,
after a long release cycle (almost one year) the B.A.T.M.A.N. team is proud to
announce the release of:
- batman 0.3 stable
- vis server 0.3 stable
- batman advanced kernelland 0.1 beta
We used the Wireless Community Weekend 2008 in the c-Base to release our
newest version. Here are the main features in brief:
batman 0.3:
- TQ based routing algorith to overcome BATMAN III limitations
- policy routing (see: http://open-mesh.net/batman/doc/RoutingVodoo)
- policy routing script to fully control the routing table (see:
http://downloads.open-mesh.net/batman/useful-scripts-and-tools/policy_routing_script.sh)
- tunneling rewritten (only UDP based, blackhole detection and kernel module
batgat for performance boosting)
- parameters can be changed at runtime (routing_class, gateway_class, hna,
preferred gateway)
- routing_class support 4 different settings (see:
http://open-mesh.net/batman/doc/InternetTuning)
- interface watchdog (interfaces can be (de)activated dynamically)
- packet aggregation (experimental)
- official IANA port 4035 is used
- RFC draft published
batman advanced kernelland:
- layer 2 meshing based on BATMAN TQ algorithm in kernelland
- operates on any ethernet like interface
- supports IPv4, IPv6, DHCP, etc
- is controlled via /proc/net/bvatman-adv/
- bridging via brctl is supported
- interface watchdog (interfaces can be (de)activated dynamically)
- offers integrated vis server which meshes/syncs with other vis servers in
range
The latest version of batman layer 3 obsoletes batman 0.2 which is not
supported anymore. The current version (batman 0.3) is the stable version
from now on. Even though a version 0.4 might emerge we will continue
supporting 0.3 for a long time period with security fixes and stability
patches.
Download our code and have fun ! :-)
Greetings,
Marek
next reply other threads:[~2008-05-05 11:54 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-05 11:54 Marek Lindner [this message]
2008-05-05 12:54 ` [B.A.T.M.A.N.] 0.3 final released dondavis
2008-05-05 13:07 ` Vinay Menon
2008-05-05 20:36 ` Marek Lindner
2008-05-05 21:57 ` Holger Levsen
2008-05-06 19:01 ` Marek Lindner
2008-05-07 12:44 ` Holger Levsen
2008-05-07 13:13 ` Marek Lindner
2008-05-07 23:27 ` Holger Levsen
2008-05-05 13:30 ` Philippe April
2008-05-05 18:24 ` Marek Lindner
2008-05-05 23:22 ` dondavis
2008-05-06 7:27 ` Marek Lindner
2008-05-15 0:24 ` Marek Lindner
2008-05-05 19:12 ` Holger Levsen
2008-05-05 19:18 ` Aaron Kaplan
2008-05-05 20:36 ` a.anselmi
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=200805051954.19727.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