SixXS::Sunset 2017-06-06

2a00:1450:4013:c00::8a not reachable (deham01)
[de] Carmen Sandiego on Friday, 27 March 2015 00:13:20
hi, can anyone confirm that "2a00:1450:4013:c00::8a" aka google isnt reachable over tunnel useing deham01? i temp fixed it by using the sixxs dnscache. it seems any connection to google over deham01 want to go over the irish google which isnt working. thanks.
2a00:1450:4013:c00::8a not reachable (deham01)
[ch] Jeroen Massar SixXS Staff on Friday, 27 March 2015 09:48:20
can anyone confirm that "2a00:1450:4013:c00::8a" aka google isnt reachable over tunnel useing deham01?
Traceroutes end in the Google network. Hence, little we can do about that.
i temp fixed it by using the sixxs dnscache.
If that 'fixed' it, then you are likely getting a completely different address. Which one is that and what does the traceroute look like?
2a00:1450:4013:c00::8a not reachable (deham01)
[de] Shadow Hawkins on Friday, 27 March 2015 20:03:51
hi same problem here. Google not reachable with pop deham01 thanks
2a00:1450:4013:c00::8a not reachable (deham01)
[de] Shadow Hawkins on Saturday, 28 March 2015 23:38:29
I have same issue with connecting to www.google.com and www.google.de via sixxs (deham02) : $ dig AAAA www.google.com +short 2a00:1450:4013:c01::6a NOTE: At home my router uses Deutsches Telekom (DTAG AS3320) DNS server. $ mtr -wrc10 2a00:1450:4013:c01::6a Start: Sun Mar 29 00:26:47 2015 HOST: shadow Loss% Snt Last Avg Best Wrst StDev 1.|-- fritz.box 0.0% 10 0.5 0.6 0.5 1.2 0.0 2.|-- gw-638.ham-02.de.sixxs.net 0.0% 10 29.8 29.9 29.5 30.2 0.0 3.|-- 2001:6f8:891:1::c2e9:c721 0.0% 10 29.8 29.8 29.6 30.2 0.0 4.|-- 2001:6f8:891:1::c2e9:c725 0.0% 10 30.7 30.6 30.4 30.9 0.0 5.|-- de-cix20.net.google.com 0.0% 10 40.9 40.6 39.9 41.3 0.0 6.|-- 2001:4860::1:0:70c3 0.0% 10 40.1 40.4 40.0 41.3 0.0 7.|-- 2001:4860::8:0:5038 0.0% 10 40.3 40.3 39.9 41.3 0.0 8.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 Now after reading this thread I tried resolving www.google.com through google DNS servers and got: $ dig @8.8.8.8 AAAA www.google.com +short 2a00:1450:4016:802::1014 $ mtr -wrc10 2a00:1450:4016:802::1014 Start: Sun Mar 29 00:25:51 2015 HOST: shadow Loss% Snt Last Avg Best Wrst StDev 1.|-- fritz.box 0.0% 10 0.7 0.6 0.5 1.0 0.0 2.|-- gw-638.ham-02.de.sixxs.net 0.0% 10 30.3 30.0 29.6 30.4 0.0 3.|-- 2001:6f8:891:1::c2e9:c721 0.0% 10 30.0 30.1 29.7 30.7 0.0 4.|-- 2001:6f8:891:1::c2e9:c725 0.0% 10 30.2 30.5 30.0 30.8 0.0 5.|-- de-cix20.net.google.com 0.0% 10 40.2 40.2 39.8 40.6 0.0 6.|-- 2001:4860::1:0:4ca2 0.0% 10 40.4 44.1 39.8 68.7 8.9 7.|-- 2001:4860::8:0:5038 0.0% 10 40.0 40.2 39.6 42.0 0.6 8.|-- 2001:4860::8:0:8bd6 0.0% 10 45.2 47.0 45.2 49.9 1.7 9.|-- 2001:4860::1:0:336c 0.0% 10 46.1 46.8 45.4 50.2 1.5 10.|-- 2001:4860:0:1::179 0.0% 10 45.8 45.9 45.6 46.1 0.0 11.|-- muc03s07-in-x14.1e100.net 0.0% 10 45.7 45.3 44.8 45.7 0.0 Apparently only some Google IPv6 addresses are not reachable via Sixxs. I also tested this unreachable IPv6 address from a server with native IPv6 connectivity and could reach it: mtr -wrc10 2a00:1450:4013:c01::6a HOST: vms1 Loss% Snt Last Avg Best Wrst StDev 1.|-- xxxxx 0.0% 10 0.8 1.6 0.7 3.8 1.2 2.|-- xxxxx.hetzner.de 0.0% 10 0.4 2.7 0.2 19.5 6.0 3.|-- core21.hetzner.de 0.0% 10 0.3 0.3 0.2 0.6 0.1 4.|-- core1.hetzner.de 0.0% 10 4.9 4.9 4.9 5.1 0.1 5.|-- juniper1.ffm.hetzner.de 0.0% 10 5.0 5.0 4.9 5.1 0.1 6.|-- de-cix20.net.google.com 0.0% 10 5.2 5.3 5.2 5.5 0.1 7.|-- 2001:4860::1:0:70c3 0.0% 10 5.8 6.1 5.8 6.5 0.3 8.|-- 2001:4860::8:0:5038 0.0% 10 6.1 6.7 5.8 14.0 2.5 9.|-- 2001:4860::8:0:519f 0.0% 10 12.4 12.5 12.2 13.0 0.3 10.|-- 2001:4860::8:0:519e 0.0% 10 15.6 15.9 15.1 19.3 1.2 11.|-- 2001:4860::2:0:8651 0.0% 10 16.0 16.0 15.4 17.0 0.5 12.|-- ??? 100.0 10 0.0 0.0 0.0 0.0 0.0 13.|-- ea-in-x6a.1e100.net 0.0% 10 15.6 15.8 15.4 17.5 0.7 As expected: 2001:4860::8:0:519f is pingable from native IPv6 of server but not pingable from home via sixxs tunnel. - Alexander
2a00:1450:4013:c00::8a not reachable (deham01)
[ch] Jeroen Massar SixXS Staff on Sunday, 29 March 2015 08:29:55
All things point to Google not being able to reach deham0X... The reverse route also has to work. And as can be seen the traceroutes die inside Google.

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

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