From: rene <batman@absorb.it>
To: The list for a Better Approach To Mobile Ad-hoc Networking
<b.a.t.m.a.n@open-mesh.net>
Subject: Re: [B.A.T.M.A.N.] batmand still doesn't start the right way
Date: Sun, 25 Nov 2007 12:30:02 +0530 [thread overview]
Message-ID: <47491D72.8020007@absorb.it> (raw)
In-Reply-To: <200711241744.20844.lindner_marek@yahoo.de>
Hi,
just had a look around over the installations and found the problem
again. This time between two mipsel's. The setup: AP144 has a wireless
connection to AP43. Just like that (192.168.1.X are olsr-routes):
-- AP 144 --------------------------------------------------------
root@144:~# route -n | grep ^192.168.1.43
192.168.1.43 0.0.0.0 255.255.255.255 UH 1 0 0 eth1
root@144:~# ping 192.168.1.43
PING 192.168.1.43 (192.168.1.43): 56 data bytes
64 bytes from 192.168.1.43: icmp_seq=0 ttl=64 time=2.8 ms
64 bytes from 192.168.1.43: icmp_seq=1 ttl=64 time=5.5 ms
--- 192.168.1.43 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 2.8/4.1/5.5 ms
root@144:~# ps | grep batman
905 root 436 S /usr/sbin/batmand eth1:1 vlan1:1
907 root 436 S /usr/sbin/batmand eth1:1 vlan1:1
909 root 436 S /usr/sbin/batmand eth1:1 vlan1:1
9661 root 280 S grep batman
root@144:~# ifconfig eth1:1
eth1:1 Link encap:Ethernet HWaddr 00:13:10:27:D6:A6
inet addr:192.168.40.144 Bcast:192.168.43.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:4 Base address:0x1000
root@144:~# ifconfig vlan1:1
vlan1:1 Link encap:Ethernet HWaddr 00:13:10:27:D6:A4
inet addr:192.168.41.144 Bcast:192.168.43.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
-- AP 43 ---------------------------------------------------------
root@43:~# route -n | grep ^192.168.1.144
192.168.1.144 0.0.0.0 255.255.255.255 UH 1 0 0 eth1
root@43:~# ping 192.168.1.144
PING 192.168.1.144 (192.168.1.144): 56 data bytes
64 bytes from 192.168.1.144: icmp_seq=0 ttl=64 time=2.3 ms
64 bytes from 192.168.1.144: icmp_seq=1 ttl=64 time=2.0 ms
--- 192.168.1.144 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 2.0/2.1/2.3 ms
root@43:~# ps | grep batman
903 root 436 R /usr/sbin/batmand eth1:1 vlan1:1
907 root 436 S /usr/sbin/batmand eth1:1 vlan1:1
908 root 436 S /usr/sbin/batmand eth1:1 vlan1:1
5230 root 280 S grep batman
root@43:~# ifconfig eth1:1
eth1:1 Link encap:Ethernet HWaddr 00:18:39:6B:E0:95
inet addr:192.168.40.43 Bcast:192.168.43.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
Interrupt:2 Base address:0x5000
root@43:~# ifconfig vlan1:1
vlan1:1 Link encap:Ethernet HWaddr 00:18:39:6B:E0:93
inet addr:192.168.41.43 Bcast:192.168.43.255 Mask:255.255.252.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
root@43:~#
------------------------------------------------------------------
And now lets see what batman is doing:
-- AP 144 --------------------------------------------------------
root@144:~# tcpdump -i eth1:1 port 4305 and src 192.168.40.144
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1:1, link-type EN10MB (Ethernet), capture size 96 bytes
0 packets captured
0 packets received by filter
0 packets dropped by kernel
root@144:~# tcpdump -i vlan1:1 port 4305 and src 192.168.41.144
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vlan1:1, link-type EN10MB (Ethernet), capture size 96 bytes
06:41:17.865478 IP 192.168.41.144.4305 > 192.168.43.255.4305: UDP, length 15
06:41:17.904019 IP 192.168.41.144.4305 > 192.168.43.255.4305: UDP, length 25
...
-- AP 43 ---------------------------------------------------------
root@43:~# tcpdump -i eth1:1 port 4305 and src 192.168.40.43
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on eth1:1, link-type EN10MB (Ethernet), capture size 96 bytes
06:41:02.984846 IP 192.168.40.43.4305 > 192.168.43.255.4305: UDP, length 20
06:41:03.065075 IP 192.168.40.43.4305 > 192.168.43.255.4305: UDP, length 20
...
19 packets captured
38 packets received by filter
0 packets dropped by kernel
root@43:~# tcpdump -i vlan1:1 port 4305 and src 192.168.41.43
tcpdump: verbose output suppressed, use -v or -vv for full protocol decode
listening on vlan1:1, link-type EN10MB (Ethernet), capture size 96 bytes
06:41:31.255300 IP 192.168.41.43.4305 > 192.168.43.255.4305: UDP, length 20
06:41:31.406760 IP 192.168.41.43.4305 > 192.168.43.255.4305: UDP, length 25
...
18 packets captured
----------------------------------------------------------------
So batman does not send any OGMs over eth1:1 from AP144. As a result
there is no wireless batman-link between the two Accesspoints.
You can find the output of batmand -c -d4 at:
http://www.opennet-initiative.de/firmware/misc/log_AP43.log.gz
http://www.opennet-initiative.de/firmware/misc/log_AP144.log.gz
If you require more information, just ask.
Regards,
Rene
next prev parent reply other threads:[~2007-11-25 7:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-24 6:01 [B.A.T.M.A.N.] batmand still doesn't start the right way rene
2007-11-24 6:15 ` a.anselmi
2007-11-24 6:31 ` rene
2007-11-24 11:05 ` Axel Neumann
2007-11-24 16:11 ` rene
2007-11-24 16:44 ` Marek Lindner
2007-11-25 7:00 ` rene [this message]
2007-11-25 16:32 ` Axel Neumann
2007-11-25 16:46 ` rene
2007-11-25 17:55 ` Axel Neumann
2007-11-25 18:51 ` rene
2007-11-25 19:56 ` Axel Neumann
2007-11-24 20:24 ` Jan Hetges
2007-11-25 4:23 ` rene
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=47491D72.8020007@absorb.it \
--to=batman@absorb.it \
--cc=b.a.t.m.a.n@open-mesh.net \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox