Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: Cannot access VPS through HE.net tunnel  (Read 3884 times)

amwdrizz

  • Newbie
  • *
  • Posts: 5
Cannot access VPS through HE.net tunnel
« on: December 28, 2012, 07:32:03 AM »

Hello folks,

This is my first post, and the problem is puzzling me a bit.

This problem, I got a new VPS with Front Range hosting.  It was assigned an IPv6 address which I assumed would work pretty much anywhere there is an IPv6 connection.  Apparently my tunnel goes through a different route and due to that never reaches the server.  If I use IPv4 it will connect fine, I just have longer times to connect due to IPv6 try and IPv4 fall back.  Now I have another VPS with another company (I am looking at switching over to Front Range hosting due to overall costs).  I can access that secondary VPS no problem with IPv6.

Data/Logs

From my HE.net Tunnel End Point
Code: [Select]
Tracing route to kara.amwdrizz.com [2604:2880::3f50:8ac2]
over a maximum of 30 hops:
1    <1 ms    <1 ms    <1 ms  2001:470:1f07:161f:4cf9:91ff:fece:1a9f
2    28 ms    29 ms    28 ms  2001:470:1f06:161f::1
3    25 ms    24 ms    26 ms  gige-g3-8.core1.nyc4.he.net [2001:470:0:5d::1]
4    42 ms    43 ms    47 ms  10gigabitethernet8-3.core1.chi1.he.net [2001:470:0:1c6::2]
5    65 ms    81 ms    65 ms  10gigabitethernet3-2.core1.den1.he.net [2001:470:0:1af::2]
6    75 ms    71 ms    77 ms  data102-llc.gigabitethernet2-9.core1.den1.he.net [2001:470:1:291::2]
7     *        *        *     Request timed out.
....
18     *     ^C

From my secondary VPS
Code: [Select]
traceroute to kara.amwdrizz.com (2604:2880::3f50:8ac2), 30 hops max, 80 byte packets
 1  2600:3c00:ffff:0:ca4c:75ff:fef5:c4ff (2600:3c00:ffff:0:ca4c:75ff:fef5:c4ff)  0.656 ms  0.648 ms  0.658 ms
 2  2607.f0d0.0002.0004.0000.0000.0001.0010-static.reverse.softlayer.com (2607:f0d0:2:4::1:10)  0.244 ms  0.208 ms  0.244 ms
 3  2607.f0d0.0002.0004.0000.0000.0001.000c-static.reverse.softlayer.com (2607:f0d0:2:4::1:c)  0.477 ms  0.497 ms 2607.f0d0.0002.0004.0000.0000.0001.0008-static.reverse.softlayer.com (2607:f0d0:2:4::1:8)  0.761 ms
 4  2607.f0d0.0002.0004.0000.0000.0001.0004-static.reverse.softlayer.com (2607:f0d0:2:4::1:4)  1.063 ms 2607.f0d0.0002.0004.0000.0000.0001.0002-static.reverse.softlayer.com (2607:f0d0:2:4::1:2)  0.666 ms 2607.f0d0.0002.0004.0000.0000.0001.0004-static.reverse.softlayer.com (2607:f0d0:2:4::1:4)  0.953 ms
 5  2607.f0d0.0002.0002.0000.0000.0000.006c-static.reverse.softlayer.com (2607:f0d0:2:2::6c)  0.558 ms 2607.f0d0.0002.0002.0000.0000.0000.006e-static.reverse.softlayer.com (2607:f0d0:2:2::6e)  0.842 ms 2607.f0d0.0002.0002.0000.0000.0000.006c-static.reverse.softlayer.com (2607:f0d0:2:2::6c)  0.820 ms
 6  10gigabitethernet3-1.core1.dal1.he.net (2001:504:0:5::6939:1)  4.557 ms  11.778 ms  3.602 ms
 7  10gigabitethernet1-3.core1.mci3.he.net (2001:470:0:23d::1)  28.120 ms  28.099 ms  27.293 ms
 8  10gigabitethernet5-1.core1.den1.he.net (2001:470:0:240::1)  35.484 ms  35.805 ms  35.015 ms
 9  data102-llc.gigabitethernet2-9.core1.den1.he.net (2001:470:1:291::2)  39.173 ms  39.153 ms  39.129 ms
10  2607:2800:102:8::1 (2607:2800:102:8::1)  39.898 ms  39.512 ms  39.807 ms
11  * * *
12  kara.amwdrizz.com (2604:2880::3f50:8ac2)  49.777 ms !X  49.765 ms !X  49.723 ms !X

Now, traceroute data from Free Range Hosting to my IPV6 endpoint
Code: [Select]
traceroute to 2001:470:1f07:161f:7c45:2c0e:4178:c856 (2001:470:1f07:161f:7c45:2c0e:4178:c856), 30 hops max, 80 byte packets
 1  * * *
 2  2604:2880::2 (2604:2880::2)  7.293 ms  6.928 ms  6.939 ms
 3  2607:2800:104:3::1 (2607:2800:104:3::1)  28.832 ms  28.783 ms  28.225 ms
 4  2607:2800:102::1 (2607:2800:102::1)  0.784 ms  0.621 ms  0.640 ms
 5  * * *
 ...
30  * * *

And From Free Range Hosting to my Secondary VPS
Code: [Select]
traceroute to kate.amwdrizz.com (2600:3c00::f03c:91ff:fe70:bab4), 30 hops max, 80 byte packets
 1  * * *
 2  2001:550:2:3c::2:1 (2001:550:2:3c::2:1)  0.599 ms  0.484 ms  0.597 ms
 3  te4-2.ccr01.den01.atlas.cogentco.com (::ffff:154.54.40.26)  86.954 ms  86.662 ms te3-2.ccr02.den01.atlas.cogentco.com (::ffff:154.54.40.18)  166.197 ms
 4  2001:550::1091 (2001:550::1091)  31.076 ms  30.946 ms  31.125 ms
 5  2001:550::25 (2001:550::25)  30.982 ms 2001:550::113 (2001:550::113)  30.770 ms 2001:550::25 (2001:550::25)  31.285 ms
 6  2001:550::1040 (2001:550::1040)  30.692 ms  30.534 ms  30.674 ms
 7  2001:550:4::32 (2001:550:4::32)  30.634 ms  30.812 ms  30.677 ms
 8  2001:550:3::28a (2001:550:3::28a)  30.546 ms  30.563 ms 2001:550:3::6 (2001:550:3::6)  30.860 ms
 9  ae-1.softlayer.snjsca04.us.bb.gin.ntt.net (2001:418:8400:5000::86)  30.893 ms  30.764 ms  30.554 ms
10  po3.bbr02.cs01.lax01.networklayer.com (2607:f0d0:2:2::17)  33.223 ms  32.918 ms  32.788 ms
11  po1.bbr01.cs01.lax01.networklayer.com (2607:f0d0:2:2::26)  33.061 ms  32.932 ms  32.819 ms
12  po5.bbr01.eq01.dal01.networklayer.com (2607:f0d0:2:2::c)  50.240 ms  47.300 ms  47.176 ms
13  2607.f0d0.0002.0002.0000.0000.0000.006d-static.reverse.softlayer.com (2607:f0d0:2:2::6d)  50.783 ms 2607.f0d0.0002.0002.0000.0000.0000.006f-static.reverse.softlayer.com (2607:f0d0:2:2::6f)  47.019 ms 2607.f0d0.0002.0002.0000.0000.0000.006d-static.reverse.softlayer.com (2607:f0d0:2:2::6d)  47.941 ms
14  2607.f0d0.0002.0004.0000.0000.0001.0005-static.reverse.softlayer.com (2607:f0d0:2:4::1:5)  47.512 ms 2607.f0d0.0002.0004.0000.0000.0001.0003-static.reverse.softlayer.com (2607:f0d0:2:4::1:3)  50.010 ms 2607.f0d0.0002.0004.0000.0000.0001.0005-static.reverse.softlayer.com (2607:f0d0:2:4::1:5)  50.813 ms
15  2607.f0d0.0002.0004.0000.0000.0001.000d-static.reverse.softlayer.com (2607:f0d0:2:4::1:d)  50.320 ms 2607.f0d0.0002.0004.0000.0000.0001.0009-static.reverse.softlayer.com (2607:f0d0:2:4::1:9)  46.764 ms 2607.f0d0.0002.0004.0000.0000.0001.000d-static.reverse.softlayer.com (2607:f0d0:2:4::1:d)  50.252 ms
16  2610:40:ff00:1:0:200:3:1 (2610:40:ff00:1:0:200:3:1)  51.940 ms  48.550 ms  50.621 ms
17  2600:3c00::f03c:91ff:fe70:bab4 (2600:3c00::f03c:91ff:fe70:bab4)  51.318 ms  51.308 ms  51.331 ms


So as you can see, IPv6 does work on my Free Range VPS.  But for some reason I -cannot- connect to it.  Any insight on methods to possibly resolve this problem?
Logged

cholzhauer

  • Hero Member
  • *****
  • Posts: 2715
Re: Cannot access VPS through HE.net tunnel
« Reply #1 on: December 28, 2012, 07:42:37 AM »

What tunnel server?  It doesn't work for me either

Code: [Select]
traceroute6 to kara.amwdrizz.com (2604:2880::3f50:8ac2) from 2001:470:1f10:2aa::2, 64 hops max, 12 byte packets
 1  servicespring-1.tunnel.tserv9.chi1.ipv6.he.net  22.488 ms  22.428 ms  20.927 ms
 2  gige-g3-4.core1.chi1.he.net  26.962 ms  24.082 ms  24.923 ms
 3  10gigabitethernet3-2.core1.den1.he.net  42.073 ms  41.453 ms  41.233 ms
 4  data102-llc.gigabitethernet2-9.core1.den1.he.net  43.929 ms  44.689 ms  43.849 ms
 5  * * *
Logged

kasperd

  • Founder, Netiter ApS
  • Hero Member
  • *****
  • Posts: 953
Re: Cannot access VPS through HE.net tunnel
« Reply #2 on: December 28, 2012, 08:26:42 AM »

I tested through Stockholm and Frankfurt tunnel servers. Neither can reach your IP.

Code: [Select]
1  2a01:d0:839a:babe:735d:77a7:990d:702c  7.325 ms  0.101 ms  0.117 ms
 2  2001:470:1f0a:1e45::1  43.380 ms  46.829 ms  51.005 ms
 3  2001:470:0:69::1  55.274 ms  39.263 ms  40.089 ms
 4  2001:470:0:21b::2  53.622 ms  53.693 ms  49.479 ms
 5  2001:470:0:21e::1  73.422 ms  69.236 ms  69.246 ms
 6  2001:470:0:128::1  127.501 ms  127.964 ms  127.187 ms
 7  2001:470:0:1c6::2  148.268 ms  135.400 ms  135.993 ms
 8  2001:470:0:1af::2  161.606 ms  165.525 ms  166.359 ms
 9  2001:470:1:291::2  166.415 ms  164.102 ms  164.488 ms
10  *  *  *
11  *  *  *
Code: [Select]
traceroute to 2604:2880::3f50:8ac2 (2604:2880::3f50:8ac2), 30 hops max, 80 byte packets
 1  2001:470:28:940:5d75:c1f4:e0a0:f8ec  0.572 ms  4.390 ms  4.630 ms
 2  2001:470:27:940::1  51.822 ms  79.856 ms  83.142 ms
 3  2001:470:0:11e::1  85.985 ms  41.175 ms  46.511 ms
 4  2001:470:0:22f::1  55.271 ms  55.805 ms  58.842 ms
 5  2001:470:0:3f::1  70.113 ms  72.498 ms  72.977 ms
 6  2001:470:0:128::1  138.863 ms  139.374 ms  134.513 ms
 7  2001:470:0:1c6::2  219.592 ms  181.122 ms  181.551 ms
 8  2001:470:0:1af::2  210.968 ms  209.755 ms  203.834 ms
 9  2001:470:1:291::2  206.981 ms  196.206 ms  196.635 ms
10  *  *  *
11  *  *  *
12  *  *  *

I tried through another tunnel broker. No connectivity either.
Code: [Select]
traceroute to 2604:2880::3f50:8ac2 (2604:2880::3f50:8ac2), 30 hops max, 80 byte packets
 1  2a01:d0:839a:babe:735d:77a7:990d:702c  0.202 ms  4.857 ms  4.823 ms
 2  2a01:d0:ffff:39a::1  77.024 ms  77.017 ms  76.995 ms
 3  2a01:d0:0:1c::fa  76.972 ms  76.948 ms  76.922 ms
 4  2a02:2d8:0:2801:232a::  76.898 ms  76.883 ms  76.836 ms
 5  2a02:2d8::57f5:e0a1  126.118 ms  162.017 ms  162.009 ms
 6  2001:978:2:7::17:1  102.022 ms 2001:978:2:7::f:1  101.874 ms 2001:978:2:7::17:1  97.353 ms
 7  2001:978:4::16  233.211 ms  231.211 ms  231.766 ms
 8  2001:978::123  234.769 ms  235.526 ms  235.459 ms
 9  2001:550:2:23::1a  238.227 ms  238.909 ms  238.840 ms
10  2001:550::218  236.374 ms  243.915 ms  243.814 ms
11  2001:550::204  243.852 ms  235.185 ms  336.418 ms
12  2001:550::24  338.304 ms  271.891 ms  230.544 ms
13  * * *
14  2001:550:2:3c::2:1  347.320 ms  346.470 ms  343.537 ms
15  * * *
16  2604:2880::3f50:8ac2  323.750 ms !X  323.755 ms !X  308.538 ms !X

I also tried using native IPv6 from a VPS at Hetzner. From there I can reach your IP. Interestingly the path goes through HE, the hops between HE and your IP are not responding.

Code: [Select]
4  2a01:4f8:d16:2::1  5.967 ms  6.001 ms  5.888 ms
 5  2a01:4f8:0:d1:2:0:10:1  1.431 ms  0.743 ms  0.767 ms
 6  2a01:4f8:0:1::1:1  5.508 ms  5.541 ms  5.546 ms
 7  2001:7f8::1b1b:0:1  7.504 ms  7.202 ms  7.232 ms
 8  2001:470:0:21b::2  21.650 ms  21.685 ms  21.689 ms
 9  2001:470:0:21e::1  27.087 ms  25.363 ms  25.388 ms
10  2001:470:0:128::1  89.410 ms  89.449 ms  89.455 ms
11  2001:470:0:1c6::2  107.611 ms  107.105 ms  107.136 ms
12  2001:470:0:1af::2  130.439 ms  130.471 ms  130.471 ms
13  2001:470:1:291::2  133.289 ms  133.170 ms  133.201 ms
14  *  *  *
15  *  *  *
16  2604:2880::3f50:8ac2  136.860 ms  136.884 ms  136.879 ms

I also tested using 6to4 from three different networks. From two of them I can reach your IP from one of them I could not.

It does look like there are problems both with packets to your IP and packets from your IP.

Since packets from Hetzner and from a HE tunnel both go through the HE network, and appear to leave the HE network through 2001:470:1:291::2 in both cases, the difference causing one to work and one to fail is most likely due to the return path failing.

From one of the tunnel brokers where it fails as well as from the network where 6to4 connectivity to your IP fails I see roughly the same path for the last 9 hops.

Code: [Select]
8  2001:978::123  234.769 ms  235.526 ms  235.459 ms
 9  2001:550:2:23::1a  238.227 ms  238.909 ms  238.840 ms
10  2001:550::218  236.374 ms  243.915 ms  243.814 ms
11  2001:550::204  243.852 ms  235.185 ms  336.418 ms
12  2001:550::24  338.304 ms  271.891 ms  230.544 ms
13  * * *
14  2001:550:2:3c::2:1  347.320 ms  346.470 ms  343.537 ms
15  * * *
16  2604:2880::3f50:8ac2  323.750 ms !X  323.755 ms !X  308.538 ms !X
Code: [Select]
9  2001:978::123  171.567 ms 2001:978::124  166.428 ms  165.730 ms
10  2001:550:2:23::1a  168.934 ms 2001:550::207  168.853 ms 2001:550:2:23::1a  169.022 ms
11  2001:550::218  170.308 ms 2001:550::207  170.441 ms 2001:550::156  169.948 ms
12  2001:550::202  163.496 ms 2001:550::201  171.052 ms 2001:550::202  169.705 ms
13  2001:550::202  175.109 ms 2001:550::24  175.038 ms 2001:550::16  174.669 ms
14  ::ffff:154.54.24.81  258.844 ms ::ffff:154.54.87.89  237.284 ms ::ffff:154.54.82.201  232.865 ms
15  2001:550:2:3c::2:1  256.146 ms  255.972 ms  235.370 ms
16  * * *
17  2604:2880::3f50:8ac2  175.427 ms !X  171.874 ms !X  171.478 ms !X

Since I actually get an ICMP error back, the problem isn't the return path. And actually it looks like it is your own host rejecting the packets in those cases.
Logged

kasperd

  • Founder, Netiter ApS
  • Hero Member
  • *****
  • Posts: 953
Re: Cannot access VPS through HE.net tunnel
« Reply #3 on: December 28, 2012, 08:57:31 AM »

On a second look I realize that the difference in responses from your IP are due to different traceroute versions using different types of packets by default. It works with ICMP but gets errors with UDP. That's why it looked different, and not due to me running the traceroute from different sources.

That means the only cases where I observed lack of connectivity was when using an HE tunnel. And symptoms suggest the problem is in the direction from your VPS to HE. Thus the most usable piece of information you provided so far is
Now, traceroute data from Free Range Hosting to my IPV6 endpoint
Code: [Select]
traceroute to 2001:470:1f07:161f:7c45:2c0e:4178:c856 (2001:470:1f07:161f:7c45:2c0e:4178:c856), 30 hops max, 80 byte packets
 1  * * *
 2  2604:2880::2 (2604:2880::2)  7.293 ms  6.928 ms  6.939 ms
 3  2607:2800:104:3::1 (2607:2800:104:3::1)  28.832 ms  28.783 ms  28.225 ms
 4  2607:2800:102::1 (2607:2800:102::1)  0.784 ms  0.621 ms  0.640 ms
 5  * * *
 ...
30  * * *
A traceroute from my VPS to each of those IP addresses look like this
Code: [Select]
traceroute to 2604:2880::2 (2604:2880::2), 30 hops max, 80 byte packets
...
 4  2a01:4f8:d16:2::1  3.062 ms  3.064 ms  2.834 ms
 5  2a01:4f8:0:d1:4:0:10:2  0.896 ms  0.562 ms  0.562 ms
 6  2a01:4f8:0:1::1:1  5.155 ms  5.156 ms  5.157 ms
 7  2001:7f8::1b1b:0:1  7.055 ms  6.859 ms  6.873 ms
 8  2001:470:0:21b::2  19.889 ms  19.907 ms  19.919 ms
 9  2001:470:0:21e::1  20.987 ms  21.149 ms  21.159 ms
10  2001:470:0:128::1  88.309 ms  88.326 ms  88.337 ms
11  2001:470:0:1c6::2  106.563 ms  106.055 ms  106.090 ms
12  2001:470:0:1af::2  130.201 ms  130.236 ms  130.255 ms
13  2001:470:1:291::2  132.806 ms  132.891 ms  132.924 ms
14  *  *  *
...
30  *  *  *
Code: [Select]
traceroute to 2607:2800:104:3::1 (2607:2800:104:3::1), 30 hops max, 80 byte packets
...
 4  2a01:4f8:d16:2::1  5.863 ms  5.866 ms  5.554 ms
 5  2a01:4f8:0:d1:3:0:10:2  1.182 ms  0.614 ms  0.617 ms
 6  2a01:4f8:0:2::1:4  6.415 ms  6.419 ms  6.420 ms
 7  2001:7f8::1b1b:0:1  7.324 ms  15.887 ms  15.887 ms
 8  2001:470:0:21b::2  21.222 ms  21.231 ms  21.234 ms
 9  2001:470:0:21e::1  25.438 ms  22.851 ms  22.876 ms
10  2001:470:0:128::1  100.578 ms  100.617 ms  100.647 ms
11  2001:470:0:1c6::2  108.101 ms  107.771 ms  118.969 ms
12  2001:470:0:1af::2  131.032 ms  131.062 ms  131.087 ms
13  2001:470:1:291::2  134.825 ms  135.081 ms  135.110 ms
14  *  *  *
...
30  *  *  *
Code: [Select]
traceroute to 2607:2800:102::1 (2607:2800:102::1), 30 hops max, 80 byte packets
...
 4  2a01:4f8:d16:2::1  3.234 ms  3.237 ms  6.567 ms
 5  2a01:4f8:0:d1:3:0:10:2  20.524 ms  17.866 ms  17.890 ms
 6  2a01:4f8:0:2::1:4  6.606 ms  6.687 ms  6.507 ms
 7  2001:7f8::1b1b:0:1  16.213 ms  13.498 ms  13.523 ms
 8  2001:470:0:21b::2  31.887 ms  31.920 ms  28.370 ms
 9  2001:470:0:21e::1  22.210 ms  26.497 ms  26.528 ms
10  2001:470:0:128::1  89.529 ms  89.568 ms  89.577 ms
11  2001:470:0:1c6::2  108.232 ms  108.241 ms  108.271 ms
12  2001:470:0:1af::2  137.515 ms  137.551 ms  137.556 ms
13  2001:470:1:291::2  134.891 ms  135.050 ms  135.611 ms
14  *  *  *
...
30  *  *  *
What we learn from this is that none of those three routers can communicate with my VPS, and they cannot send packets to HE. Possibly they cannot send packets anywhere except form back to the Free Range Hosting network. Whether they can receive packets from outside is unclear. If they could receive packets from outside but not send packets outside, that could explain the missing hops just before your IP in those traceroutes, that do work.

As you already observed the packets from your VPS take different routes very early on depending on which destination they are heading for. Try traceroute from your VPS to a few more destinations to see which route they take early on, and if there is any correlation. Maybe there are other destinations, which also use those routers, and are unreachable.

Traceroutes from my VPS and from an HE tunnel to the routers on the good path away from your VPS reveals that those just like your VPS can receive packets through the HE network, but they cannot send replies back to the HE network. Probably they too take the bad route out.
Code: [Select]
traceroute to 2001:550:2:3c::2:1 (2001:550:2:3c::2:1), 30 hops max, 80 byte packets
...
 4  2a01:4f8:d16:2::1  5.615 ms  5.647 ms  5.999 ms
 5  2a01:4f8:0:d1:2:0:10:1  1.836 ms  0.816 ms  0.846 ms
 6  2a01:4f8:0:2::b:4  3.867 ms  3.893 ms  3.892 ms
 7  2001:1620:1000::1a9  14.684 ms  12.896 ms  12.923 ms
 8  2001:1620:2::f2  14.108 ms  14.144 ms  13.283 ms
 9  2001:1620:2::101  6.793 ms  6.873 ms  6.904 ms
10  2001:1620:2::e1  9.455 ms  9.502 ms  9.508 ms
11  2001:1620:2::5  13.938 ms  25.824 ms  25.854 ms
12  2001:668:0:3::5000:11  14.086 ms  14.097 ms  14.363 ms
13  2001:668:0:2::1:1d21  18.129 ms  17.773 ms  17.804 ms
14  2001:978:3::4d  63.273 ms  63.312 ms  2001:978:3::49  63.317 ms
15  2001:978::135  153.351 ms  152.785 ms  152.793 ms
16  2001:978::19  161.662 ms  161.685 ms  161.678 ms
17  2001:978::158  155.018 ms  154.671 ms  154.702 ms
18  2001:550::47  162.256 ms  162.298 ms  162.292 ms
19  2001:550::204  154.999 ms  154.639 ms  154.644 ms
20  2001:550::190  152.773 ms  152.799 ms  152.807 ms
21  *  *  *
22  2001:550:2:3c::2:1  248.704 ms  248.742 ms  246.513 ms
Code: [Select]
traceroute to 2001:550::1091 (2001:550::1091), 30 hops max, 80 byte packets
...
 4  2a01:4f8:d16:2::1  3.871 ms  3.895 ms  3.402 ms
 5  2a01:4f8:0:d1:1:0:10:1  1.700 ms  0.771 ms  0.773 ms
 6  2a01:4f8:0:2::b:4  3.355 ms  3.362 ms  3.681 ms
 7  2001:1620:1000::1a9  3.692 ms  3.192 ms  3.200 ms
 8  2001:1620:2::f2  3.486 ms  3.499 ms  3.501 ms
 9  2001:1620:2::101  7.342 ms  6.289 ms  6.301 ms
10  2001:1620:2::e1  11.070 ms  11.108 ms  10.819 ms
11  2001:1620:2::5  13.216 ms  13.243 ms  13.278 ms
12  2001:668:0:3::5000:11  13.873 ms  13.908 ms  13.931 ms
13  2001:668:0:2::1:13d2  17.655 ms  17.409 ms  17.447 ms
14  2001:978:3::49  27.461 ms  27.501 ms  27.525 ms
15  2001:978::135  170.492 ms  169.813 ms  169.833 ms
16  2001:978::6  164.007 ms  164.041 ms  164.064 ms
17  2001:978::160  163.945 ms  163.620 ms  163.640 ms
18  2001:550::47  164.360 ms  164.383 ms  164.378 ms
19  2001:550::204  170.590 ms  170.460 ms  170.463 ms
20  2001:550::190  170.769 ms  170.777 ms  170.756 ms
21  *  *  *
22  2001:550::1091  168.481 ms  168.488 ms  168.468 ms
Code: [Select]
traceroute to 2001:550:2:3c::2:1 (2001:550:2:3c::2:1), 30 hops max, 80 byte packets
 1  2a01:d0:839a:babe:735d:77a7:990d:702c  0.217 ms  0.175 ms  0.211 ms
 2  2001:470:1f0a:1e45::1  44.411 ms  48.144 ms  51.936 ms
 3  2001:470:0:69::1  52.767 ms  42.986 ms  43.009 ms
 4  2001:470:0:21b::2  61.888 ms  62.417 ms  58.673 ms
 5  2001:470:0:21e::1  66.268 ms  65.887 ms  65.965 ms
 6  2001:470:0:128::1  133.652 ms  134.207 ms  134.205 ms
 7  2001:470:0:1c6::2  148.440 ms  136.789 ms  137.136 ms
 8  2001:470:0:270::2  151.841 ms  152.239 ms  152.246 ms
 9  2001:470:0:240::1  164.437 ms  163.488 ms  162.645 ms
10  2001:470:0:1b4::1  205.058 ms  205.096 ms  205.082 ms
11  2001:470:0:32::2  192.547 ms  198.429 ms  198.488 ms
12  *  *  *
...
30  *  *  *
Code: [Select]
traceroute to 2001:550::1091 (2001:550::1091), 30 hops max, 80 byte packets
 1  2a01:d0:839a:babe:735d:77a7:990d:702c  12.371 ms  8.682 ms  8.709 ms
 2  2001:470:1f0a:1e45::1  45.101 ms  48.580 ms  51.834 ms
 3  2001:470:0:69::1  61.304 ms  39.877 ms  40.721 ms
 4  2001:470:0:21b::2  51.649 ms  51.723 ms  48.502 ms
 5  2001:470:0:1b1::1  140.068 ms  130.677 ms  130.688 ms
 6  2001:470:0:286::1  135.755 ms  136.397 ms  154.149 ms
 7  2001:470:0:270::2  172.996 ms  158.681 ms  158.689 ms
 8  2001:470:0:240::1  163.055 ms  162.232 ms  163.043 ms
 9  2001:470:0:1b4::1  191.531 ms  190.310 ms  191.168 ms
10  2001:470:0:32::2  193.203 ms  194.563 ms  194.596 ms
11  *  *  *
...
30  *  *  *

I think you need to contact the VPS provider to get the problem resolved, because as far as I can see all symptoms points to a problem in their network.
Logged

amwdrizz

  • Newbie
  • *
  • Posts: 5
Re: Cannot access VPS through HE.net tunnel
« Reply #4 on: December 28, 2012, 09:04:26 AM »

What tunnel server?  It doesn't work for me either

Tunnel Server IPv4: 209.51.161.14  & IPv6: 2001:470:1f06:161f::1

I tested through Stockholm and Frankfurt tunnel servers. Neither can reach your IP.

~snip~

I tried through another tunnel broker. No connectivity either.

~snip~

I also tried using native IPv6 from a VPS at Hetzner. From there I can reach your IP. Interestingly the path goes through HE, the hops between HE and your IP are not responding.

~snip~

I also tested using 6to4 from three different networks. From two of them I can reach your IP from one of them I could not.

It does look like there are problems both with packets to your IP and packets from your IP.

Since packets from Hetzner and from a HE tunnel both go through the HE network, and appear to leave the HE network through 2001:470:1:291::2 in both cases, the difference causing one to work and one to fail is most likely due to the return path failing.

From one of the tunnel brokers where it fails as well as from the network where 6to4 connectivity to your IP fails I see roughly the same path for the last 9 hops.

~snip~

Since I actually get an ICMP error back, the problem isn't the return path. And actually it looks like it is your own host rejecting the packets in those cases.

That is actually interesting, I'll forward this in my ticket with them.  As of now they escalated the ticket on their end to a Senior engineer for investigation.  Since I am now thinking it is more of a network issue somewhere.  I am still unsure if it is actually them or another network in between.


~Recent update by kasperd

As the text above indicates, they are now investigating the issue on their end.  I'll run some more trace routes here to a few other sources and see what the end result is or if there is any correlation in the data.  I am also going to link them to this thread to see the data that you have provided so far.


All ~snips~ are code blocks removed from the quote
Logged

amwdrizz

  • Newbie
  • *
  • Posts: 5
Re: Cannot access VPS through HE.net tunnel
« Reply #5 on: January 01, 2013, 06:50:34 PM »

Thought I should update any one interested in the out come of this.

Apparently the DC that Front Range Hosting uses was the culprit.  I can only guess either A) A bad link, or B) Mis-Configuration somewhere. 

The SA that handled my ticket received a response this morning stating it was fixed, and passed it on to me.  So now, I can in fact ping my server (kara.amwdrizz.com)

Thanks to all that assisted with their own reports on the matter.  And feel free to double check to make sure that you can in-fact reach that host via IPv6.

Logged