[B.A.T.M.A.N.] Batman gateway lock ups
by Outback Dingo
see pastebin
http://www.pastebin.ca/1194874
pertinent info
dmesg | grep 'batgat loaded'
batgat: [init_module:96] batgat loaded rv1025
uname -a
Linux nightwing 2.6.23.16 #16 Tue Apr 22 20:00:17 ART 2008 mips unknown
root@nightwing:~# batmand -v
WARNING: You are using the unstable batman branch. If you are interested in
*using* batman get the latest stable release !
B.A.T.M.A.N. 0.3-beta (compatibility version 5)
lsmod
Module Size Used by Tainted:
P
sch_htb 14048
2
ath_ahb 103616
0
wlan_xauth 480
0
wlan_wep 4000
0
wlan_tkip 9856
0
wlan_ccmp 5440
2
wlan_acl 1920 0
ath_rate_minstrel 8352 1
ath_hal 136832 3 ath_ahb,ath_rate_minstrel
wlan_scan_sta 8768 1
wlan_scan_ap 6656 0
wlan 152464 10
ath_ahb,wlan_xauth,wlan_wep,wlan_tkip,wlan_ccmp,wlan_acl,ath_rate_minstrel,wlan_scan_sta,wlan_scan_ap
batgat 10944 1
ipt_iprange 672 0
ipt_TOS 832 0
ipt_TTL 928 0
xt_MARK 960 3
ipt_ECN 1472 0
xt_CLASSIFY 640 0
ipt_ttl 704 0
ipt_tos 544 0
ipt_time 1568 0
xt_tcpmss 1088 0
xt_statistic 832 0
xt_mark 672 7
xt_mac 736 3
xt_length 736 0
ipt_ecn 1024 0
xt_DSCP 1056 0
xt_dscp 832 0
imq 2096 0
ipt_IMQ 672 2
xt_string 896 0
xt_layer7 9840 0
ipt_ipp2p 6784 0
ipt_LOG 4640 0
xt_CHAOS 1792 0
xt_DELUDE 2624 1
xt_TARPIT 2816 1
xt_quota 800 0
xt_portscan 2016 0
xt_pkttype 704 0
xt_physdev 1488 0
ipt_owner 800 0
iptable_raw 832 0
xt_NOTRACK 832 0
xt_CONNMARK 1088 0
ipt_recent 4992 0
xt_helper 992 0
xt_conntrack 1312 0
xt_connmark 832 0
xt_connbytes 1312 0
tun 6592 0
13 years, 4 months
[B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)
by 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 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
13 years, 7 months
[B.A.T.M.A.N.] Batman-adv nodes do not recieve OGMs
by Kai Timmer
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
13 years, 8 months
[B.A.T.M.A.N.] What do you think of this result?
by marco tozzini
This is my typical view, of my batman fonera stations, from my batman
laptop (with atheros wifi pcmcia)
Originator (#/255) Nexthop [outgoingIF]: Potential nexthops
... [B.A.T.M.A.N. 0.3, MainIF/IP: wlan1/192.168.2.65, UT: 0d 0h36m]
192.168.2.200 (245) 192.168.2.200 [ wlan1]: 192.168.2.200
(245) 192.168.2.203 (211) 192.168.2.201 (244)
192.168.2.201 (253) 192.168.2.201 [ wlan1]: 192.168.2.201
(253) 192.168.2.200 (234) 192.168.2.203 (209)
192.168.2.203 (233) 192.168.2.200 [ wlan1]: 192.168.2.203
(231) 192.168.2.200 (233) 192.168.2.201 (231)
from my laptop
fping -c 1000 -g 192.168.2.200/30
and this is the results
192.168.2.200 : xmt/rcv/%loss = 1000/928/7%, min/avg/max = 1.23/2.04/92.8
192.168.2.201 : xmt/rcv/%loss = 1000/759/24%, min/avg/max = 1.28/3.11/27.5
192.168.2.203 : xmt/rcv/%loss = 1000/766/23%, min/avg/max = 1.33/3.36/38.7
I don't think it's normal, isn't it?
Ciao
Marco
13 years, 8 months
Re: [B.A.T.M.A.N.] What do you think of this result?
by Marco Tozzini
----- Original Message Follows -----
From: "Antonio Anselmi"
> Marco
>
> can you post the 802.11 and inet configurations of the
> involved iface (I think wlan1) and a memory usage hwile
> batmand is running?
>
> Antonio
>
Hi Antonio,
Sorry I read your message after dismission of the system
I hope I can replicate the system again and post
informations you required
Thanks
Marco
13 years, 8 months
[B.A.T.M.A.N.] Fragen zu Batman
by Raphaela Wrede
Kann mir jemand folgende Fragen beantworten:
Ich fertige gerade eine Dipl. Arbeit zum Thema: "Leistungsanalyse des BATMAN Routingprotokolls für drahtlose
Sensornetze" an der FU Berlin an. (Abgabe 11.5.)
Es geht um einen Leistungsvergleich von OLSR und BATMAN. Hierfür habe ich jedes der beiden Protokolle für die Scatternet
Platform der FU Berlin implementiert und sehr aufwändige realworld Tests bis zu eine Netzgröße von 15 Sensorknoten
durchgeführt. Zusätzlich läuft eine andere Diplomarbeit, die das Ganze im Simulator untersucht, für eine größe
Knotenanzahl, um Skalierbarkeit zu testen.
Wie auch immer.. ich habe noch ein paar Fragen. Vielleicht hast du Zeit sie zu beantworten:
1.) Warum habt ihr BATMAN als Alternative zu OLSR entworfen?
Das Argument, das ich kenne sind die widersprüchlichen Topologieinformationen bei Olsr, die zu Kreisrouten führen
können. Aber was ist zum Beispiel mit dem Routing Traffic Overhead, bei großen Netzen.. wie verhält der sich. Wie stark
wirkt sich das auf den Durchsatz aus? Ende-Zu-Ende Verzögerung... etc. Was war das gravierendste Problem nach eurer
Erfahrung bei großen Netzen. Gibt es hierzu irgendwelche Dokumente.. Diagramme.. die ihr habt? Falls ja, wie wurden die
Daten darüber gewonnen.
2.) Warum ist das RFC zu Batman abgelaufen? Warum läuft sowas überhaupt ab? Wie geht es diesbezüglich weiter? Leider
kenne ich mich mit diesem Request For Comments Krempel nicht so gut aus.. Mein Betreuer meinte, dass es schlecht ist,
sich auf ein abgelaufenes RFC zu berufen.
3.) Gewinnt Batman eher an Popularität in der Meshgemeinde oder ist eher das Gegenteil der Fall. Wo wird Batman noch
eingesetzt?
4.) Wie mein Kommilitone und ich feststellen mussten, gibt es so gut wie keine offiziell veröffentlichten
wissenschaftlichen Arbeiten zu BATMAN. Das ist ein kleines Problem, da es schwierig ist, sich auf andere Arbeiten bei
bestimmten Behauptungen zu stützen. Hier dürfen nur offizielle Papers angegeben werden. Es gibt da ein Paper, wo du auch
mitgewirkt hast, wo ein Leistungsvergleich zwischen OLSR und BATMAN in eine Realtestbed gemacht wurde. Aber leider
scheint selbst dies nicht offiziell veröffentlich zu sein.
Falls du mir irgendwelche Papers schicken kannst, wäre ich dir sehr dankbar.
Vielen Dank.
Raphaela
13 years, 8 months
[B.A.T.M.A.N.] Why in my configuration batmand works only in debug mode?
by 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 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.
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:
iptables --flush
iptables -F
iptables -X
iptables -t nat -F
iptables -t nat -X
iptables -t mangle -F
iptables -t mangle -X
iptables -P INPUT ACCEPT
iptables -P FORWARD ACCEPT
iptables -P OUTPUT ACCEPT
As concern the other problem it's still present.
I'm working with meshboxes equipped with OpenWrt Kamikaze 8.09 and Atheros
WiFi Cards.
In my meshboxes, BATMAN sends OGMs only when it's launched in debug mode
using the command
"batmand -d 3 ath0 &". In this case, I see OGMs travelling in the network
using Wireshark and the command "ip route ls table 66" lists all reachable
batman nodes. Also for the other debug levels (i.e. 1,2,4,5) batmand works
properly.
On the other hand, when I launch the daemon in normal mode, using the
command "batmand ath0", no error is displayed but no OGMs is observed to be
travelling in the network using Wireshark. The only message displayed is:
"Interface activated: ath0
Using interface ath0 with address 10.0.0.1 and broadcast address
10.255.255.255"
Also the command "ip route ls table 66" does not produce any output.
This morning I've installed the last version named B.A.T.M.A.N. 0.3.2-beta
rv1235 (compatibility version 5) but I face again with the same problem.
And finally another question...
Is it normal to observe 3 different processes named batmand using the shell
command ps even if I launched the daemon only once?
Thank you in advance!
Best regards,
Massimo
13 years, 8 months
Re: [B.A.T.M.A.N.] Problem with B.A.T.M.A.N. 0.3.1 rv1206 (compatibility version 5)
by Marco Tozzini
----- Original Message Follows -----
From: Max <rey.web.mail(a)gmail.com>
> 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
...
>
> Best regards,
> Massimo Reineri
>
Hi Massimo,
Please don't blame me for this, but ...
did you start batman this way:
batman -d 1 ath0
I my case batman remain in foreground and if you send ^C it
stops
I used
batmand ath0
and then
batman -c -d 1
to see what happens to daemon in background
Ciao
Marco
13 years, 8 months
Re: [B.A.T.M.A.N.] Unable to connect to internet
by Marco Tozzini
----- Original Message Follows -----
From: Sven Eckelmann
> Solution was found today on irc.
...
> Regards,
> Sven
indeed it is !
thanks you so much for your support (expecially d0tslash on
irc #batman channel)
Ciao
Marco
13 years, 8 months
[B.A.T.M.A.N.] Unable to connect to internet
by marco tozzini
Hi All,
I have 2 fonera router running openwrt and batman
wireless IP are 192.168.2.200 and 192.168.2.203
Routers have separete wifi and eth interfaces
Here it is openwrt network config file:
root@OpenWrt:~# cat /etc/config/network
config 'interface' 'loopback'
option 'ifname' 'lo'
option 'proto' 'static'
option 'ipaddr' '127.0.0.1'
option 'netmask' '255.0.0.0'
config 'interface' 'lan'
option 'ifname' 'eth0'
option 'type' 'bridge'
option 'proto' 'static'
option 'ifname' 'eth0'
option 'ipaddr' '192.168.0.203'
option 'netmask' '255.255.255.0'
option 'gateway' '192.168.0.1'
option 'dns' '192.168.0.1'
config 'interface' 'wifi'
option 'ifname' 'ath0'
option 'proto' 'static'
option 'ipaddr' '192.168.2.203'
option 'netmask' '255.255.255.0'
other router has br-lan 192.168.1.200 and 192.168.0.200
router 192.168.2.203 is connected to my ADSL modem (IP 192.168.0.1)
through ethernet port (br-lan in openwrt)
I would like to connect to internet (and at least to ADSL modem) but
something doesn't work...
I used this command on node 200:
root@OpenWrt:~# batmand ath0
I used this command on node 203:
root@OpenWrt:~# batmand -a 192.168.0.1/24 ath0
Interface activated: ath0
Using interface ath0 with address 192.168.2.203 and broadcast address
192.168.2.255
Here it is result from ping command issued from node 200
root@OpenWrt:~# ping -c 3 192.168.2.203
PING 192.168.2.203 (192.168.2.203): 56 data bytes
64 bytes from 192.168.2.203: seq=0 ttl=64 time=3.539 ms
64 bytes from 192.168.2.203: seq=1 ttl=64 time=2.875 ms
64 bytes from 192.168.2.203: seq=2 ttl=64 time=6.233 ms
--- 192.168.2.203 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 2.875/4.215/6.233 ms
root@OpenWrt:~# ping -c 3 192.168.0.203
PING 192.168.0.203 (192.168.0.203): 56 data bytes
64 bytes from 192.168.0.203: seq=0 ttl=64 time=4.981 ms
64 bytes from 192.168.0.203: seq=1 ttl=64 time=2.991 ms
64 bytes from 192.168.0.203: seq=2 ttl=64 time=3.119 ms
--- 192.168.0.203 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 2.991/3.697/4.981 ms
root@OpenWrt:~# ping -c 3 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss
root@OpenWrt:~# ssh root(a)192.168.0.203
root(a)192.168.0.203's password:
BusyBox v1.11.2 (2008-10-07 13:44:59 UTC) built-in shell (ash)
Enter 'help' for a list of built-in commands.
_______ ________ __
| |.-----.-----.-----.| | | |.----.| |_
| - || _ | -__| || | | || _|| _|
|_______|| __|_____|__|__||________||__| |____|
|__| W I R E L E S S F R E E D O M
KAMIKAZE (8.09, r13118) ----------------------------
* 10 oz Vodka Shake well with ice and strain
* 10 oz Triple sec mixture into 10 shot glasses.
* 10 oz lime juice Salute!
---------------------------------------------------
root@OpenWrt:~# ping -c 3 192.168.0.1
PING 192.168.0.1 (192.168.0.1): 56 data bytes
64 bytes from 192.168.0.1: seq=0 ttl=255 time=4.106 ms
64 bytes from 192.168.0.1: seq=1 ttl=255 time=2.193 ms
64 bytes from 192.168.0.1: seq=2 ttl=255 time=2.187 ms
--- 192.168.0.1 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 2.187/2.828/4.106 ms
root@OpenWrt:~#
As you can see from node 200 I can ping node 203 (wireless interface
192.168.2.203 and wired interface 192.168.0.203), but I'm unable to go
through adsl modem (192.168.0.1)
But I can connect to adsl modem from node 203
Any Hints?
Thanks
Ciao
Marco
13 years, 8 months