Tickets - Tunnel downtime complaints :: SixXS - IPv6 Deployment & Tunnel Broker

Ticket ID: SIXXS #11729585
Ticket Status: User

PoP: ruled01 - EDPnet N.V. (St.Petersburg)

Tunnel downtime complaints

Shadow Hawkins on Monday, 02 June 2014 19:53:13

I have tunnel downtime complaints coming to my mail for over a week: "Tunnel Downtime for AKJ9-SIXXS's 2a02:578:5002:5::2" My tunnel was already automatically switched off once. The whole thing cost me 90 ISKs, however the problem is not on my side: ICMPv6 echo packets are simply not coming to my side of the tunnel while I can ping the PoP side of the tunnel just fine with both IPv4 and IPv6. There must be something wrong either with the PoP or with the tunnelrobot. Please fix! traceroute6 to www.google.com (2a00:1450:4010:c04::69) from 2a02:578:5002:5::2, 64 hops max, 12 byte packets 1 gw-6.led-01.ru.sixxs.net 1.993 ms 1.539 ms 1.498 ms 2 ruled01.sixxs.net 1.497 ms 1.569 ms 1.561 ms 3 2a02:578:5001:2::1 3.461 ms 2.076 ms 1.835 ms 4 2a02:578:1:46::2 35.197 ms 2.553 ms 2.090 ms 5 2a02:578:1:38::1 14.583 ms 14.612 ms 14.084 ms 6 2a02:578:1:49::1 42.719 ms 42.537 ms 42.564 ms 7 amsix-router.google.com 42.417 ms 42.439 ms 43.263 ms

Tunnel downtime complaints

Jeroen Massar SixXS Staff

on Monday, 02 June 2014 20:52:58

There is a FAQ item for this, please actually read it, it does not involve anything google.

Tunnel downtime complaints

Shadow Hawkins on Tuesday, 03 June 2014 07:53:25

Yeah, I've actually read it more than once and it is not helpful. If you'd found time to actually read my ticket and check my tunnel, you would find out that it worked for years and now suddenly broke without any change on my side. And even now metric sometimes shows zero packet loss for short periods of time. Please read again: there are no ICMPv6 echo requests coming from your side. That's why your robot "thinks" that the tunnel is down while it isn't. It has nothing to do with firewall or anything else on my side.

Tunnel downtime complaints

Jeroen Massar SixXS Staff

on Tuesday, 03 June 2014 08:00:13

Yeah, I've actually read it more than once and it is not helpful.

What part is not helpful? Did you note the bulletpointed list in the relevant FAQ entry? Why are you not providing the details requested?

If you'd found time to actually read my ticket and check my tunnel

Without you providing any technical details as very clearly requested, there is nothing for us to check. If the robot is telling you that your tunnel does not ping, then that is exactly what we'll see by manually checking too.

And even now metric sometimes shows zero packet loss for short periods of time.

Sounds a lot like a pattern that is answered in the FAQ item.

there are no ICMPv6 echo requests coming from your side

As per the Live Tunnel Status, they are being sent, you are just not properly seeing or answering them. excerpt:

Latency Pkt Sent        : 7
Latency Pkt Recv        : 7
Latency Loss            : 0.00
Latency Min             : 2.67 ms
Latency Avg             : 3.00 ms
Latency Max             : 3.70 ms

The FAQ item has the answer to your problem. Though, that is a very educated guess as you are not providing any single detail.

Please note Posting is only allowed when you are logged in.