B.A.T.M.A.N

b.a.t.m.a.n@lists.open-mesh.org

15 participants
4308 discussions

[B.A.T.M.A.N.] BATMAN test at Fosdem
by Benjamin Henrion 20 Feb '07

20 Feb '07

Hi, For those of you who are coming to Fosdem, I am planning a BATMAN test in order to see if the routing protocol chooses the fastest route. Here are the details: Saturday 24 feb @ 12H30 in front of the Chavanne room. I will put more instructions here: http://www.reseaucitoyen.be/wiki/index.php/Batman2chans Best, -- Benjamin Henrion <bhenrion at ffii.org> FFII Brussels - +32-484-566109 - +32-2-4148403

1 0

[B.A.T.M.A.N.] First batman tests
by Benjamin Henrion 16 Feb '07

16 Feb '07

Hi, We met with several people in Brussels active on the reseaucitoyen project to test Batman. Our configuration was 4 laptops like this: laptop1 <----ethernet----> laptop2 + + + + + + wlan1 wlan11 + + + + + + laptop3 <----ethernet----> laptop4 With 8 different IPs for the 8 interfaces. We launched batman-0.10 on all the nodes, but it appeared that one of the interfaces was not reachable via ping. And the experience was reproductible when we restarted the dameon, sometimes with a different IP unreachable. We are going to test the same configuration soon to see if batman chooses the fastest route in terms of throughput. Best, -- Benjamin Henrion <bhenrion at ffii.org> FFII Brussels - +32-484-566109 - +32-2-4148403

3 2

[B.A.T.M.A.N.] Probleme mit Routing bei BATMAN
by Hendrik 09 Feb '07

09 Feb '07

Hallo, ich wollte mal BATMAN ausprobieren und habe hierzu folgendes Netz aufgebaut: A --- B ---- C (stehen alle drei direkt nebeneinander) (IP: 192.168.0. A:3 B:1 C:2) So, bei einer direkten Kommunikation klapp alles ganz toll (und schnell!). Sobald ich aber in A via iptables sage, dass er nichts mehr von der MAC-Adr. von C annehmen soll (und andersherum) - spich so tue als ob die Nodes A und C keine Funkverbindung mehr haben, Klappt das Routing über B nicht. B sagt zwar, dass es A und C kennt/ hört, A kennt aber nur B und C auch nur B (nicht aber den Weg dahinter) Der Debug auf Node A (192.168.0.3) auf Level 3 gab mir folgendes aus: [ 39552] Received BATMAN packet from 192.168.0.1 (originator 192.168.0.2, seqno 162, TTL 49) [ 39552] update_last_hop(): Searching originator entry of last- hop neighbour of received packet [ 39552] new packet - orig: 192.168.0.2, sender: 192.168.0.1 [ 39552] Packet with unidirectional flag [ 39552] purge() [ 39552] ------------------ DEBUG ------------------ [ 39552] Forward list [ 39552] 192.168.0.3 at 40000 [ 39552] Originator list [ 39552] 192.168.0.1, last_aware:39552, last_reply:36003, last_seen:1153 via: [ 39552] ---------------------------------------------- END DEBUG [ 39552] Er bekommt also über B (192.168.0.1) von C (192.168.0.2) eine Message, kann damit aber nichts anfangen. Ich benutze batman-III-0.1-rc1auf einem Debian Sarge System ohne tun. Danke für eure Hilfe Hendrik

2 1

[B.A.T.M.A.N.] -p ... crashes
by Lui 29 Jan '07

29 Jan '07

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

2 1

[B.A.T.M.A.N.] Performance
by Michael Oh 27 Jan '07

27 Jan '07

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

2 1

[B.A.T.M.A.N.] Announcement: batman 0.1.1 released
by Marek Lindner 25 Jan '07

25 Jan '07

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

1 0

[B.A.T.M.A.N.] hi all
by rcml＠lecurie.org 23 Jan '07

23 Jan '07

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)

6 5

[B.A.T.M.A.N.] debian package
by elektra 23 Jan '07

23 Jan '07

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

1 0

[B.A.T.M.A.N.] Testing
by Dan Flett 23 Jan '07

23 Jan '07

Hi all Seeing as how this list is pretty new, I figure it wouldn't be too rude to send a test message first. Happy BATMAN to you all! Dan

2 2

[B.A.T.M.A.N.] List Language
by Dan Flett 11 Jan '07

11 Jan '07

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

2 1

Jump to page:

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

B.A.T.M.A.N