Hello,
Ipv6 works fine from the router itself:
root@lgr5g:~# ping6 -c 1 2a00:1288:110:c305::1:8000
PING 2a00:1288:110:c305::1:8000 (2a00:1288:110:c305::1:8000): 56 data bytes
64 bytes from 2a00:1288:110:c305::1:8000: seq=0 ttl=53 time=58.981 ms
--- 2a00:1288:110:c305::1:8000 ping statistics ---
1 packets transmitted, 1 packets received, 0% packet loss
round-trip min/avg/max = 58.981/58.981/58.981 ms
but not from any other device on the lan:
[root@lgtsn]# ping6 -c 1 2a00:1288:110:c305::1:8000
PING 2a00:1288:110:c305::1:8000(2a00:1288:110:c305::1:8000) 56 data bytes
--- 2a00:1288:110:c305::1:8000 ping statistics ---
1 packets transmitted, 0 received, 100% packet loss, time 0ms
A tcpdump on the router shows:
root@lgr5g:~# tcpdump -i any -n -v 'icmp6 or host 2a00:1288:110:c305::1:8000'
tcpdump: data link type LINUX_SLL2
tcpdump: listening on any, link-type LINUX_SLL2 (Linux cooked v2), snapshot length 262144 bytes
12:58:28.768185 eth0 In IP6 (flowlabel 0xf2fea, hlim 64, next-header ICMPv6 (58) payload length: 64) 2a0d:e487:41f:e334::262 > 2a00:1288:110:c305::1:8000: [icmp6 sum ok] ICMP6, echo request, id 5, seq 1
12:58:28.768185 br-lan In IP6 (flowlabel 0xf2fea, hlim 64, next-header ICMPv6 (58) payload length: 64) 2a0d:e487:41f:e334::262 > 2a00:1288:110:c305::1:8000: [icmp6 sum ok] ICMP6, echo request, id 5, seq 1
12:58:28.768384 qmimux0 Out IP6 (flowlabel 0xf2fea, hlim 63, next-header ICMPv6 (58) payload length: 64) 2a0d:e487:41f:e334::262 > 2a00:1288:110:c305::1:8000: [icmp6 sum ok] ICMP6, echo request, id 5, seq 1
12:58:28.827705 qmimux0 In IP6 (flowlabel 0xf2fea, hlim 52, next-header ICMPv6 (58) payload length: 64) 2a00:1288:110:c305::1:8000 > 2a0d:e487:41f:e334::262: [icmp6 sum ok] ICMP6, echo reply, id 5, seq 1
12:58:28.827861 qmimux0 Out IP6 (flowlabel 0xf2fea, hlim 51, next-header ICMPv6 (58) payload length: 64) 2a00:1288:110:c305::1:8000 > 2a0d:e487:41f:e334::262: [icmp6 sum ok] ICMP6, echo reply, id 5, seq 1
So the server replies, but the icmp echo reply isn’t forwarded from qmimux0 to br-lan.
There is nothing suspicious in the rules table, and stopping the firewall doesn’t help.
Any idea ?
Regards,