vis-server reachable via secondary batman-interface, but not for batman
first of all: The routing works perfectly.
node-A 22.214.171.124 has batman running on eth1 (primary) and tap0 (secondary).
node-B 126.96.36.199 has batman running on tap0. node-B is the visualisation-server.
they reach each other directly via tap0.
batman sets the correct routes on both nodes, however the visualisation-packets don't
get sent on the right interface (despite the routing table).
following output on node-A (188.8.131.52)
batmand is started like this:
root@se:~# ps aux |grep batman 2930 root 408 S batmand -g 10 -s 184.108.40.206 eth1:bat tap0:bat
the topoviser server is reachable via tap0, batman found this route.
root@se:~# route -n |grep 220.127.116.11 18.104.22.168 0.0.0.0 255.255.255.255 UH 0 0 0 tap0
root@se:~# ping 22.214.171.124 PING 126.96.36.199 (188.8.131.52): 56 data bytes 64 bytes from 184.108.40.206: icmp_seq=0 ttl=64 time=106.4 ms
however batmand wants to send the vis-packets via eth1.
of course the topoviser server is not reachable via eth1 but via tap0
root@se:~# tcpdump -n -i eth1 net 105 and arp 18:04:44.293731 arp who-has 220.127.116.11 tell 18.104.22.168
no visualisation-packets on tap0.
i think that this is a bug in the visualisation-socket-code.
maybe it is a false assumption that vis-packets are only sent on the primary interface?!
root@se:~# batmand -v B.A.T.M.A.N.-III vIII 0.2.0 rc2 rv372 (compability version 3)
on both nodes.
Updated by Anonymous almost 16 years ago
- Status changed from New to Closed
Updated by Anonymous over 12 years ago
Milestone 0.2 release deleted
Updated by Anonymous about 12 years ago
- Category set to vis
- Assignee deleted (
Updated by Sven Eckelmann about 6 years ago
- Target version set to 0.2