B.A.T.M.A.N April 2009

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

12 participants
19 discussions

[B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)
by Max 11 Apr '09

11 Apr '09

Good afternoon to everybody! I have to deal with 2 big problems occurred when I run batmand 0.3.1 rv 1206 in meshboxs equipped with OpenWrt Kamikaze 8.09 I detect the following problems: 1) B.A.T.M.A.N. daemon only works whether launched in debug mode. I'm sure about this because I'm monitoring the network with a packet sniffer. 2) When launched in debug mode (using the command batmand -d 3 ath0 &), the daemon starts to generate OGMs and to fill up its routing tables in a correct way. The problem occurs when I tries to ping an host in the network because the routing process uses the default routing table (that has not been modified by the batman daemon) and it is not aware on the correct batman routing tables. Does someone know how to solve these problems? Thank you in advance. Best regards, Massimo Reineri

4 18

[B.A.T.M.A.N.] [PATCH] Add compilation support for GNU/kFreeBSD
by Sven Eckelmann 09 Apr '09

09 Apr '09

Debian recently announced that it added GNU/kFreeBSD as supported distribution. It consists of an FreeBSD kernel and the usual debian userspace tools and libraries. It uses the glibc with some extra (free)bsd libraries to support bsd-only functions like devname and strlcpy. batmand should instantly work on this platform if a BSD developer would port the bsd compatibility layer again to (Open|Free)BSD. Signed-off-by: Sven Eckelmann <sven.eckelmann(a)gmx.de> --- batman/Makefile | 5 +++++ batman/bsd/tun.c | 2 +- 2 files changed, 6 insertions(+), 1 deletions(-) diff --git a/batman/Makefile b/batman/Makefile index 509217d..0f6e61f 100644 --- a/batman/Makefile +++ b/batman/Makefile @@ -44,6 +44,11 @@ ifeq ($(UNAME),Darwin) OS_C= $(BSD_C) $(POSIX_C) endif +ifeq ($(UNAME),GNU/kFreeBSD) +OS_C= $(BSD_C) $(POSIX_C) +LDFLAGS+= -lfreebsd -lbsd +endif + ifeq ($(UNAME),FreeBSD) OS_C= $(BSD_C) $(POSIX_C) endif diff --git a/batman/bsd/tun.c b/batman/bsd/tun.c index 2629bcd..2c571c0 100644 --- a/batman/bsd/tun.c +++ b/batman/bsd/tun.c @@ -71,7 +71,7 @@ static int open_tun_any(char *dev_name, size_t dev_name_size) } return -1; } -#elif defined(__FreeBSD__) +#elif defined(__FreeBSD__) || defined(__FreeBSD_kernel__) static int open_tun_any(char *dev_name, size_t dev_name_size) { int fd; -- 1.6.2.2

1 0

[B.A.T.M.A.N.] hardware requirements for mesh
by leongmzlist 09 Apr '09

09 Apr '09

Hi, I've got a wrt54gl and Airlink AR430W w/ openwrt 8.09, but they can't do multiple modes. (eg: ap and ad-hoc at the same time). So far, I've gotten ad-hoc mode working w/ the 2 routers and batman partially working. Can those 2 routers be use in a mesh network so that laptops can connect to them and go on the net? All the other mesh routers/repeaters I've seen can run in multiple modes. thx mike

2 1

[B.A.T.M.A.N.] default routes not set
by leongmzlist 09 Apr '09

09 Apr '09

Hi, new at batman. I've got the following done: 1. got an airlink ar430w and wrt54gl to ping each other over ad-hoc network 2. setup br-lan:0 on each router. ar430w has is 192.168.100.1; wrt54gl is 192.168.100.2 3. was able to ping each other via br-lan:0 IP 4. using openwrt 8.09 on both routers. The wrt54gl got the wan/internet link up. I started "batmand -g 1mbit/128kbit br-lan:0" the ar430w doesn't have internet; I started "batmand -r 3 -d 3 br-lan:0" got this on the ar430w logs: Interface activated: br-lan:0 Using interface br-lan:0 with address 192.168.100.1 and broadcast address 192.168.100.255 B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5) Adding throw route to 127.0.0.0/8 via 0.0.0.0 (table 68 - lo) Adding throw route to 192.168.1.0/24 via 0.0.0.0 (table 68 - br-lan) Adding throw route to 192.168.100.0/24 via 0.0.0.0 (table 68 - br-lan:0) debug level: 3 routing class: 3 Adding route to 192.168.100.2 via 0.0.0.0 (table 66 - br-lan:0) Found new gateway 192.168.100.2 -> class: 32 - 1024KBit/128KBit Adding default route to 192.168.100.2 (gw_flags: 32, tq: 217, gw_product: 0) Gateway client - got IP (169.254.0.1) from gateway: 192.168.100.2 Adding default route via gate0 (table 68) When I run route -n on the ar430w, there's no default route set. I manually ran: route add default gw 169.254.0.1 Next I tried to ping the outside world on the ar430w but it gets no where. Any ideas? thx mike

2 3

[B.A.T.M.A.N.] bmxd rv1197 changelog
by Jan Hetges 09 Apr '09

09 Apr '09

Hi Axel http://downloads.open-mesh.net/batman/development/sources/batmand-exp_0.3-a… this seems to be empty!? cheers --Jan

2 1

[B.A.T.M.A.N.] bmxd debug level 8
by Jan Hetges 08 Apr '09

08 Apr '09

Hi Axel, Hi bmxd users as my network grows, bmxd -cd8 gets kind of... not so useful (as the output doesn't fit on one page anymore). for my part, i'm mostly interested, in what bmxd thinks about the neighbours. so, what do you guys think about splitting it into two parts? cheers --Jan

3 3

[B.A.T.M.A.N.] Trouble with SSH in L2 batman network
by Gargi Purohit 08 Apr '09

08 Apr '09

Hi I have configured a Layer 2 mesh (Using batman kernel module) on Routerboard 433. These are boards equipped with 2 interfaces. I have configured/created a virtual interface on every physical interface. So for E.g. my routerboard 1 (RB1) has ath0 (Phy interface - Adhoc mode), ath1 (Virtual interface - Master mode), ath2 (Phy interface - Adhoc mode) and ath3 (Virtual interface in Master mode). My set up has 2 routerboards - one is wired and the other is wireless. Thus RB1 has (ath0, ath1, ath2, ath3 and eth0) RB2 has (ath0, ath1, ath2, ath3) The proc is as follows on both RB1 and RB2 root@open-mesh:~# cat /proc/net/batman-adv/interfaces ath0 ath2 I have created a bridge between all interfaces. The bridge config on RB1 is: root@open-mesh:~# brctl show bridge name bridge id STP enabled interfaces br0 8000.000c422fbfe4 no eth0 ath1 ath3 bat0 The bridge config on RB2 is: root@open-mesh:~# brctl show bridge name bridge id STP enabled interfaces br0 8000.00ff8fffdcc7 no bat0 ath1 ath3 I can connect clients to each of these RB and they can get Internet access. My configuration is like this: -------------------Server 1 -------------| | |-------------Wired AP (RB1) = = = = = = = Wireless AP (RB2) | ^ ^ | ^ ^ | ^ ^ | C1 (Client of RB1) C2 (Client of RB2) The APs RB1 and RB2 are connected to each other over 2 mesh wireless links on different channels (ath0 and ath2) I am trying to ssh to Server 1 from all these nodes. I can ssh to Server 1 from anyone but RB2 (RB1, C1, C2 can ssh Server 1 but RB2 cannot). Likewise I can ssh all nodes from each other. E.g from anywhere on LAN I can ssh to each of these nodes. But RB2 can be sshed only from nodes directly connected (eg. RB1 and C2). Note however i can ping Server 1 from RB2. Am not sure where I am going wrong? Regards Gargi

1 0

[B.A.T.M.A.N.] [PATCH] Don't access random memory after forwarding broadcast
by Sven Eckelmann 02 Apr '09

02 Apr '09

B.A.T.M.A.N. advanced iterates over every known interface when receiving data and tries to forward as much as possible data from the same interface as possible using a while-loop inside the outer loop. When it receives a broadcast ethernet frame which needs to be forwarded again it will try to send it to every known interface again. This loop is inside the first one and used the same pos variable as the outer loop. After the inner loop has finished it will point to a memory location which is not part of the interface list, but the while loop starts again and tries to access this memory region without knowing what it is and to what it belongs. This could lead to a kernel oops or any kind of other unspecified behavior of the kernel. The inner loop should use a seperate position variable to iterate over all interfaces for the broadcast. Signed-off-by: Sven Eckelmann <sven.eckelmann(a)gmx.de> --- batman-adv-kernelland/routing.c | 6 +++--- 1 files changed, 3 insertions(+), 3 deletions(-) diff --git a/batman-adv-kernelland/routing.c b/batman-adv-kernelland/routing.c index 73e786e..89bfb3f 100644 --- a/batman-adv-kernelland/routing.c +++ b/batman-adv-kernelland/routing.c @@ -567,7 +567,7 @@ int receive_raw_packet(struct socket *raw_sock, unsigned char *packet_buff, int int packet_recv_thread(void *data) { - struct batman_if *batman_if; + struct batman_if *batman_if, *batman_bcastif; struct ethhdr *ethhdr; struct batman_packet *batman_packet; struct unicast_packet *unicast_packet; @@ -851,8 +851,8 @@ int packet_recv_thread(void *data) interface_rx(soft_device, packet_buff + sizeof(struct ethhdr) + sizeof(struct bcast_packet), result - sizeof(struct ethhdr) - sizeof(struct bcast_packet)); /* rebroadcast packet */ - list_for_each_entry_rcu(batman_if, &if_list, list) { - send_raw_packet(packet_buff + sizeof(struct ethhdr), result - sizeof(struct ethhdr), batman_if->net_dev->dev_addr, broadcastAddr, batman_if); + list_for_each_entry_rcu(batman_bcastif, &if_list, list) { + send_raw_packet(packet_buff + sizeof(struct ethhdr), result - sizeof(struct ethhdr), batman_bcastif->net_dev->dev_addr, broadcastAddr, batman_bcastif); } break; -- 1.6.2.1

2 1

[B.A.T.M.A.N.] Batman-adv nodes do not recieve OGMs
by Kai Timmer 01 Apr '09

01 Apr '09

Hello, i have a problem using batman-adv. At the moment i use v0.1, but i had the same problem when trying the svn version 1241. All the nodes send their ogm, but none does recieve any of these. What i did on all nodes is: iwconfig $wlaninterface essid batman mode ad-hoc and then echo "$wlaninterface" > /proc/net/batman-adv/interfaces echo 15 > /proc/net/batman-adv/log_level cat /proc/net/batman-adv/log after that shows somethink like this: Adding interface: ath0 Can't activate module: the primary interface is not active Sending own packet (originator 00:18:84:14:48:e5, seqno 1, TTL 50) on interface ath0 [00:18:84:14:48:e5] Sending own packet (originator 00:18:84:14:48:e5, seqno 2, TTL 50) on interface ath0 [00:18:84:14:48:e5] Sending own packet (originator 00:18:84:14:48:e5, seqno 3, TTL 50) on interface ath0 [00:18:84:14:48:e5] I also tried to set the channel on all nodes, but with no effect. Maybe someone can tell me what i do wrong. Thank you, -- Kai Timmer Email : email(a)kait.de Jabber: kai(a)kait.de Blog: http://blog.kaitimmer.de

3 4

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

B.A.T.M.A.N April 2009