Good evening, That's now the second time, the tunnel T116214 (aiccu controlled) drops all traffics. Tunnel is up, restart aiccu didn't solve the issue. Network config is fetched but I'm not able to reach the remote peer and beyond. # ip a s dev sixxs 14: sixxs: <POINTOPOINT,NOARP,UP,LOWER_UP> mtu 1280 qdisc noqueue state UNKNOWN group default link/sit 192.168.1.2 peer 78.153.240.201 inet6 2a01:240:fe00:22b::2/64 scope global valid_lft forever preferred_lft forever inet6 fe80::c0a8:f40b/64 scope link valid_lft forever preferred_lft forever inet6 fe80::c0a8:f5fe/64 scope link valid_lft forever preferred_lft forever inet6 fe80::c0a8:102/64 scope link valid_lft forever preferred_lft forever The first time issue appear, the problem was gone after few time. You can see that on the drop graph you provide on the tunnel stats. On my side, no config change on the router, but I switched from internet provider. New one, doesn't provide static IP address. IPv4 in tunnel info is correct. I cannot capture an inbound packet from the tunnel interface. Here is an aiccu test; # aiccu test ####### ####### AICCU Quick Connectivity Test ####### ####### [1/8] Ping the IPv4 Local/Your Outer Endpoint (192.168.1.2) ### This should return so called 'echo replies' ### If it doesn't then check your firewall settings ### Your local endpoint should always be pingable ### It could also indicate problems with your IPv4 stack PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_seq=1 ttl=64 time=0.197 ms 64 bytes from 192.168.1.2: icmp_seq=2 ttl=64 time=0.164 ms 64 bytes from 192.168.1.2: icmp_seq=3 ttl=64 time=0.126 ms --- 192.168.1.2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2007ms rtt min/avg/max/mdev = 0.126/0.162/0.197/0.030 ms ###### Did this work? [Y/n] y ####### [2/8] Ping the IPv4 Remote/PoP Outer Endpoint (78.153.240.201) ### These pings should reach the PoP and come back to you ### In case there are problems along the route between your ### host and the PoP this could not return replies ### Check your firewall settings if problems occur PING 78.153.240.201 (78.153.240.201) 56(84) bytes of data. 64 bytes from 78.153.240.201: icmp_seq=1 ttl=55 time=12.3 ms 64 bytes from 78.153.240.201: icmp_seq=2 ttl=55 time=12.7 ms 64 bytes from 78.153.240.201: icmp_seq=3 ttl=55 time=12.1 ms --- 78.153.240.201 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2008ms rtt min/avg/max/mdev = 12.138/12.410/12.741/0.249 ms ###### Did this work? [Y/n] y ####### [3/8] Traceroute to the PoP (78.153.240.201) over IPv4 ### This traceroute should reach the PoP ### In case this traceroute fails then you have no connectivity ### to the PoP and this is most probably the problem traceroute to 78.153.240.201 (78.153.240.201), 30 hops max, 60 byte packets 1 192.168.1.254 (192.168.1.254) 0.659 ms 0.612 ms 0.645 ms 2 80.10.123.200 (80.10.123.200) 2.582 ms 1.993 ms 3.635 ms 3 10.123.109.10 (10.123.109.10) 3.645 ms 10.123.109.74 (10.123.109.74) 3.466 ms 3.599 ms 4 193.252.98.177 (193.252.98.177) 3.569 ms 3.539 ms 193.252.98.161 (193.252.98.161) 3.499 ms 5 81.253.184.14 (81.253.184.14) 4.671 ms 81.253.184.86 (81.253.184.86) 4.218 ms 4.164 ms 6 tengige0-7-0-7.auvtr4.Aubervilliers.opentransit.net (193.251.132.14) 5.080 ms 3.001 ms te8-3.parse1.Paris.opentransit.net (193.251.128.70) 1.826 ms 7 te5-1.er01.par01.jaguar-network.net (193.251.247.226) 1.847 ms te3-1.parse1.Paris.opentransit.net (193.251.128.230) 2.502 ms te5-1.er01.par01.jaguar-network.net (193.251.247.226) 2.412 ms 8 sixxs.cust.jaguar-network.net (78.153.224.50) 13.043 ms 13.022 ms te5-1.er01.par01.jaguar-network.net (193.251.247.226) 2.540 ms 9 sixxs.cust.jaguar-network.net (78.153.224.50) 12.845 ms 13.022 ms 18.592 ms 10 78.153.240.201 (78.153.240.201) 12.889 ms 12.845 ms 12.121 ms ###### Did this work? [Y/n] y ###### [4/8] Checking if we can ping IPv6 localhost (::1) ### This confirms if your IPv6 is working ### If ::1 doesn't reply then something is wrong with your IPv6 stack PING ::1(::1) 56 data bytes 64 bytes from ::1: icmp_seq=1 ttl=64 time=0.210 ms 64 bytes from ::1: icmp_seq=2 ttl=64 time=0.141 ms 64 bytes from ::1: icmp_seq=3 ttl=64 time=0.154 ms --- ::1 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2007ms rtt min/avg/max/mdev = 0.141/0.168/0.210/0.031 ms ###### Did this work? [Y/n] y ###### [5/8] Ping the IPv6 Local/Your Inner Tunnel Endpoint (2a01:240:fe00:22b::2) ### This confirms that your tunnel is configured ### If it doesn't reply then check your interface and routing tables PING 2a01:240:fe00:22b::2(2a01:240:fe00:22b::2) 56 data bytes 64 bytes from 2a01:240:fe00:22b::2: icmp_seq=1 ttl=64 time=0.183 ms 64 bytes from 2a01:240:fe00:22b::2: icmp_seq=2 ttl=64 time=0.137 ms 64 bytes from 2a01:240:fe00:22b::2: icmp_seq=3 ttl=64 time=0.128 ms --- 2a01:240:fe00:22b::2 ping statistics --- 3 packets transmitted, 3 received, 0% packet loss, time 2004ms rtt min/avg/max/mdev = 0.128/0.149/0.183/0.026 ms ###### Did this work? [Y/n] y ###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2a01:240:fe00:22b::1) ### This confirms the reachability of the other side of the tunnel ### If it doesn't reply then check your interface and routing tables ### Don't forget to check your firewall of course ### If the previous test was successful then this could be both ### a firewalling and a routing/interface problem PING 2a01:240:fe00:22b::1(2a01:240:fe00:22b::1) 56 data bytes --- 2a01:240:fe00:22b::1 ping statistics --- 3 packets transmitted, 0 received, 100% packet loss, time 2011ms ###### Did this work? [Y/n] n Traceroute does't reach 78.153.240.201 each try. Sometimes it ends on sixxs.cust.jaguar-network.net. Regards,