Re: [B.A.T.M.A.N.] Rev 972: batmand -c -d n hangs sometimes
by Freifunk Dresden
Hi Axel,
when I use rv980 and call "kill -STOP $(pidof tincd)" then batman works
for a while (1-2 minutes) and exists with the following error:
[ 411413] Error - can't send udp packet: Resource temporarily unavailable.
Connection terminated by remote host
When I restart batmand when tincd is still stopped, the OGM are processed and
I see the neighbour nodes until I get the same error after about 1-2 minutes.
good news, it does not block.
Because of the error message I have inserted at posix/posix.c: 705 "return 0"
(send_udp_packet()).
I have tested two wrt54gl that had the problems before with the rev980 and
the "return 0" statement. Both routers has be running for 18 hours when
tincd was running without creating a connection.
After that I called "kill -STOP $(pidof tincd)" on both routers. Both routers
running now since 13 hours without problems.
Please check and insert the "return 0" at posix/posix:705 if it is the right
solution.
Have a nice week
/Stephan
Zitat von Axel Neumann <axel(a)open-mesh.net>:
> Hi Stephan,
>
> can you check if rv980 solves the problem ?
>
> ciao,
> axel
>
> On Donnerstag 14 Februar 2008, Freifunk Dresden wrote:
>> Hi Axel,
>>
>> I have done some checks. First I have added the tincd tap interface to
>> a bridge and used the bridge as parameter for batmand. This is currently
>> running since 10h.
>>
>> The second what I have tried is to call "kill -STOP $(pidof tincd)".
>> On the WRT54GL batmand stopped quite fast, but it stopped also fast without
>> the "kill". On the WRT54SL where I never have seen batmand stopping, the
>> "kill" has stopped batmand after 5-10 minutes. I could reproduce this
>> serveral times with the GS.
>>
>> When calling batmand -c -a 120.56.56.56/32 I get the following output on
>> batmand -cd3:
>>
>> [ 275531] Unix socket: got connection
>> [ 275539] got request: 10
>> [ 275540] Unix socket: Requesting adding of HNA 120.56.56.34/32 -
>> put this on todo list...
>> [ 275544] got request: 10
>> [ 275545] Unix client closed connection ...
>>
>> Three batmand processes are running and batmand -c returns:
>> WARNING: You are using BatMan-eXp 0.3-alpha (compatibility version 10) !
>> /sbin/batmand [not-all-options-displayed] -r 2 -a 10.12.10.16/28 eth1 tbb
>>
>> After calling "killall batmand" only one of three batmand processes is
>> killed. I have to killall -9 to get rid of it.
>>
>> Regards
>> /Stephan
>>
>>
>>
>>
>>
>>
>> _______________________________________________
>> B.A.T.M.A.N mailing list
>> B.A.T.M.A.N(a)open-mesh.net
>> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>
>
> _______________________________________________
> B.A.T.M.A.N mailing list
> B.A.T.M.A.N(a)open-mesh.net
> https://list.open-mesh.net/mm/listinfo/b.a.t.m.a.n
>
13 years, 8 months
[B.A.T.M.A.N.] simple question
by giuseppe de marco
Does Batman run also on embedded devices with multiple interfaces?
I mean: every link has one radio interface, but evey node can have
multiple radio interface.
That is, link are orthogonal in frequency.
G
--
Giuseppe De Marco, PhD
Toyota Technological Institute
13 years, 8 months
Re: [B.A.T.M.A.N.] Rev 972: batmand -c -d n hangs sometimes
by Freifunk Dresden
Hi Axel,
I have done some checks. First I have added the tincd tap interface to
a bridge and used the bridge as parameter for batmand. This is currently
running since 10h.
The second what I have tried is to call "kill -STOP $(pidof tincd)".
On the WRT54GL batmand stopped quite fast, but it stopped also fast without
the "kill". On the WRT54SL where I never have seen batmand stopping, the
"kill" has stopped batmand after 5-10 minutes. I could reproduce this serveral
times with the GS.
When calling batmand -c -a 120.56.56.56/32 I get the following output on
batmand -cd3:
[ 275531] Unix socket: got connection
[ 275539] got request: 10
[ 275540] Unix socket: Requesting adding of HNA 120.56.56.34/32 -
put this on todo list...
[ 275544] got request: 10
[ 275545] Unix client closed connection ...
Three batmand processes are running and batmand -c returns:
WARNING: You are using BatMan-eXp 0.3-alpha (compatibility version 10) !
/sbin/batmand [not-all-options-displayed] -r 2 -a 10.12.10.16/28 eth1 tbb
After calling "killall batmand" only one of three batmand processes is killed.
I have to killall -9 to get rid of it.
Regards
/Stephan
13 years, 8 months
[B.A.T.M.A.N.] Rev 972: batmand -c -d n hangs sometimes
by Freifunk Dresden
Hi,
I'm currently try using batmand-experimental Rev.972.
I have encountered a strange behaviour. I'm running two
WRT54 (GL and GS).
Routing is working and there is enough memory. I have setup
a cron job to call "batmand -c -d [2,7,8,9]" every minutes to
update the status files on ramdisk. The webinterface then
access the content of the status file which reduces the cpu load.
The WRT54GS is working almost, but the WRT54GL hangs after a while
as described below:
The call to "batmand -c -d [2,7,8,9]" blocks batmand completely.
batman does not do any routing and OGM processing. As result the
router leaves the network.
I can still call "batmand -c -r 3" and verify with "batmand -c" that the
options were set. But OGMs are not processed.
Any call to access the debug-information is blocked.
After killall batmand and restart the call to "batmand -c -d x" is possible
serveral times until batman hangs. The process list shows this
"batmand -c -d x" - process.
I have compiled batmand for whiterussian_rc6 and with the following options:
(The email server has a problem with the assignment character so I have
removed it in this email)
CFLAGS -Wall -Os
LDFLAGS -lpthread
CFLAGS_MIPS -Wall -Os -DREVISION_VERSION $(REVISION_VERSION)
LDFLAGS_MIPS -lpthread
I had to remove the -pg option because it was not possible to compile.
Also in whiterussian_rc the CFLAGS_MIPS/LDFLAGS_MIPS are not used (I think).
Any Idea
/Stephan
13 years, 8 months
[B.A.T.M.A.N.] Basic question
by Carlo Beccia
Hi all,
a basic question for you guys...
How can I compile the stuff https://dev.open-mesh.net/svn/batman/trunk/batman-adv-kernelland/ into openwrt...I would like to try the layer 2 version on my fonera router....
I don't understand if I have to integrate it in a package inside the menuconfig or I can build everything off from the standard configuration...
>From Makefile I understand that the module is not actually integrated into the firmware but it is compiled outside of the menuconfig and then insmod on the target...
I need some hint to create a right build environment...
Thank you in advance
Ciao, Carlo.
_________________________________________________________________
Scarica GRATIS le tue emoticon preferite!
http://intrattenimento.it.msn.com/emoticon/
13 years, 8 months
[B.A.T.M.A.N.] Kernel panic with batman-advanced, pinging remote nodes
by Donald Gordon
Hi
I've installed batman-advanced on a gaggle of Meraki minis, and run into
a kernel panic when I ping a node over the mesh from my laptop (plugged
into a meraki).
The kernel I'm running is
Linux OpenWrt 2.6.23.1 #3 Sun Feb 3 16:24:29 NZDT 2008 mips unknown
The version of batman-advanced I'm running is
B.A.T.M.A.N. Adv 0.1-alpha rv963
The laptop is attached via ethernet to mesh node 0a:18:0a:01:1c:43. On
this node, eth0 is bridged to bat0, and ath2 is an ahdemo interface.
root@OpenWrt:/# cat /proc/net/batman-adv/originators
Originator (#/255) Nexthop [outgoingIF]: Potential
nexthops ... [B.A.T.M.A.N. Adv 0.1-alpha rv963, MainIF/MAC:
ath2/0a:18:0a:01:1c:43]
0a:18:0a:01:1c:41 (255) 0a:18:0a:01:1c:41 [ ath2]:
0a:18:0a:01:1c:41 (255) 0a:18:0a:01:1c:31 (241)
0a:18:0a:01:1c:31 (255) 0a:18:0a:01:1c:31 [ ath2]:
0a:18:0a:01:1c:31 (255) 0a:18:0a:01:1c:41 (244)
root@OpenWrt:/# cat /proc/net/batman-adv/transtable_global
Globally announced HNAs received via the mesh (translation table):
* 00:ff:4f:62:a2:f6 via 0a:18:0a:01:1c:41
* 00:ff:37:ac:5e:5b via 0a:18:0a:01:1c:31
root@OpenWrt:/# cat /proc/net/batman-adv/transtable_local
Locally retrieved addresses (from bat0) announced via HNA:
* 00:ff:7c:45:52:7f
* 00:1d:60:59:53:bc
* 00:18:0a:01:1c:43
The last address is the MAC address of eth0, which gets assigned to the
bridge.
Node 0a:18:0a:01:1c:41 has an IP address assigned to its bridge
(identical configuration to the :43 node) of 192.168.116.65.
When the laptop pings this address, an ARP goes out over the mesh:
root@OpenWrt:/#
root@OpenWrt:/# skb_under_panic: text:c009da8c len:50 put:8
head:812be000 data:812bdffa tail:0x812be02c end:0x812be040 dev:bat0
Break instruction in kernel code[#1]:
Cpu 0
$ 0 : 00000000 10009c00 00000073 8025e9a0
$ 4 : 8025e994 00000001 00000000 00000000
$ 8 : 00000000 8129e5c8 00000002 01c9c380
$12 : 00000002 625a0000 00989646 20ab6400
$16 : 81e5e480 812a2ec0 812a2ec0 81f0bf80
$20 : 0000002a 8107e484 8107e480 00000000
$24 : 81292fd0 00008000
$28 : 81292000 81293130 8128c026 80189924
Hi : 00000140
Lo : 68fdd3c0
epc : 80189924 Tainted: P
ra : 80189924 Status: 10009c03 KERNEL EXL IE
Cause : 10800024
PrId : 00019064
Modules linked in: ath_ahb wlan_xauth wlan_wep wlan_tkip wlan_ccmp
wlan_acl ath_rate_minstrel ath_hal(P) wlan_scan_sta wlan_scan_ap wlan
batman_adv_core nf_nat_tftp nf_conntrack_tftp nf_nat_irc
nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ppp_async ppp_generic slhc
crc_ccitt
Process batman-adv (pid: 632, threadinfo=81292000, task=8129e598)
Stack : 00020020 c009da8c 00000032 00000008 812be000 812bdffa 812be02c
812be040
81f0bc00 812a2ec0 c009daa8 c009da28 00000000 00008020 8128c026
800b36f8
00000000 00000000 812a2ec0 812a2ec0 00000000 81f0bc00 80215768
801a5d48
c0a87401 00000000 81118000 00000000 81f0bc00 812a2ec0 00000000
81f07680
80196378 801962cc 80268348 8107e480 813b0ea0 8107e480 812a2ec0
812a2140
...
Call
Trace:[<c009da8c>][<c009daa8>][<c009da28>][<800b36f8>][<80215768>][<801a5d48>][<80196378>][<801962cc>][<80215600>][<801c2118>][<80215680>][<802157d8>][<802154dc>][<80214324>][<801963d4>][<80270000>][<80270000>][<801ef2c0>][<80270000>][<801f04b8>][<801f0334>][<801f0c80>][<8018a9ac>][<80216574>][<80216464>][<802167f0>][<8019280c>][<801959e4>][<80195c48>][<80196460>][<8006a4ac>][<c00edf88>][<8006a588>][<80185c28>][<8006a8ec>][<80196460>][<80211b30>][<8018aea4>][<802126f4>][<80148400>][<80183ca4>][<c009908c>][<c009c4d4>][<801476b4>][<8006a588>][<8007c254>][<8007c254>][<8018405c>][<c009ae24>][<c009d2dc>][<c009d280>][<c00e9d10>][<c012fe60>][<8007c254>][<8005dd20>][<8005e088>][<c01306a8>][<c01391ec>][<c0138f54>][<c013b728>][<80195c48>][<8006a4ac>][<8006a588>][<800431e0>][<c01306a8>][<c01306a8>][<c01306a8>][<c0138f54>][<c01391ec>][<c0138f54>][<c013b728>][<c01306a8>][<80195c48>][<c01391ec>][<c0138f54>][<c013b728>][<8006a588>][<80195c48>][<8006a4ac>][<8006a588>][<8005f140>][<800431e0>]
[<8005e004>][<8005c490>][<8005ccd0>][<8005dd20>][<8005c45c>][<8005e004>][<8005d824>][<8005c490>][<8005ccd0>][<8007bf00>][<c009c3e4>][<8007bf58>][<80045098>][<80045088>]
Code: afa8001c 0c019286 afa20020 <0200000d> 8fbf0028 03e00008
27bd0030 27bdffd0 afbf0028
Kernel panic - not syncing: Fatal exception in interrupt
Rebooting in 3 seconds..
84 00:21:13 a:18:a:1:1c:43 -> ff:ff:ff:ff:ff:ff BAT_BCAST
a:18:a:1:1c:43ARP 192.168.116.1 ARP_REQUEST(1) 192.168.116.65
84 00:21:13 a:18:a:1:1c:41 -> ff:ff:ff:ff:ff:ff BAT_BCAST
a:18:a:1:1c:43ARP 192.168.116.1 ARP_REQUEST(1) 192.168.116.65
No packets from 0a:18:a:1:1c:41 are seen after the first ARP.
Then 0a:18:a:1:1c:41 panics:
root@OpenWrt:/#
root@OpenWrt:/# skb_under_panic: text:c009da8c len:50 put:8
head:812be000 data:812bdffa tail:0x812be02c end:0x812be040 dev:bat0
Break instruction in kernel code[#1]:
Cpu 0
$ 0 : 00000000 10009c00 00000073 8025e9a0
$ 4 : 8025e994 00000001 00000000 00000000
$ 8 : 00000000 8129e5c8 00000002 01c9c380
$12 : 00000002 625a0000 00989646 20ab6400
$16 : 81e5e480 812a2ec0 812a2ec0 81f0bf80
$20 : 0000002a 8107e484 8107e480 00000000
$24 : 81292fd0 00008000
$28 : 81292000 81293130 8128c026 80189924
Hi : 00000140
Lo : 68fdd3c0
epc : 80189924 Tainted: P
ra : 80189924 Status: 10009c03 KERNEL EXL IE
Cause : 10800024
PrId : 00019064
Modules linked in: ath_ahb wlan_xauth wlan_wep wlan_tkip wlan_ccmp
wlan_acl ath_rate_minstrel ath_hal(P) wlan_scan_sta wlan_scan_ap wlan
batman_adv_core nf_nat_tftp nf_conntrack_tftp nf_nat_irc
nf_conntrack_irc nf_nat_ftp nf_conntrack_ftp ppp_async ppp_generic slhc
crc_ccitt
Process batman-adv (pid: 632, threadinfo=81292000, task=8129e598)
Stack : 00020020 c009da8c 00000032 00000008 812be000 812bdffa 812be02c
812be040
81f0bc00 812a2ec0 c009daa8 c009da28 00000000 00008020 8128c026
800b36f8
00000000 00000000 812a2ec0 812a2ec0 00000000 81f0bc00 80215768
801a5d48
c0a87401 00000000 81118000 00000000 81f0bc00 812a2ec0 00000000
81f07680
80196378 801962cc 80268348 8107e480 813b0ea0 8107e480 812a2ec0
812a2140
...
Call
Trace:[<c009da8c>][<c009daa8>][<c009da28>][<800b36f8>][<80215768>][<801a5d48>][<80196378>][<801962cc>][<80215600>][<801c2118>][<80215680>][<802157d8>][<802154dc>][<80214324>][<801963d4>][<80270000>][<80270000>][<801ef2c0>][<80270000>][<801f04b8>][<801f0334>][<801f0c80>][<8018a9ac>][<80216574>][<80216464>][<802167f0>][<8019280c>][<801959e4>][<80195c48>][<80196460>][<8006a4ac>][<c00edf88>][<8006a588>][<80185c28>][<8006a8ec>][<80196460>][<80211b30>][<8018aea4>][<802126f4>][<80148400>][<80183ca4>][<c009908c>][<c009c4d4>][<801476b4>][<8006a588>][<8007c254>][<8007c254>][<8018405c>][<c009ae24>][<c009d2dc>][<c009d280>][<c00e9d10>][<c012fe60>][<8007c254>][<8005dd20>][<8005e088>][<c01306a8>][<c01391ec>][<c0138f54>][<c013b728>][<80195c48>][<8006a4ac>][<8006a588>][<800431e0>][<c01306a8>][<c01306a8>][<c01306a8>][<c0138f54>][<c01391ec>][<c0138f54>][<c013b728>][<c01306a8>][<80195c48>][<c01391ec>][<c0138f54>][<c013b728>][<8006a588>][<80195c48>][<8006a4ac>][<8006a588>][<8005f140>][<800431e0>]
[<8005e004>][<8005c490>][<8005ccd0>][<8005dd20>][<8005c45c>][<8005e004>][<8005d824>][<8005c490>][<8005ccd0>][<8007bf00>][<c009c3e4>][<8007bf58>][<80045098>][<80045088>]
Code: afa8001c 0c019286 afa20020 <0200000d> 8fbf0028 03e00008
27bd0030 27bdffd0 afbf0028
Kernel panic - not syncing: Fatal exception in interrupt
Rebooting in 3 seconds..
I realise this dump is full of unhelpful hex; if you can tell me how to
get symbol names out of my kernel I'll gladly forward them on :-)
donald
13 years, 8 months
[B.A.T.M.A.N.] get the branches explained
by Marek Lindner
Hi,
in the last months many new branches were created and many numbers are
floating around which caused much confusion. Here comes a brief summary why
these branches and numbers were created, what they are good for and who is
behind it:
Whenever we mention Roman numerals (as II or III) we speak of B.A.T.M.A.N.'s
routing algorithm version. It describes how the routing information are
flooded and how they are handled to make the best routing decission possible.
Arabic numerals are used to distinguish the version of our implementation.
Next to the routing algorithm many features and goodies are added to simplify
the users life.
Example: batman 0.2 uses the B.A.T.M.A.N. III routing algorithm.
=== batman-0.2 ===
[Maintainer: Marek Lindner, Axel Neumann]
- 0.2 stable was created last summer and represents our implementation of the
BATMAN III routing algorithm. It works quite well and stable but has a major
flaw while routing strong asymetric links. That is why we began working on
a new algorithm - 0.2 is to be deprecated soon.
=== batman-0.3 ===
[Maintainer: Marek Lindner, Andreas Langer]
- The 0.3 branch brought a bunch of new features and updates to 0.2,
especially a newly designed routing algorithm. It seems rather stable but
needs some more testing before replacing the current stable version.
=== batman-experimental (aka bmx) ===
[Maintainer: Axel Neumann]
- This branch kept the 0.2 routing algorithm and tried to overcome its flaws
by extending it.
Despite its name it is neither specifically unstable nor contains the latest
features for the 0.3 branch (we are not debian ;-) ). Under the hood it
shares much code with 0.3 - not more or less.
=== batman-advanced (aka batman-adv aka batman-adv-userspace) ===
[Maintainer: Simon Wunderlich, Marek Lindner]
- In April 2007 batman advanced (residing in user space) came to light. It was
a layer 2 implementation of batman 0.2. Since then it was continuously worked
on and uses the batman 0.3 routing algorithm today. It builds a switch of all
your nodes and enables you to ran any protocol (IPv4, IPv6, ..) on top of it.
=== batman-saxnet (merged back into batman-adv-userspace) ===
[Maintainer: www.saxnet.de]
- In autumn 2007 Saxnet (a German company) wanted to use our layer 2
implementation for their products. They tested, fixed and improved our layer
2 implementation. Therefore they got an extra branch which was merged back
into our batman advanced userspace branch.
=== batman-adv-kernelland ===
[Maintainer: Marek Lindner]
- Due to the testing we realized that the layer 2 implementation in user space
suffered from many performance problems. In late 2007 we ported our layer 2
implementation to kernel space in form of a kernel modul. At the moment it is
heavily worked on and a release is to be expected in the coming weeks.
=== battools ===
[Maintainer: Andreas Langer]
- The battools are a set of debugging tools which work together with our layer
2 implementation (user space and kernel land). You can use them to debug the
mesh which proved to be difficult without them.
Regards,
Marek
13 years, 8 months
[B.A.T.M.A.N.] Rev 972: VIS not working
by Freifunk Dresden
Hi,
I'm currently try using batmand-experimental Rev.972.
First the visualisation server does not show any connections.
Have two routers with batmand-exp rev 972 running. It seems
that this batman version is not compatible with the vis-server.
When I use the old version of vis, I get the dot information
when I call "telnet localhost 2004".
I assume that the batman-exp implementation still uses the old
compatibility version for vis.
/Stephan
13 years, 8 months
[B.A.T.M.A.N.] Problems with 0.3-beta rv963 and kmod-batgat
by Vinay Menon
Hi,
I am testing out batman 0.3-beta rv963 with openwrt-trunk (r10219) .
I could get the expected results when i am using tun instead of kmod-batgat
.
but when i use kmod-batgat even tho the tunnel gate0 is established the
routing rules and firewall is same as with kmod-tun i cant get traffic thru
gate0
My Setup:
---- Wired
- - - - WiFi
192.168.111.1-----(WAN)-192.168.111.74(Gateway)10.1.125.158 - - - - - -
10-1-125-158 (Node2)
*With kmod-batgat:*
from
ping 192.168.111.1 -I gate0
##on gateway
root@10-1-125-158:~# lsmod |grep batgat
batgat 10976 1
##Ping from Node
root@Node2:~# ping 192.168.111.1 -I gate0
PING 192.168.111.1 (192.168.111.1): 56 data bytes
--- 192.168.111.1 ping statistics ---
46 packets transmitted, 0 packets received, 100% packet loss
##tcpdump on node
root@10-1-125-158:~# tcpdump -i gate0 proto \\icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on gate0, link-type EN10MB (Ethernet), capture size 96 bytes
0 packets captured
0 packets received by filter
0 packets dropped by kernel
*With kmod-tun:*
root@10-1-125-158:/# lsmod |grep tun
tun 6592 1
*##on Node*
batman -cd2
Gateway (#/255) Nexthop [outgoingIF], gw_class ... [
B.A.T.M.A.N. 0.3-beta rv963, MainIF/IP: ath0/10.1.124.248, UT: 0d 0h52m]
=> 10.1.125.158 (255 + 0) 10.1.125.158 [ ath0], gw_class 49 -
4MBit/1024KBit, reliability: 0
*##Ping from Node*
root@Node2:~# ping 192.168.111.1
PING 192.168.111.1 (192.168.111.1): 56 data bytes
64 bytes from 192.168.111.1: seq=0 ttl=63 time=8.473 ms
64 bytes from 192.168.111.1: seq=1 ttl=63 time=6.585 ms
*##tcpDump on gateway's gate0*
root@10-1-125-158:/# tcpdump -i gate0 proto \\icmp
tcpdump: WARNING: arptype 65534 not supported by libpcap - falling back to
cooked socket
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on gate0, link-type LINUX_SLL (Linux cooked), capture size 96
bytes
00:50:45.798376 IP 169.254.0.1 > 192.168.111.1: ICMP echo request, id 1004,
seq 0, length 64
00:50:46.614360 IP 192.168.111.1 > 169.254.0.1: ICMP echo reply, id 1004,
seq 0, length 64
00:50:46.805310 IP 169.254.0.1 > 192.168.111.1: ICMP echo request, id 1004,
seq 1, length 64
00:50:46.806369 IP 192.168.111.1 > 169.254.0.1: ICMP echo reply, id 1004,
seq 1, length 64
*##tcpDump on gateway's eth0*
root@10-1-125-158:/# tcpdump -i eth0 proto \\icmp
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth0, link-type EN10MB (Ethernet), capture size 96 bytes
00:48:29.108148 IP 192.168.111.74 > 192.168.111.1: ICMP echo request, id
1003, seq 6, length 64
00:48:29.145367 IP 192.168.111.1 > 192.168.111.74: ICMP echo reply, id 1003,
seq 6, length 64
Also at times ip rules dont appear on node and i have to restart batmand to
get the network working.
--
Vinay Menon
13 years, 8 months
