Ticket ID: SIXXS #1080439 Ticket Status: Resolved PoP: sesto01 - Availo (Stockholm)
No IPv6 connectivity
Shadow Hawkins on Thursday, 07 May 2009 16:07:04
My ID is MWI2-SIXXS, using tunnel T15207 to sesto01.
After about 14:00 today, 2009-05-07, IPv6 connectivity through the
tunnel stopped. Running aiccu test stops working here:
###### [6/8] Ping the IPv6 Remote/PoP Inner Tunnel Endpoint (2001:16d8:ff00:243::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 succesful then this could be both
### a firewalling and a routing/interface problem
PING6(56=40+8+8 bytes) 2001:16d8:ff00:243::2 --> 2001:16d8:ff00:243::1
--- 2001:16d8:ff00:243::1 ping6 statistics ---
3 packets transmitted, 0 packets received, 100.0% packet loss
######
I tested with and without firewall rules enabled with the same
result. Listening with tcpdump on the tunnel interface I see only
traffic going out, nothing coming back from sesto01.
Looking at the traffic graphs for sesto01, I see traffic has dropped
to zero quite recently, so maybe I'm not alone:
https://www.sixxs.net/misc/traffic/?pop=sesto01&last=1day
A traceroute6 from a server in co-lo at XS4All towards my tunnel endpoint:
ecki:~ % traceroute6 -n 2001:16d8:ff00:243::2
traceroute6 to 2001:16d8:ff00:243::2 (2001:16d8:ff00:243::2) from
2001:888:22b3::2, 64 hops max, 12 byte packets
1 2001:888:22b3::1 0.510 ms 0.465 ms 0.486 ms
2 2001:888:0:114::1 0.483 ms 0.487 ms 0.489 ms
3 2001:888:2:2::1 0.985 ms 0.986 ms 0.989 ms
4 2001:470:0:e8::1 0.987 ms 0.986 ms 0.989 ms
5 2001:7f8:1::a501:6150:1 2.485 ms 1.486 ms 1.488 ms
6 2001:16d8:1:1308::72 12.480 ms 12.479 ms 12.483 ms
7 2001:16d8:1:1306::73 12.979 ms 13.478 ms 12.986 ms
8 2001:16d8:1:1317::84 32.464 ms 33.466 ms 33.470 ms
9 2001:16d8:1:1316::87 33.966 ms 33.967 ms 33.470 ms
10 * * *
Please tell me if I can do anything more.
State change: resolved
Jeroen Massar on Thursday, 07 May 2009 16:12:58
The state of this ticket has been changed to resolved
Posting is only allowed when you are logged in. |