SixXS::Sunset 2017-06-06

Ticket ID: SIXXS #8348242
Ticket Status: User

PoP: gblon03 - Gyron Internet LTD - Limited UK Company (London)

tunnelrobot reports tunnel down yet tunnel is up.
[gb] Shadow Hawkins on Wednesday, 05 December 2012 00:47:47
Dear Sixxs support, I received an email : This is the tunnelrobot at SixXS, mailing you to inform you that your tunnel to Gyron Internet LTD - Limited UK Company has not been replying to pings for a period of time Here's the information regarding the tunnel: Handle : DJA5-SIXXS PoP Name : gblon03 (uk.gyron [AS29017]) Your Location: Ballyclare, gb SixXS IPv6 : 2a00:14f0:e000:46::1/64 Your IPv6 : 2a00:14f0:e000:46::2/64 SixXS IPv4 : 212.113.147.150 Your IPv4 : 217.37.141.201 Last known responding: 2012-12-03 13:21:48 My tunnel status shows a downtime since 3/12/12. Yet the tunnel is functional, I have not changed anything and I'm able to ping it from an outside IPV6 public server in a London DC and also from SubnetOnline.com :- root@xxxxxx ~# ping6 2a00:14f0:e000:46::2 PING 2a00:14f0:e000:46::2(2a00:14f0:e000:46::2) 56 data bytes 64 bytes from 2a00:14f0:e000:46::2: icmp_seq=1 ttl=51 time=57.1 ms 64 bytes from 2a00:14f0:e000:46::2: icmp_seq=2 ttl=51 time=57.1 ms 64 bytes from 2a00:14f0:e000:46::2: icmp_seq=3 ttl=51 time=56.3 ms 64 bytes from 2a00:14f0:e000:46::2: icmp_seq=4 ttl=51 time=56.4 ms ^C --- 2a00:14f0:e000:46::2 ping statistics --- 5 packets transmitted, 4 received, 20% packet loss, time 4038ms rtt min/avg/max/mdev = 56.373/56.799/57.183/0.440 ms IPv6 Ping Output: PING 2a00:14f0:e000:46::2(2a00:14f0:e000:46::2) 32 data bytes 40 bytes from 2a00:14f0:e000:46::2: icmp_seq=0 ttl=55 time=62.5 ms 40 bytes from 2a00:14f0:e000:46::2: icmp_seq=1 ttl=55 time=79.4 ms 40 bytes from 2a00:14f0:e000:46::2: icmp_seq=2 ttl=55 time=62.2 ms 40 bytes from 2a00:14f0:e000:46::2: icmp_seq=3 ttl=55 time=62.3 ms --- 2a00:14f0:e000:46::2 ping statistics --- 4 packets transmitted, 4 received, 0% packet loss, time 3012ms rtt min/avg/max/mdev = 62.269/66.654/79.482/7.413 ms, pipe 2 Finished! I tried to use the IPV6 traceroute at https://www.sixxs.net/tools/traceroute/ but it says it is temporarily unavailable for all PoPs I tried. IPv6 traceroute IPv6 traceroute from gblon03.sixxs.net @ Gyron Internet LTD - Limited UK Company, AS29017 to 2a00:14f0:e018::1 : Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation Traceroutes from gblon03 are temporarily unavailable Here is a traceroute from the public server in London to an IPV6 address on my subnet, the endpoint is the penultimate hop :- root@xxxxxx ~# traceroute6 -I 2a00:14f0:e018::1 traceroute to 2a00:14f0:e018::1 (2a00:14f0:e018::1), 30 hops max, 80 byte packets 1 vlan-185.cs0.gs2.uk.goscomb.net (2a01:348:0:27::1) 0.915 ms 1.116 ms 1.153 ms 2 xe-0-1-0.cs0.tch.uk.goscomb.net (2a01:348::25:1:1) 1.798 ms 1.876 ms 1.916 ms 3 xe-0-1-0.cs0.mer.uk.goscomb.net (2a01:348::22:1:1) 0.906 ms 0.973 ms 1.006 ms 4 xe-0-1-1.cs0.sov.uk.goscomb.net (2a01:348::23:1:1) 3.744 ms 3.793 ms 3.835 ms 5 ge-1-1-5.rt0.sov.uk.goscomb.net (2a01:348::17:0:1) 0.293 ms 0.299 ms 0.327 ms 6 lonap.he.net (2001:7f8:17::1b1b:1) 11.428 ms 11.195 ms 11.231 ms 7 xe-0-0-3.border-1.sov.lon.uk.as29017.net (2001:7f8:4::7159:1) 0.567 ms 0.596 ms 0.586 ms 8 xe-0-0-1.core-2.centro.hml.uk.as29017.net (2a00:14f0:0:1::a) 1.524 ms 1.520 ms 1.530 ms 9 gblon03.sixxs.net (2a00:14f0:1:2::5) 1.579 ms 1.568 ms 1.502 ms 10 gw-71.lon-03.gb.sixxs.net (2a00:14f0:e000:46::1) 1.505 ms 1.503 ms 1.544 ms 11 2a00:14f0:e018::1 (2a00:14f0:e018::1) 55.689 ms 58.367 ms 60.962 ms root@xxxxxx ~# and again simply to my IPV6 endpoint : root@xxxxxx ~# traceroute6 -I 2a00:14f0:e000:46::2 traceroute to 2a00:14f0:e000:46::2 (2a00:14f0:e000:46::2), 30 hops max, 80 byte packets 1 vlan-185.cs0.gs2.uk.goscomb.net (2a01:348:0:27::1) 0.901 ms 0.949 ms 0.996 ms 2 xe-0-1-0.cs0.tch.uk.goscomb.net (2a01:348::25:1:1) 1.137 ms 1.196 ms 1.234 ms 3 xe-0-1-0.cs0.mer.uk.goscomb.net (2a01:348::22:1:1) 0.976 ms 1.042 ms 1.074 ms 4 xe-0-1-1.cs0.sov.uk.goscomb.net (2a01:348::23:1:1) 1.878 ms 1.959 ms 1.996 ms 5 ge-1-1-5.rt0.sov.uk.goscomb.net (2a01:348::17:0:1) 0.316 ms 0.322 ms 0.349 ms 6 lonap.he.net (2001:7f8:17::1b1b:1) 10.412 ms 10.159 ms 10.195 ms 7 xe-0-0-3.border-1.sov.lon.uk.as29017.net (2001:7f8:4::7159:1) 0.601 ms 0.599 ms 0.584 ms 8 xe-0-0-1.core-2.centro.hml.uk.as29017.net (2a00:14f0:0:1::a) 1.551 ms 1.544 ms 1.537 ms 9 gblon03.sixxs.net (2a00:14f0:1:2::5) 1.530 ms 1.523 ms 1.533 ms 10 gw-71.lon-03.gb.sixxs.net (2a00:14f0:e000:46::1) 1.520 ms 1.560 ms 1.526 ms 11 cl-71.lon-03.gb.sixxs.net (2a00:14f0:e000:46::2) 55.280 ms 60.213 ms 57.207 ms root@xxxxxx ~# If you could point me in the direction of the problem I will certainly fix it as I'm at a loss as to what could have changed or what cold have gone wrong. Thank you in advance for your help. Yours Sincerely Dr Allen.
State change: user Locked
[ch] Jeroen Massar SixXS Staff on Wednesday, 05 December 2012 01:31:16
Message is Locked
The state of this ticket has been changed to user
tunnelrobot reports tunnel down yet tunnel is up.
[ch] Jeroen Massar SixXS Staff on Wednesday, 05 December 2012 01:32:13
Yet the tunnel is functional, I have not changed anything and I'm able to ping it from an outside IPV6 public server in a London DC and also from SubnetOnline.com :-
[..]
If you could point me in the direction of the problem I will certainly fix it as I'm at a loss as to what could have changed or what cold have gone wrong.
Please read the FAQ and understand that the PoP pings you, not some random site on the Internet.
tunnelrobot reports tunnel down yet tunnel is up.
[gb] Shadow Hawkins on Wednesday, 05 December 2012 10:36:20
Jeroen, thanks for getting back to me. I have fully read the FAQ and I do understand that the PoP pings my endpoint. That doesn't however help me understand why it couldn't ping me. I only included the pings and traceroute's to demonstate that other, random, sites could ping without problem. I'm running kernel 3.4.11 and even wondered if it was a recent kernel update that caused it. I assure you I think I have, and had, checked all I could before posting. I've checked the tunnel status and shortly after posting this ticket, the graphs, seem to show that it started working again. I changed nothing and would really like to know why it stopped then appears to have now started again. Transient route problem? Should we just leave it and keep an eye on it ? The traceroute at https://www.sixxs.net/tools/traceroute/ still won't let me test from the gblon03 end --------------- IPv6 traceroute IPv6 traceroute from gblon03.sixxs.net @ Gyron Internet LTD - Limited UK Company, AS29017 to 2a00:14f0:e018::1 : Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation Traceroutes from gblon03 are temporarily unavailable When the ASN of a prefix is blank then the prefix doesn't have an route6 entry in the registries. --------------- Can you try from your end just to assure me that gblon03 is happy? Cheers, and many thanks, Jim :-)
tunnelrobot reports tunnel down yet tunnel is up.
[ch] Jeroen Massar SixXS Staff on Wednesday, 05 December 2012 12:51:39
I have fully read the FAQ
If you have read the FAQ, where are the answers to the question it asks? Or even the answers to the "Reporting Problems" list that the big yellow/orange box alludes to when posting?
I only included the pings and traceroute's to demonstate that other, random, sites could ping without problem
Which, as stated in the FAQ is irrelevant.
shortly after posting this ticket, the graphs, seem to show that it started working again.
Sounds like connection tracking issues to me. But if you had read the FAQ you would have come to that conclusion.
Can you try from your end just to assure me that gblon03 is happy?
Please actually read and provide the information requested. We really do not have time to play helpdesk for everybody, hence why we have a FAQ (Frequently Asked Questions)

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

Static Sunset Edition of SixXS
©2001-2017 SixXS - IPv6 Deployment & Tunnel Broker