From: Marek Lindner <mareklindner@neomailbox.ch>
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 2013.4.0 released
Date: Wed, 16 Oct 2013 14:18:49 +0800 [thread overview]
Message-ID: <5553213.hTQb2bQGTZ@diderot> (raw)
[-- Attachment #1: Type: text/plain, Size: 2888 bytes --]
On October 16th, B.A.T.M.A.N. has released batman-adv 2013.4.0, the newest in
a series of stability and bugfix releases. The recently introduced data
distribution daemon 'alfred' received quite some attention and gained new
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-2013.4.0/
as well as prepackaged binaries in your distribution.
Thanks
------
Thanks to all people sending in patches:
* Andrew Lunn <andrew@lunn.ch>
* Antonio Quartulli <ordex@autistici.org>
* Linus Lüssing <linus.luessing@web.de>
* Marco Dalla Torre <marco.dallato@gmail.com>
* Marek Lindner <mareklindner@neomailbox.ch>
* Matthias Schiffer <mschiffer@universe-factory.net>
* Simon Wunderlich <sw@simonwunderlich.de>
* Sven Eckelmann <sven@open-mesh.com>
* Wedson Almeida Filho <wedsonaf@gmail.com>
batman-adv
----------
With this release comes a fix for a kernel crash running on hardware with
specific Ethernet chips triggering a rare code path when forwarding traffic. A fix
for the network coding initialization was submitted to allow to create
multiple batX interfaces when this feature has been included in the module.
The bridge loop avoidance now correctly handles VLAN tags (a regression
introduced with the previous release). Additional Linux kernel backward
compatibility code enables batman-adv to run on various kernel versions.
batctl
------
The incorrectly reported TCP payload length in the tcpdump component was fixed.
The hyphens in the manpage were properly escaped to be groff compliant. C types
and error handling were improved to better handle some error cases.
alfred
------
In order to allow a mesh topology visualization with true geographic layout
alfred was enriched with a location service based on libgpsd. In addition to
retrieving the location via GPS on mobile nodes alfred can be configured with a
static location on stationary nodes to be announced in the network.
A new JSON output format for the vis service was added. The newly added format
is JSON compliant throughout an entire message, in contrast to the "legacy"
per-line JSON output. Alfred also learned to be tolerant to
vanishing/reappearing interfaces and to switch its operation mode
(slave/master) without the need for a restart or losing cached information. To
avoid conflicts in distributions with other "vis" binaries (like the batmand
vis), the binary was renamed to "batadv-vis". Manpages have been added to help
documenting the growing functionality. Also various code/build system cleanups
and bugfixes have been integrated.
Happy routing,
The B.A.T.M.A.N. team
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 490 bytes --]
reply other threads:[~2013-10-16 6:18 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=5553213.hTQb2bQGTZ@diderot \
--to=mareklindner@neomailbox.ch \
--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