Hi all,
cleanups - and more... ;-)
!!!Important!!!
For those of you, who have installed any previous versions - 1st:
#>ipkg remove freifunk-batman-de
For others:
freifunk-batman-de is a WebUI-Plugin for the freifunk-firmware (->[1])
It allows to easily configure and manage all aspects of the batman-daemon in a side-by-side environment with olsr (even for unskilled users).
The main target have been users in the berlin-freifunk community (104/8 net). The main goal is to raise the amount of batman-nodes in 'a mesh' of heterogeneous skilled node owners over 'the critical-mass' in the phase of development and testing... and of course, to make it easy for myself to manage testing with 10++ batman-nodes.
If the interface-config of your hardware differ from those of the Linksys wrt54g v2++/wrt54gl/...(->[2])
you have to use freifunk-batman-*std*-de...
Find it at: http://freifunk.schmudde.com/ipkg
Regards
Lui
[1] - http://ff-firmware.sourceforge.net/
[2] - http://wiki.openwrt.org/OpenWrtDocs/Configuration#head-b62c144b9886b221e0c4…
Hi,
i've seen this behavior bevor, but couln't reproduce it until now:
If B.A.T.M.A.N.-III v0.1.1 beta2 (compability version 2)
is startet with a -p(refered gateway) option and the given gateway is (at least) 2 hops away
(may also not/-always/-directly reachable after start), batmand crashes.
This happens reproduceble ~30-60sec. after start.
Until this point routes are written.
No output. No purging of written routes.
Tests used: batmand -p <gateway> -r 2 eth1:bat br0:bat
With a 1-hop-to-prefered-gateway enviroment batmand seems to have no problems...
Regards
Lui
Just curious if there were any performance and scalability info/figures for
batman vs olsrd vs roofnet. Running / testing olsrd right now, but running
into scalability issues...
--
Thanks!
Michael Oh
Hi,
the batman team proudly announces the 0.1.1 release which is a stability and
bugfix release for the 0.1.x branch.
The following bugs were squashed:
- compability version increased to 2
- batmand deactivates linux kernel antispoof protection which led to packet
loss on multihomed devices
- "logical" memory leaks fixed (continuously growing neighbour and packet
list)
- removed double free on neighbour purge (neighbour with hna)
- broken tun support disabled (on *BSD and MacOS X)
- debug level 1 display bug fixed (patch from nino)
We suggest you to upgrade to the latest version for a better batman
experience ! ;-)
ATTENTION: Certain bugs affect the behaviour of a batman network not only the
one batman node itself. That is why we increased the compability version for
batman packets for the first time. batman irgnores all batman packets that do
not have the same compability version. Which means that batman 0.1.1 will
ignore batman 0.1 and the other way round.
You can get the sources and precompiled mips binaries from open-mesh.net.
Regards,
Marek
first question:
I wondered whether there was a debian package of batman
?
and if freinfunk package is openwrt compatible.
afflicted for these simple question, it is the beginning
thank
Dako
(i speak french)
Hi -
there is a Debian developer which has declared that he will maintain the
b.a.t.m.a.n. Debian-package. We are going to release 0.1.1. soon, which
is a bugfix release. If we are satisfied with the maturity of the code
we'll ask him whether he would like to go ahead and add the package to
Debian.
Currently you have to build your own.
cu elektra
Hi Guys,
At the risk of making myself unpopular at this early stage, could I make a
request that all posts to this list be made in English? I am extremely
interested in this new routing protocol - as I was in OLSR. I've spent a
lot of time trying to translate German with google translator to get a
better understanding of OLSR. I'd rather not have to go through that again
with B.A.T.M.A.N.! The mailing list info page does list English as the list
language, and http://www.open-mesh.net seems to be entirely in English too.
If B.A.T.M.A.N. lives up to it's promise, it will be the best mesh protocol
yet seen. I would like to see it become popular outside of Europe as soon
as possible. Having this list in English will help that happen.
Cheers,
Dan Flett
Hi,
We are having a problem with the first release of B.A.T.M.A.N. When we
try to compile it (trying both gcc-3.4 and 4.0), we got the following
error:
root@Pablo:/home/pablo/Desktop/batman# make
gcc -Wall -O0 -g3 -c -o batman.o batman.c
batman.c: En la función `send_outstanding_packets':
batman.c:889: error: error sintáctico before '<<' token
batman.c:891: error: error sintáctico before ')' token
batman.c:894: error: error sintáctico before '>>' token
batman.c:896: error: error sintáctico before ')' token
batman.c:891: aviso: statement with no effect
batman.c:896: aviso: statement with no effect
batman.c: En el nivel principal:
batman.c:927: error: error sintáctico before '}' token
make: *** [batman.o] Error 1
We are using Ubuntu distro.
Regards:
Pablo
Hi,
die folgende Idee ist auf dem Kongress in diversen Diskussionen entstanden und
bei weitem noch nicht ausgereift. Mich würde eure Meinung dazu interessieren.
Bisher rebroadcastet jeder batman Knoten alle batman Pakete (wir ignorieren
die Ausnahmen jetzt mal). Können wir einen geschickten Algorithmus
entwickeln / anwenden, der es uns gestattet an Stelle des Rebroadcasts der
Nachbar-Nachrichten HNA informationen in unserem Paket mitzusenden ?
So könnte das funktioneren: Mein batman Knoten merkt, dass er 3 one Hop
Nachbarn hat, welche keine anderen Nachbarn hinter sich haben. Daher nehme
ich diese Nachbarn als HNA auf. Meine anderen Nachbarn erhalten nun das Paket
und können feststellen, dass meine IP und die IPs meine Nachbarn ziemlich
dicht beieinander sind und stopfen uns alle in eine HNA Nachricht.
Die Vorteil liegt auf der Hand: Weniger batman Pakete und weniger
Routeneinträge.
Wir müssten das aber so geschickt machen, dass wir nicht unsere eigene
Statistik fälschen. Wenn ich zu meinem aggregierten Nachbarn 50% packet loss
habe, ihn aber in jeder meine OGMs erwähne, könnte der Eindruck entstehen,
dass der Link recht gut ist ?!
Was meint ihr ?
Gruß,
Marek
