View difference between Paste ID: Qq4D8KGQ and yWhn69eJ
SHOW: | | - or go back to the newest paste.
1
2-
Warning - name already known (changing mac from '66:70:2:ed:f9:64' to '66:70:02:ED:F9:63'): frigorifico
2+
3
         joseluis    0.960s   (148)            marisa [   wlan0-1]:            marisa (148)
4
5
root@nogal:~# batctl ping joseluis
6
PING joseluis (fa:d1:11:54:4f:0a) 20(48) bytes of data
7
Reply from host joseluis timed out
8
Reply from host joseluis timed out
9
Reply from host joseluis timed out
10
Reply from host joseluis timed out
11
Reply from host joseluis timed out
12
^C--- joseluis ping statistics ---
13
5 packets transmitted, 0 received, 100% packet loss
14
rtt min/avg/max/mdev = 0.000/0.000/0.000/0.000 ms
15
16
17
root@nogal:~# ping joseluis
18
PING joseluis (10.5.3.13): 56 data bytes
19
^C
20
--- joseluis ping statistics ---
21
12 packets transmitted, 0 packets received, 100% packet loss
22
23
24
root@nogal:~# arping -b -I br-lan joseluis
25
ARPING to 10.5.3.13 from 10.5.0.4 via br-lan
26
Unicast reply from 10.5.3.13 [f8:d1:11:54:4f:9] 21.720ms
27
Unicast reply from 10.5.3.13 [f8:d1:11:54:4f:9] 18.516ms
28
Unicast reply from 10.5.3.13 [f8:d1:11:54:4f:9] 17.776ms
29
Unicast reply from 10.5.3.13 [f8:d1:11:54:4f:9] 29.290ms
30
Unicast reply from 10.5.3.13 [f8:d1:11:54:4f:9] 17.981ms
31
Unicast reply from 10.5.3.13 [f8:d1:11:54:4f:9] 17.550ms
32
^CSent 6 probe(s) (6 broadcast(s))
33
Received 6 reply (0 request(s), 0 broadcast(s))
34-
Received 6 reply (0 request(s), 0 broadcast(s))
34+
35
36
----------------------
37
NOW FROM A NEIGHBORING NODE
38
39
root@coco:~# batctl o | cut -c -70 | grep joseluis
40
         joseluis    0.230s   (251)          joseluis [   wlan0-1]:  
41
42
43
## mac2bat shows the hostname related to a MAC in /etc/bat-hosts
44
root@coco:~# iw wlan0-1 station dump | mac2bat | grep joseluis -A 8
45
Station joseluis (on wlan0-1)
46
	inactive time:	20 ms
47
	rx bytes:	57642738
48
	rx packets:	570324
49
	tx packets:	2353
50
	tx retries:	429
51
	tx failed:	1
52
	signal:  	-53 [-66, -53] dBm
53
	signal avg:	-48 [-64, -48] dBm
54
55
root@coco:~# ping 10.5.3.13
56
PING 10.5.3.13 (10.5.3.13): 56 data bytes
57
^C
58
--- 10.5.3.13 ping statistics ---
59
11 packets transmitted, 0 packets received, 100% packet loss
60
61
62
root@coco:~# batctl ping joseluis
63
PING joseluis (fa:d1:11:54:4f:0a) 20(48) bytes of data
64
Reply from host joseluis timed out
65
Reply from host joseluis timed out
66
Reply from host joseluis timed out
67
Reply from host joseluis timed out
68
^C--- joseluis ping statistics ---
69
4 packets transmitted, 0 received, 100% packet loss
70
71
72
root@coco:~# arping -b -I br-lan 10.5.3.13
73
ARPING to 10.5.3.13 from 10.5.0.20 via br-lan
74
Unicast reply from 10.5.3.13 [f8:d1:11:54:4f:9] 12.934ms
75
Unicast reply from 10.5.3.13 [f8:d1:11:54:4f:9] 13.569ms
76
Unicast reply from 10.5.3.13 [f8:d1:11:54:4f:9] 12.814ms
77
Unicast reply from 10.5.3.13 [f8:d1:11:54:4f:9] 11.426ms
78
^CSent 4 probe(s) (4 broadcast(s))
79
Received 4 reply (0 request(s), 0 broadcast(s))
80
81
82
## Try to ping through the fe80 of the associated interface (no batman involved here)
83
84
root@coco:~# cat /etc/bat-hosts | grep joseluis
85
FA:D1:11:54:4F:0A joseluis
86
87
$ ipv6calc fe80:: FA:D1:11:54:4F:0A -I prefix+mac
88
fe80::f8d1:11ff:fe54:4f0a
89
90
root@coco:~# ping6 fe80::f8d1:11ff:fe54:4f0a%wlan0-1
91
PING fe80::f8d1:11ff:fe54:4f0a%wlan0-1 (fe80::f8d1:11ff:fe54:4f0a): 56 data bytes
92
^C
93
--- fe80::f8d1:11ff:fe54:4f0a%wlan0-1 ping statistics ---
94
10 packets transmitted, 0 packets received, 100% packet loss
95
96
97
checking that the ping is correct, repeating from another neighbor
98
99
root@ipem265:~#  ping6 fe80::f8d1:11ff:fe54:4f0a%wlan0-1
100
PING fe80::f8d1:11ff:fe54:4f0a%wlan0-1 (fe80::f8d1:11ff:fe54:4f0a): 56 data bytes
101
64 bytes from fe80::f8d1:11ff:fe54:4f0a: seq=0 ttl=64 time=5.957 ms
102
64 bytes from fe80::f8d1:11ff:fe54:4f0a: seq=1 ttl=64 time=3.335 ms
103
104
-----------
105
106
This problem seems to appear randomly. Some nodes cannot "talk" to others that are accessible through another neighbor, but the problem is not always with the same nodes. It will appear "randomly" after a full network reset.