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: [B.A.T.M.A.N.] batman-adv 2011.4.0 released
Date: Tue, 15 Nov 2011 00:56:58 +0800 [thread overview]
Message-ID: <201111150056.58226.lindner_marek@yahoo.de> (raw)
The B.A.T.M.A.N. team is proud to announce its final milestone in 2011,
2011.4.0, concentrating on the stabilization & bug fixing of the recent
protocol changes and adding some smaller features . As the kernel module
always depends on the Linux kernel it was compiled against, it does not make
sense to provide binaries on our website. As usual, you will find the signed
tarballs in our download section:
http://downloads.open-mesh.org/batman/releases/batman-adv-2011.4.0/
as well as prepackaged binaries in your distribution.
Thanks
------
Thanks to all people sending in patches:
* Antonio Quartulli <ordex@autistici.org>
* Joe Perches <joe@perches.com>
* Jonathan Neuschäfer <j.neuschaefer@gmx.net>
* Marek Lindner <lindner_marek@yahoo.de>
* Martin Hundebøll <martin@hundeboll.net>
* Simon Wunderlich <siwu@hrz.tu-chemnitz.de>
batman-adv
----------
Above all, the 2011.4.0 milestone centers around polishing the protocol
changes introduced with the previous release. Non-mesh clients connected via a
wireless interface are marked as such. This information is then propagated in
the mesh on top of the new non-mesh client infrastructure and can be used to
prevent mesh wide wireless client to wireless client communication (on
standard WiFi AccessPoints this feature is known as 'AP isolation'). The non-
mesh client status flags (new/delete/purge/roaming/wireless) are exported to
user space as part of the translation table output to allow following a
client's status closely.
The coming releases will be escorted by a stepwise inclusion of an improved
version of our routing algorithm. It will be possible to switch between the
current protocol and the new protocol at runtime in order to make testing as
easy as possible. This first stage prepared the existing routing algorithm
code for the upcoming feature for switching routing protocols. No changes to
the routing code behavior have been included.
A couple of translation table bugs have been squashed: memory leaks in the
translation table, wrong initialization of ethernet addresses of translation
table entries and a kernel crash on module unload. Numerous spelling mistakes
in the source code comments were corrected.
batctl
------
batctl received an option to turn on/off the aforementioned mesh wide AP
isolation. When called with '-v' batctl will not only print its own version
but also the batman-adv kernel module version (requires the module to be
loaded). The log level section was rewritten, so that it now expects human
readable log level definitions instead of digits and bitmasks. Also fixed was
the mangled tcpdump output of the CRC value in translation table exchange
packets.
Happy routing,
The B.A.T.M.A.N. team
reply other threads:[~2011-11-14 16:56 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=201111150056.58226.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