Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-04-11 Thread Marek Lindner
Hi, > 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 (th

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-25 Thread Marek Lindner
On Wednesday 25 March 2009 03:17:47 Sven Eckelmann wrote: > 0.9.28 worked without any problems and 0.9.30.1 without nptl showed the > same problem - the nptl version doesn't compile at the moment. So changing > the uclibc is a possible solution. Otherwise ask the openwrt developers to > take a look

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-24 Thread Sven Eckelmann
On Monday 23 March 2009 23:05:34 Sven Eckelmann wrote: > On Monday 23 March 2009 18:13:32 Marek Lindner wrote: > > I downloaded the OpenWRT trunk and compiled the i386 image before loading > > it into a qemu environment. I can confirm that batman does nothing if > > started without a debug level. I

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-24 Thread P. Mazart
Hello, Am Montag, 23. März 2009 schrieb Marek Lindner: > I guess OpenWRT uses some different libs / compile > time options / etc that provoke that problem. I hope I understood this thread right… I run OpenWRT whiterussion RC6 with libpthread 0.9.27-1 and it runs ok with batmand_0.3.1-current_mi

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-23 Thread Sven Eckelmann
On Monday 23 March 2009 18:13:32 Marek Lindner wrote: > I downloaded the OpenWRT trunk and compiled the i386 image before loading > it into a qemu environment. I can confirm that batman does nothing if > started without a debug level. It seems the main thread is not doing > anything. Interestingly,

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-23 Thread Marek Lindner
Hi, > In such a meshbox, I installed OpenWRT Kamikaze 8.09. > In order to do that, I downloaded the OpenWRT trunk and all the > available packages from the OpenWRT repository. > Then, I built the image selecting all the interesting packages; among > these packages, in the network section, > I sel

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-21 Thread Max
Hi Marek! In my lab, meshbox is a miniPC with motherboard Lex System MV823A with 512 MByte of DDR SDRAM, a Realtek 10/100 Mbps wired network card, 1 GByte of Flash Memory and 2 wireless network cards Atheros complaint with the IEEE 802.11 a/b/g standards. In such a meshbox, I installed OpenWRT Kam

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-21 Thread Marek Lindner
On Friday 20 March 2009 21:03:24 Max wrote: > r...@meshboxa:~# batmand -c -d 4 > > But it does not display anything and it does not return. > Moreover, no OGM packets are observed to be travelling using Wireshark. That sounds interesting - we are coming closer to the root of the problem. Did you

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-20 Thread Max
Hi Marek, thank you for your support! I have launched the batmand daemon with the command "batmand ath0" and it displays the following message (as usual): r...@meshboxa:~# batmand ath0 Interface activated: ath0 Using interface ath0 with address 10.0.0.1 and broadcast address 10.255.255.255 Now,

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-20 Thread Marek Lindner
On Thursday 19 March 2009 21:38:14 Max wrote: > Now I'm able to ping every originator in the network. The problem is > derived from some iptables filters that stop the ping. Executing the > following command I remove the filters solving the problem: Glad to hear that. > When I launch the daemon

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-19 Thread Max
Thank you Marek and Marco for your suggestions. I have solved the following problem: >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 i

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-19 Thread Marco Tozzini
- Original Message Follows - From: Max > 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

Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-19 Thread Marek Lindner
Hi, > 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. how sure are you about this ? So far nobody could observe this bug. Batman checks whether the interface is up & running before sending packets.

[B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)

2009-03-18 Thread Max
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 th