You are not logged in.
Hello, I have a problem with IPv6, and I wonder if a configuration issue could be the reason.
Here is the configuration:
* little_finger: connected to a router through WiFi
wlan0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1280
inet 192.168.0.6 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::216:44ff:fef1:d307 prefixlen 64 scopeid 0x20<link>
inet6 2a02:2788:44:116c:216:44ff:fef1:d307 prefixlen 64 scopeid 0x0<global>
ether 00:16:44:f1:d3:07 txqueuelen 1000 (Ethernet)
* naboo: Connected to a cable ethernet switch
enp3s0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.8 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 2a02:2788:44:116c:12c3:7bff:fe4f:34dd prefixlen 64 scopeid 0x0<global>
inet6 fe80::12c3:7bff:fe4f:34dd prefixlen 64 scopeid 0x20<link>
ether 10:c3:7b:4f:34:dd txqueuelen 1000 (Ethernet)
* gallifrey: Connected to the same cable ethernet switch
eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.18 netmask 255.255.255.0 broadcast 192.168.0.255
inet6 fe80::ba27:ebff:fe20:3ed5 prefixlen 64 scopeid 0x20<link>
inet6 2a02:2788:44:116c:ba27:ebff:fe20:3ed5 prefixlen 64 scopeid 0x0<global>
ether b8:27:eb:20:3e:d5 txqueuelen 1000 (Ethernet)
ping and ssh with IPv4 addresses works fine.
ping6 doesn't: it looks like naboo and gallifrey cannot really communicate.
On little_finger:
ping6 2a02:2788:44:116c:12c3:7bff:fe4f:34dd #naboo
ping6 -I wlan0 fe80::12c3:7bff:fe4f:34dd #naboo
ping6 2a02:2788:44:116c:ba27:ebff:fe20:3ed5 #gallifrey
ping6 -I wlan0 fe80::ba27:ebff:fe20:3ed5 #gallifrey
They all work.
On naboo:
ping6 2a02:2788:44:116c:216:44ff:fef1:d307 #little_finger
ping6 -I enp3s0 fe80::216:44ff:fef1:d307 #little_finger
ping6 -I enp3s0 fe80::ba27:ebff:fe20:3ed5 #gallifrey
They all work but
ping6 2a02:2788:44:116c:ba27:ebff:fe20:3ed5 #gallifrey
won't work:
--- 2a02:2788:44:116c:ba27:ebff:fe20:3ed5 ping statistics ---
96 packets transmitted, 0 received, 100% packet loss, time 95008ms
according to wireshark, a ping request and a ping echo are seen, which is even weirder.
The same behavior applies on gallifrey: no problem contacting little_finger but contacting naboo only works on the permanent address with the interface given in the arguments.
So pinging is possible but I can't ssh (on naboo, ssh fe80::ba27:ebff:fe20:3ed5 (to gallifrey) gives an invalid argument).
Note that the switch in use is a TP-Link TL-SF1005D (a really small switch, with no configuration)
Also note that the 3 computers are running archlinux (little_finger and naboo are x86_64 and gallifrey is a raspberry 2 (armv7))
Do you have any thought on that ?
Offline
After checking, packets are being transfered in the direction gallifrey -> naboo but not naboo -> gallifrey.
Also note that there is no problem when using windows on naboo or when using the archlinux installation livecd...
Offline