Ticket ID: SIXXS #13826961 Ticket Status: Remote Problem PoP: gblon03 - Gyron Internet LTD - Limited UK Company (London)
cannot route out from gblon03
Shadow Hawkins on Sunday, 21 June 2015 14:27:20
Hello,
My outward ipv6 routing seems to be malfunctioning just outside the tunnel. I can successfully ping gblon03.sixxs.net from my local network via ipv6 but nothing further.
C:\>tracert -6 gblon03.sixxs.net
Tracing route to gblon03.sixxs.net [2a00:14f0:1:2::5]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 2a00:14f0:e000:8123:21d:aaff:fea6:4530
2 12 ms 9 ms 9 ms gw-292.lon-03.gb.sixxs.net [2a00:14f0:e000:123::1]
3 9 ms 9 ms 10 ms 2a00:14f0:1:2::5
Trace complete.
I can successfully tracert from outside ipv6 tracert tools through to my router
However, I cannot go the other way:
C:\>tracert -6 www.google.com
Tracing route to www.google.com [2a00:1450:4009:80d::2004]
over a maximum of 30 hops:
1 1 ms <1 ms <1 ms 2a00:14f0:e000:8123:21d:aaff:fea6:4530
2 15 ms 9 ms 9 ms gw-292.lon-03.gb.sixxs.net [2a00:14f0:e000:123::
1]
3 12 ms 9 ms 10 ms 2a00:14f0:1:2::5
4 * * * Request timed out.
5 * * * Request timed out.
6 ^C
C:\>ping -6 www.google.com
Pinging www.google.com [2a00:1450:4009:80b::2004] with 32 bytes of data:
Request timed out.
Request timed out.
Request timed out.
Request timed out.
Ping statistics for 2a00:1450:4009:80b::2004:
Packets: Sent = 4, Received = 0, Lost = 4 (100% loss),
When tracing from the outside to the inside the route goes via addresses such as the following - and these particular names do not resolve against say the google dns: xe-1-2-2.core-2.centro.hml.uk.as29017.net.
Is this where the error lies - if I tracert to gblon02.sixxs.net then all the intermediate names do resolve to addresses on global dns servers.
My routing table is:
Destination Interface Flags Metric Next Hop
2A00:14F0:E000:123::/64 WAN2 U 256
2A00:14F0:E000:8123::/64 LAN U 256
2A00:14F0:E000:8123::/64 LAN UGA 1024 2A00:14F0:E000:8123:21D:AAFF:FEA6:4530
FE80::/64 LAN U 256
FE80::/64 WAN2 U 256
FF00::/8 LAN U 256
FF00::/8 WAN2 U 256
::/0 WAN2 UGAF 1024 2A00:14F0:E000:123::1
My details are
Tunnel Name
My First Tunnel
PoP Name
gblon03
PoP Location
London, United Kingdom (Great Britain) United Kingdom (Great Britain)
PoP IPv4
212.113.147.150
TIC Server
tic.sixxs.net (default in AICCU)
Your Location
Oxford, United Kingdom (Great Britain) United Kingdom (Great Britain)
Your IPv4
Heartbeat, currently 82.70.211.118
IPv6 Prefix
2a00:14f0:e000:123::1/64
PoP IPv6
2a00:14f0:e000:123::1
Your IPv6
2a00:14f0:e000:123::2
Created
2013-06-18 22:30:27 UTC
Last Alive
2015-06-21 14:15:14 UTC
Last Dead
2015-06-20 01:15:01 UTC
Uptime
1 days (based on latency check)
Config State
Heartbeat (automatically enabled on the fly)
PoP Status
Live Tunnel Status on the PoP
cannot route out from gblon03
Jeroen Massar on Sunday, 21 June 2015 15:12:57 When tracing from the outside to the inside the route goes via addresses such as the following - and these particular names do not resolve against say the google dns: xe-1-2-2.core-2.centro.hml.uk.as29017.net.
Reverse DNS is irrelevant to actual functional delivery of IP packets.
traceroute to 2a00:1450:4009:80d::2004 (2a00:1450:4009:80d::2004) from 2a00:14f0:1:2::5, 30 hops max, 16 byte packets
1 2a00:14f0:1:2::2 (2a00:14f0:1:2::2) 8.125 ms 0.249 ms 0.224 ms
2 ae3.core-1.maylands.hml.uk.as29017.net (2a00:14f0:0:1::2d) 0.236 ms 0.221 ms 0.24 ms
3 xe-0-0-0.border-1.sov.lon.uk.as29017.net (2a00:14f0:0:1::9) 25.901 ms 1.611 ms 1.644 ms
4 ibr01-ve26.lndn01.occaid.net (2001:7f8:4::7577:1) 2.681 ms 2.676 ms 3.036 ms
5 2001:7f8:4::3b41:1 (2001:7f8:4::3b41:1) 2.835 ms 2.793 ms 2.925 ms
6 2001:4860::1:0:15f (2001:4860::1:0:15f) 3.292 ms 3.729 ms 4.286 ms
7 2001:4860:0:1::124d (2001:4860:0:1::124d) 3.036 ms 2.982 ms 2.897 ms
8 lhr08s07-in-x04.1e100.net (2a00:1450:4009:80d::2004) 2.877 ms 2.827 ms 2.937 ms
6 Po1.ge3-4.br01.gva253.ip-max.net (2a02:2528:102:10::2) 5.178 ms 4.978 ms 4.878 ms
7 ge-1-0-8.border-1.thn.lon.uk.as29017.net (2001:7f8:1::a502:9017:1) 27.148 ms 27.242 ms 27.645 ms
8 xe-0-0-1.border-1.sov.lon.uk.as29017.net (2a00:14f0:0:1::1a) 99.821 ms 27.305 ms 27.253 ms
9 xe-1-2-2.core-2.centro.hml.uk.as29017.net (2a00:14f0:0:1::a) 28.644 ms 28.671 ms 28.717 ms
10 ae3.core-1.centro.hml.uk.as29017.net (2a00:14f0:0:1::2e) 28.71 ms 28.633 ms 28.344 ms
11 gblon03.sixxs.net (2a00:14f0:1:2::5) 29.228 ms 28.851 ms 28.745 ms
12 gw-292.lon-03.gb.sixxs.net (2a00:14f0:e000:123::1) 28.583 ms 28.633 ms 28.758 ms
State change: remoteproblem
Jeroen Massar on Sunday, 21 June 2015 15:13:02
The state of this ticket has been changed to remoteproblem
Posting is only allowed when you are logged in. |