[B.A.T.M.A.N.] freifunk-batman-de (0.73 "vampimated")
by Lui
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-b62c144b9886b221e0...
14 years
[B.A.T.M.A.N.] b.a.t.m.a.n & OLPC
by Diego Paez
Hi!
i wonder if there are some chances to test b.a.t.m.a.n protocol over a
olpc...I want to test it, but i know that we have some things to consider,
like the ability for the protocol to run into the arm9e processor (the
processor of the marvell libertas, some specifications here
http://arm.com/products/CPUs/ARM946E-S.html ).
Im gonna need some code and/or some documentation...anything :D...
However my english isn't that good...Sorry!
Thanks!
Diego
Facultad de Informatica
UNLP
14 years
[B.A.T.M.A.N.] Visualisation software
by Andreas Langer
The visualisation software is a own programm, you can find it on
s3d.berlios.org.
When you have problems with install join irc at freenode channel #s3d ,
d0tslash is the lead developer and can help you with install.
The visualisation for batman is in work and coming soon, i hope not
later than april.
regards, andreas
14 years, 1 month
[B.A.T.M.A.N.] protocol performance
by Atis
Hi,
a bunch of questions about B.a.t.m.a.n. performance and your future plans.
After studying the source code, I understand that HNA information is included
in every originator message. Isn't such excessive amount of routing
information bad for typically limited-capacity wireless links? What are the
results of real-world tests - there isn't much info in open-mesh.net about
that. What is the largest network in which B.a.t.m.a.n. have been tested?
Is there some actual evidence that B.a.t.m.a.n. outperforms OLSR?
And if you concerned about its performance, too - have you considered using
Fish-eye to improve the algorithm? It could be either periodical TTL
modifications or not including all HNA information in each originator message
(i.e. include them in only, say, every 10-th). The second approach could work
if there some kind of route-request message. Another approach I can think of
would be to introduce some kind of delay in forwarding as the originator
packet get farther away from its originator. Or introduce random probability
of not forwarding it.
Have you thought of adding some re-active components (like in Hazy Sighted
Link State protocol)?
What about handling of asymmetrical links? Currently BATMAN appears to have an
implicit assumption of symmetry. Is there any plans to incorporate
asymmetrical link support? 'Neighbor Link Quality' field perhaps? Or do you
feel that this is something unnecessary for real world setups?
And, finally, what exactly is batman-experimental? A prototype for
B.a.t.m.a.n.-IV implementation?
Thanks,
A.E.
14 years, 1 month
[B.A.T.M.A.N.] Visualisation software
by Saurabh Gupta
Hi,
I am going to test the batman-3 -0.2.0a release . Where can I find the
visualisation software to use with the package. Please some one point me to
some link.
Thanks,
Saurabh
14 years, 1 month
[B.A.T.M.A.N.] Status in IETF
by elektra
Hello Dominik -
we have not submitted a draft to the IETF yet. Rather than
writing drafts according to IETF style about ideas, we are spending time
on improving the performance of our protocol by testing it in real life.
Within 12 months of development we have left behind B.A.T.M.A.N.-I and
B.A.T.M.A.N.-II. The successor of B.A.T.M.A.N.-III will be available in
the near future - I'm sure it will give the protocol a good boost in
performance. In my opinion the development cycle of many organizations
is slow because they are too bureaucratic and too occupied with
paperwork and their own hierarchical structure instead of developing
useful things. I like the informal character of our development. Our
research is a non-profit driven by fun and the will to empower people
around the world to improve their communication on a grass root level.
"On-line for all" is the agenda.
Of course hoity-toity people with ties, suits and long academic titles
tend to ignore a work of freaky people that don't bother about writing
texts in the style of codes of law. That's alright with me. In their
fancy-looking presentations about mesh-networks you see soldiers, tanks
and robots building a mesh on the battlefield or bugging devices for
their paranoid big-brother fantasies. I don't want to be supportive for
that kind of development. We can't avoid it because of the open nature
of open-source development. We are not doing things for our drawers or
to keep it as a secret.
Take the development of OLSR as an example. INRIA is still submitting
new drafts about ideas that we have found not feasible in real life in
the year 2004 when we did our first tests with 20 nodes on a conference
(Wizard of OS III) in Berlin.
Of course our documentation can and will be improved. It would be nice
if people find it easier to understand how B.A.T.M.A.N. works. But I
think a animation movie with comments would be much more helpful than a
text in the style of usual IETF documents.
I guess the development team will have no objections if someone is going
to write a IETF-Draft about the final version of B.A.T.M.A.N.
We may write a draft of B.A.T.M.A.N.-IV as soon as it is properly
implemented and thoroughly tested.
cu elektra
14 years, 1 month
Re: [B.A.T.M.A.N.] How does BATMAN work?
by Hendrik
Hi,
first of all thanks for the quick and good help! It realy helped a
lot (and gave me about 3 more pages to write about BATMAN ;oP)!
Now I got two more Question (hope I don't bother you too much)
1. What Fields are there in the OGM-Package/Header? As to this point
I got:
- TTL
- Seq.No.
- Orig.IP
- Unidrectional Flag
and as possible extension
- "Reachable Subnets"
- "Is willing to Serve as a gateway".
Are there any others?
2. Electra wrote:
"A Originator will see others repeating its Originator messages if
the radio conditions provide a bidirectional link. This is the only
case when we send feedback to others [..] Of course a OGM with
unidirectional flag is only helpful for its Originator, to learn:
Hey, this node has seen me and I have seen it. So we have a
bidirectional link!" about retransmitting an OGM.
Can the Originator of an OGM use this Information to put his direct
neighbor in his routingtable (since that is nessesary for knowing "So
we have a bidirectional link" ;o) ), or does it has to wait for the
OGM of his direct neighbor (neighbor is the originator) to arrive? (I
guess waiting is the answer, I just want to be sure)
Thanks
Hendrik
14 years, 1 month
[B.A.T.M.A.N.] How does BATMAN work?
by Hendrik
Hi,
I'm currently writing my Masterthesis (Performance of MANET
Protocols) and I want to write a little bit about BATMAN. Now I'm
running into some Problems, since it's not very well documented :(.
I got the informations from https://www.open-mesh.net/batman/
documentation/ and the man-page from last Newsletter and figured some
stuff about how to populate the routingtable.
But a few points are still missing and I would be happy on getting an
answer on them ;oP (Or is there an even better page to find some
informations on BATMAN?)
1. From open-mesh Docu: "Originators number their OGMs?, so other
nodes can decide whether they receive an originator-sequence-number
touple (OGSN) the first time or repeatedly"
What's the differens between in OGM and an OGSN? As far as I got to
know the protocol, there are just OGM-messages, aren't there?!?
2. Does a Node somehow send back a message (what message?) to the
originator of an OGM when ist first gets the message (so that the
originator also can populate his Routingtable) or does the originator
has to wait for the other nodes to send their OGM?
3. How can a node tell, that a route is broken? Is there some sort of
timeout in every entry in the routingtable or what?
4. How does the algorithm for the best neighbor work? (I dont need
details here, just what factors are taken for computing)
Thanks!
Greetz
Hendrik
14 years, 1 month
[B.A.T.M.A.N.] Manpage for batman
by elektra
Hi -
I just received mail from Yury Shevchuk, he has written a nice manpage
for batman-0.2. I really like it. There are a few typos and he is
considering it as a bug that 0.0.0.0/0 can't be announced via HNA ;-)
Have a look at it.
cu elektra
14 years, 1 month
[B.A.T.M.A.N.] licence question
by Yury Shevchuk
Greetings!
Could you please clarify which licence applies to B.A.T.M.A.N?
batman.c states it's GPL v2. The site (https://www.open-mesh.net)
suggests it's Creative Commons
(http://creativecommons.org/licenses/by-nc-sa/2.5/) which forbids
commercial use.
Why do I ask? We are an ISP in Pereslavl-Zalessky, Russia and look
towards converting our little multispot WiFi network into a mesh. Yes
we are commercial, but built entirely on free software. May I use
B.A.T.M.A.N as a routing protocol?
Thanks,
-- Yury
14 years, 1 month
