From: Axel Neumann <axel@open-mesh.net>
To: b.a.t.m.a.n@open-mesh.net
Subject: [B.A.T.M.A.N.] Release 0.2.0rc2 out now!
Date: Fri, 25 May 2007 20:24:41 +0200 [thread overview]
Message-ID: <200705252024.42077.axel@open-mesh.net> (raw)
HeyHo!
if you ever had the feeling that rc1 is somehow unstable and many obvious
routes were simply ignored, relax, you were totally right. Our optimism
drove us to introduce just *minor* changes to the code just five
minutes to 12 and which eventually turned out to be buggy. So happened with
rc1. We are trying hard to improve.
So what has changed since then?
- Fixed relevant bugs in the debug-system and an incredible bug in the
neighbor-detection algorithm causing one of two neighbors to simply
ignore the other (what a mess).
- Now batman is sending originator-messages with TTL of 50 on
every interface.
(results in: no more dead back-routes to nodes with multiple
interfaces but also larger routing-tables, more processing and
traffic overhead)
- Reduced bidirectional-link-check-range to 2
and increased sequence-range to 128
(as some experiments in the berlin freifunk mesh indicated that these
parameters worked best for our purpose)
- AND, in order to resolve existing bugs instead of introducing new ones,
we took some time to test all changes in our local setup which includes
freifunk-based WRTs, buffalos, and foneras as well as 4G-MeshCubes and
i386 based machines
... hoping that you can confirm the good results
Please update your nodes to batmand-0.2.0-rc2 by visiting our new
SUPA-DOWNLOAD-STORE at http://open-mesh.net/batman/downloads offering
precompiled binaries and packages for quite a number of linux-based systems.
Also we are willing to include other targets in the auto-compilation
toolchain which currently allows compilations for openWrt (
http://wiki.openwrt.org/TableOfHardware ) and openembedded
( http://www.openembedded.org/filebrowser/org.openembedded.dev/conf/machine )
based systems. So if you find your HW supported by one of the mentioned
projects (and are willing to test next autogenerated results) please give us
a hint.
very best wishes from
the B.A.T.M.A.N. development team
reply other threads:[~2007-05-25 18:24 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=200705252024.42077.axel@open-mesh.net \
--to=axel@open-mesh.net \
--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