|
Ticket ID: SIXXS #5986902 Ticket Status: Remote Problem PoP: gblon03 - Gyron Internet LTD - Limited UK Company (London)
Intermittent route via gw-71.lon-03.gb.sixxs.net
![[gb]](/s/countries/gb.gif) Shadow Hawkins on Monday, 28 November 2011 15:03:18
UN/TUNNEL DJA5-SIXXS/T68573
Please forgive me if this ends up as a double post. I read the "reporting problems page" but failed to notice the "New ticket" button so I have already sent this to the info@ address from my personal email. I then discovered the button and realised I needed to submit this as a logged in user. Again, my apologies for any confusion caused.
Original email :-
Dear Sir/Madam,
I have a test server at ipv6.phinetworksystems.co.uk (2a02:af8:3:1900::7861)
For some time now it's IPV6 connection has proved intermittent. I have now
attempted to trace the problem and discovered that the problem seems to
only be via my Sixxs PoP. I have tried several traces via different PoP's
and also using my own PoP. The problem only occurs when routing via my
gblon03 PoP route (Tunnel T68573). The problem comes and goes, but when it
does happen my connection seems to be getting routed via a US gateway
2001:4830:d1:15::1.
Traceroute just now :-
> root@stargate ~# traceroute ipv6.phinetworksystems.co.uk > traceroute to ipv6.phinetworksystems.co.uk (2a02:af8:3:1900::7861), 30 hops max, 80 byte packets > 1 gw-71.lon-03.gb.sixxs.net (2a00:14f0:e000:46::1) 47.853 ms 49.680 ms 51.616 ms > 2 ge-2-0-1-1027.core-1.lhc.lon.uk.as29017.net (2a00:14f0:1:2::2) 55.292 ms 57.201 ms 59.134 ms > 3 ae0.border-1.sov.lon.uk.as29017.net (2a00:14f0:0:1::6) 63.080 ms 65.280 ms 67.207 ms > 4 2001:4830:d1:15::1 (2001:4830:d1:15::1) 68.205 ms 79.391 ms 79.585 ms > 5 * * *
and yet using ipv6 ping6 at subnetonline.com again just now.
> IPv6 Ping Output: > > PING 2a02:af8:3:1900::7861(2a02:af8:3:1900::7861) 32 data bytes > 40 bytes from 2a02:af8:3:1900::7861: icmp_seq=0 ttl=57 time=9.00 ms > 40 bytes from 2a02:af8:3:1900::7861: icmp_seq=1 ttl=57 time=8.83 ms > 40 bytes from 2a02:af8:3:1900::7861: icmp_seq=2 ttl=57 time=8.90 ms > 40 bytes from 2a02:af8:3:1900::7861: icmp_seq=3 ttl=57 time=8.84 ms > > --- 2a02:af8:3:1900::7861 ping statistics --- > 4 packets transmitted, 4 received, 0% packet loss, time 3035ms > rtt min/avg/max/mdev = 8.835/8.898/9.006/0.067 ms, pipe 2 > > Finished!
No problem.
This same route/problem was occurring last night at 22:41 and then
magically fixed itself at 22:51. After which it was getting correctly
routed all night. Then again today at 12:35 it is happening again. Whether
this happens or not, I'm always able to ping6 and traceroute6 via other
PoP's and online ping6/trace tools. I have included a few traces here done
last night using your https://www.sixxs.net/tools/traceroute/ tool:-
> IPv6 traceroute from iedub01.sixxs.net @ HEAnet, AS1213 to 2a02:af8:3:1900::7861 : > Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation > 1.|-- 2001:770:18:8::1 0.0% 5 0.5 9.5 0.4 45.2 20.0 [.ie] Ireland 1213 HEAnet > blanch-sr1-vlan8.services.hea.net. > 2.|-- 2001:770:400:60::1 0.0% 5 2.1 2.3 2.1 2.7 0.2 [.ie] Ireland 1213 HEAnet > te0-8-0-1-cr2-cwt.hea.net. > 3.|-- 2001:668:0:3::c000:71 0.0% 5 1.3 4.5 1.3 15.4 6.2 [.eu] Europe 3257 Tiscali International Network B.V. > xe-2-1-0.dub20.ip6.tinet.net. > 4.|-- 2001:668:0:2::2 0.0% 5 11.4 15.5 11.4 32.0 9.2 [.eu] Europe 3257 Tiscali International Network B.V. > xe-4-1-0.lon21.ip6.tinet.net. > 5.|-- 2001:668:0:3::4000:352 0.0% 5 107.6 120.2 99.5 181.9 34.8 [.eu] Europe 3257 Tiscali International Network B.V. > blueconnex-gw.ip6.tinet.net. > 6.|-- 2a02:af8:0:1::2 0.0% 5 98.6 104.4 98.6 112.5 5.4 [.gb] United Kingdom (Great Britain) 29550 BlueConnex MK Ltd > vl667.the-7600.ip6.as29550.net. > 7.|-- 2a02:af8:0:3::2 0.0% 5 103.6 108.2 103.6 112.1 3.7 [.gb] United Kingdom (Great Britain) 29550 BlueConnex MK Ltd > a.3.magic-the.ip6.as29550.net. > 8.|-- 2a02:af8:3:1900::7861 0.0% 5 111.1 110.7 107.5 112.4 2.0 [.gb] United Kingdom (Great Britain) 29550 BlueConnex MK Ltd > > IPv6 traceroute from gblon02.sixxs.net @ Goscomb Technologies, AS39326 to 2a02:af8:3:1900::7861 : > Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation > 1. 2a01:348:0:4:0:3:0:1 0.0% 5 1.3 1.1 0.9 1.3 0.2 [.gb] United Kingdom (Great Britain) 39326 Goscomb Technologies Limited > ge-0-0-5-20.cs0.thw.uk.goscomb.net. > 2. 2a01:348::27:0:1 0.0% 5 16.9 5.0 0.5 16.9 7.1 [.gb] United Kingdom (Great Britain) 39326 Goscomb Technologies Limited > xe-0-0-0.rt0.the.uk.goscomb.net. > 3. 2a01:348:0:4:0:22:1:1 0.0% 5 0.7 26.1 0.7 84.2 36.4 [.gb] United Kingdom (Great Britain) 39326 Goscomb Technologies Limited > goscomb-pni.as29550.net. > 4. 2a02:af8:0:3::2 0.0% 5 2.3 3.7 2.3 8.0 2.4 [.gb] United Kingdom (Great Britain) 29550 BlueConnex MK Ltd > a.3.magic-the.ip6.as29550.net. > 5. 2a02:af8:3:1900::7861 0.0% 5 1.5 1.4 1.3 1.6 0.1 [.gb] United Kingdom (Great Britain) 29550 BlueConnex MK Ltd > > IPv6 traceroute from beanr01.sixxs.net @ EDPnet N.V., AS9031 to 2a02:af8:3:1900::7861 : > Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation > 1. 2a02:578:1:8::1 0.0% 5 1.7 8.0 0.5 35.3 15.3 [.be] Belgium 9031 Eurocarrier GEIE > 2. 2a02:578:1:e::2 0.0% 5 1.6 1.4 1.4 1.6 0.1 [.be] Belgium 9031 Eurocarrier GEIE > 3. 2a02:578:1:2e::2 0.0% 5 6.8 6.8 6.7 6.8 0.0 [.be] Belgium 9031 Eurocarrier GEIE > 4. 2001:7f8:4::736e:1 0.0% 5 74.7 74.8 74.7 75.4 0.3 [.gb] United Kingdom (Great Britain) London Internet Exchange (LINX) > the-linx.as29550.net. > 5. 2a02:af8:0:3::2 0.0% 5 79.0 77.5 76.4 79.0 1.1 [.gb] United Kingdom (Great Britain) 29550 BlueConnex MK Ltd > a.3.magic-the.ip6.as29550.net. > 6. 2a02:af8:3:1900::7861 0.0% 5 75.6 75.5 75.4 75.6 0.1 [.gb] United Kingdom (Great Britain) 29550 BlueConnex MK Ltd
> IPv6 traceroute from gblon03.sixxs.net @ Gyron Internet LTD - Limited UK Company, AS29017 to 2a02:af8:3:1900::7861 : > Hop Node Loss% Sent Last Avg Best Worst StDev ASN Organisation > 1. 2a00:14f0:1:2::2 0.0% 5 0.4 0.4 0.3 0.4 0.0 [.gb] United Kingdom (Great Britain) 29017 Gyron Internet Ltd > ge-2-0-1-1027.core-1.lhc.lon.uk.as29017.net. > 2. 2a00:14f0:0:1::6 0.0% 5 0.5 2.0 0.4 8.2 3.5 [.gb] United Kingdom (Great Britain) 29017 Gyron Internet Ltd > ae0.border-1.sov.lon.uk.as29017.net. > 3. 2001:4830:d1:15::1 0.0% 5 0.6 0.6 0.5 0.6 0.0 [.us] United States 30071 TowardEX Technologies Network > 4. ??? 100.0 5 0.0 0.0 0.0 0.0 0.0
Some of these traces can set-off the Port scanning detection on this server if
tried twice in a row, or the hop count is high etc. But I have checked the firewall logs and
temp/denied tables and this does not appear to be the cause of this
particular problem.
Can I ask if it possible for you to see why this route ends up going via a
GW in the US. I don't have a record of the trace via gblon03 when it does
work (I wish I had copied it from the terminal last night). If it magically
fixes itself again, I will certainly submit it as an update to this ticket
right away.
Please also advise if the problem lies within the BlueConnex system so that
I can instead request help from them towards getting the problem fixed.
If you need anything further in terms of tests or settings please do not
hesitate to request it from me.
Thank you for your help,
Your Sincerely
James :-)
-- Dr James Allen Domain Administrator Phi Network Systems
State change: remoteproblem
The state of this ticket has been changed to remoteproblem
Intermittent route via gw-71.lon-03.gb.sixxs.net
First try I gave to check this from a different location gave:
traceroute to 2a02:af8:3:1900::7861 (2a02:af8:3:1900::7861), 30 hops max, 80 byte packets
1 ge-1-3-0.breda.ipv6.concepts-ict.net (2001:838:1:1::1) 0.486 ms 0.605 ms 0.731 ms
2 gi2-11.nikhef.ipv6.concepts-ict.net (2001:838:5:a::1) 4.735 ms 4.733 ms 4.716 ms
3 20gigabitethernet1-3.core1.ams1.ipv6.he.net (2001:7f8:1::a500:6939:1) 4.681 ms 4.679 ms 4.641 ms
4 10gigabitethernet1-4.core1.lon1.he.net (2001:470:0:3f::1) 12.429 ms 12.535 ms 12.465 ms
5 the-linx.as29550.net (2001:7f8:4::736e:1) 12.543 ms 12.565 ms 12.627 ms
6 vl667.hex-7600.ip6.as29550.net (2a02:af8:0:1::1) 17.601 ms * *
7 a.3.magic-hex.ip6.as29550.net (2a02:af8:0:2::2) 22.305 ms 18.692 ms 21.499 ms
8 * * *
9 * * *
10 * * *
I think there is a routing issue at the remote location. Not much we can do about.
I've forwarded the ticket though to Goscomb as UK ISPs generally are close to each other thus maybe they can inform the right people to resolve this.
Intermittent route via gw-71.lon-03.gb.sixxs.net
Shadow Hawkins on Monday, 28 November 2011 15:12:14
Many thanks Jeroen.
I'll now poke them at the hosting side too and see if I can get movement from that end.
Cheers,
and many thanks again for replying so quickly.
Jim :-)
Intermittent route via gw-71.lon-03.gb.sixxs.net
Shadow Hawkins on Saturday, 03 December 2011 00:00:26
Jeroen,
sorry to trouble you with this again but I have been ping6'ing and traceroute6'ing for 4 days now and the route to ipv6.phinetworksystems.co.uk via my gblon03 tunnel is the only route that I can find that fails to this host.
I noticed that your trace ended at 2a02:af8:0:3::2 (a.3.magic-the.ip6.as29550.net.) that's the last hop before my host. So I wondered if maybe your trace failed because you were using a UDP port increment hop trace.
I scanned my firewall logs and if your IP was 2001:0838:0001:0001:0210:dcff:fe20:7c7c ( noc.sixxs.net.) then yes you triggered a port scan block.
I thank you very much for looking at this for me, but over the last week this tunnel has had a 56% success of reaching this host. It has now been unavailable for two solid days.
Is there any chance I could ask you to look at it again. I'm not saying you are incorrect that it is a remote problem but I can't find any other route that causes a trace to go via 2001:4830:d1:15::1 (TowardEx).
If possible could you try a ping6 first and then trace.
Also if your version of traceroute has the option to use ICMP (-I) could you try that.
~# traceroute6 -I ipv6.phinetworksystems.co.uk
I have been runnig down the PoP's traceing from them and so far gblon03 is the only one to fail to reach 2a02:af8:3:1900::7861.
Thank you very much in advance.
Jim :-)
Intermittent route via gw-71.lon-03.gb.sixxs.net
Shadow Hawkins on Saturday, 03 December 2011 12:59:55
Jeroen,
The route is working again and I said I'd post the traceroute next time I caught it. :-
root@stargate ~# traceroute6 -I ipv6.phinetworksystems.co.uk
traceroute to ipv6.phinetworksystems.co.uk (2a02:af8:3:1900::7861), 30 hops max, 80 byte packets
1 gw-71.lon-03.gb.sixxs.net (2a00:14f0:e000:46::1) 32.963 ms 36.412 ms 40.158 ms
2 ge-2-0-1-1027.core-1.lhc.lon.uk.as29017.net (2a00:14f0:1:2::2) 43.399 ms 47.392 ms 50.883 ms
3 ae0.border-1.sov.lon.uk.as29017.net (2a00:14f0:0:1::6) 54.612 ms 58.602 ms 61.858 ms
4 2001:4830:d1:15::1 (2001:4830:d1:15::1) 65.353 ms 69.346 ms 73.085 ms
5 hex89-linx.as29550.net (2001:7f8:4:1::736e:1) 76.578 ms * *
6 a.3.magic-hex.ip6.as29550.net (2a02:af8:0:2::2) 87.304 ms 57.024 ms 58.573 ms
7 2a02:af8:3:1900::7861 (2a02:af8:3:1900::7861) 57.310 ms 55.893 ms 55.309 ms
root@stargate ~#
root@frodo ~# traceroute6 -I 2a00:14f0:e018::1
traceroute to 2a00:14f0:e018::1 (2a00:14f0:e018::1), 30 hops max, 40 byte packets
1 2a02:af8:3:1900::1 (2a02:af8:3:1900::1) 4.397 ms 4.622 ms 4.661 ms
2 hex-a.3.magic.ip6.as29550.net (2a02:af8:0:2::1) 6.820 ms 7.343 ms *
3 vl667.the-7600.ip6.as29550.net (2a02:af8:0:1::2) 1.639 ms 1.671 ms 1.708 ms
4 ae1.border-1.sov.lon.uk.as29017.net (2001:7f8:17::7159:1) 1.944 ms 1.944 ms 1.950 ms
5 xe-0-0-1.border-1.thn.lon.uk.as29017.net (2a00:14f0:0:1::19) 1.940 ms 1.939 ms 1.989 ms
6 ae4.core-2.lhc.lon.uk.as29017.net (2a00:14f0:0:1::16) 2.104 ms 2.021 ms 2.059 ms
7 gblon03.sixxs.net (2a00:14f0:1:2::5) 2.037 ms 2.052 ms 2.050 ms
8 2a00:14f0:e018::1 (2a00:14f0:e018::1) 37.208 ms 39.733 ms 42.410 ms
root@frodo ~#
Cheers,
Jim.
Intermittent route via gw-71.lon-03.gb.sixxs.net
This is a problem involving peering at an ISP outside our scope, please contact them for resolving this issue.
Intermittent route via gw-71.lon-03.gb.sixxs.net
Shadow Hawkins on Tuesday, 06 December 2011 13:51:48
Thanks Jeroen,
I'd love to, even if only to be re-assured that someone is doing something about it. At the minute I'm geting passed around.
Any idea how I can contact them and what I should include in my request, so as to actually get the right person to investigate and act.
Cheers,
Jim :-)
Intermittent route via gw-71.lon-03.gb.sixxs.net
It is outside of any of the PoP's network, we unfortunately do not have time to go around and contact folks around the Internet to get their networks fixed.
If you want to reach the ISP, whois should be able to give you good initial contacts.
Intermittent route via gw-71.lon-03.gb.sixxs.net
Shadow Hawkins on Saturday, 17 December 2011 14:58:45
Jeroen,
My NOC at Maidenhead contacted Gyron and raised a ticket. The Gyron engineers reported that they had an issue in their network with one of their other peers leaking them incorrect routes.
On the 12th Dec they changed my route and all has been 100% since then.
My route is now :
root@stargate ~# traceroute6 -I ipv6.phinetworksystems.co.uk
traceroute to ipv6.phinetworksystems.co.uk (2a02:af8:3:1900::7861), 30 hops max, 80 byte packets
1 gw-71.lon-03.gb.sixxs.net (2a00:14f0:e000:46::1) 47.792 ms 50.008 ms 51.992 ms
2 ge-2-0-1-1027.core-1.lhc.lon.uk.as29017.net (2a00:14f0:1:2::2) 55.494 ms 57.975 ms 60.234 ms
3 ae0.border-1.sov.lon.uk.as29017.net (2a00:14f0:0:1::6) 63.724 ms 65.714 ms 67.463 ms
4 lonap.as29550.net (2001:7f8:17::736e:1) 69.453 ms 73.194 ms 75.440 ms
5 a.3.magic-the.ip6.as29550.net (2a02:af8:0:3::2) 79.181 ms 90.919 ms 92.913 ms
6 2a02:af8:3:1900::7861 (2a02:af8:3:1900::7861) 87.393 ms 50.387 ms 51.075 ms
root@stargate ~#
So we can now close this as solved.
Cheers,
Jim :-)
|
![[ch]](/s/countries/ch.gif)
on Monday, 28 November 2011 15:05:12
Posting is only allowed when you are