Debugging tunnel and/or problems with tserv1.nyc4.he.net

[dfc]

I am having trouble with my tunnel. I can not ping or traceroute to tserv1.nyc4.he.net

Code Select Expand


traceroute tserv1.nyc4.he.net
traceroute to tserv1.nyc4.he.net (209.51.161.14), 30 hops max, 60 byte packets
1  fw.llamahaus (192.168.10.1)  0.122 ms  0.089 ms  0.105 ms
2  10.236.192.1 (10.236.192.1)  11.190 ms  11.175 ms  11.144 ms
3  gig6-1-6.syrcnysl-rtr002.cny.northeast.rr.com (24.24.16.188)  19.832 ms  20.204 ms  20.370 ms
4  rdc-24-58-149-176.cny.east.twcable.com (24.58.149.176)  15.986 ms  15.959 ms  16.498 ms
5  rdc-24-58-149-252.cny.east.twcable.com (24.58.149.252)  38.217 ms  37.400 ms  39.332 ms
6  ae-3-0.cr0.chi10.tbone.rr.com (66.109.6.72)  33.047 ms  32.503 ms  33.781 ms
7  ae1.pr1.chi10.tbone.rr.com (107.14.17.194)  32.419 ms ae4.pr1.chi10.tbone.rr.com (66.109.1.66)  29.105 ms ae1.pr1.chi10.tbone.rr.com (107.14.17.194)  28.978 ms
8  chi-bb1-link.telia.net (213.248.76.97)  29.043 ms chi-bb1-link.telia.net (213.248.66.193)  31.697 ms  31.745 ms
9  chi-bb1-link.telia.net (80.91.246.168)  31.823 ms  31.739 ms chi-bb1-link.telia.net (213.155.136.34)  31.662 ms
10  nyk-bb1-link.telia.net (80.91.246.167)  39.762 ms nyk-bb1-link.telia.net (80.91.246.163)  38.738 ms nyk-bb1-link.telia.net (80.91.246.167)  39.710 ms
11  nyk-b6-link.telia.net (80.91.253.93)  38.799 ms nyk-b6-link.telia.net (80.91.253.95)  39.708 ms nyk-b6-link.telia.net (213.155.130.251)  47.866 ms
12  * * *
13  * * *
14  * * *
15  * * *
16  * * *
17  * * *
18  * * *
19  * * *
20  * * *
21  * * *
22  * * *
23  * * *
24  * * *
25  * * *
26  * * *
27  * * *
28  * * *
29  * * *
30  * * *


I have never tried in the past but I have to imagine this is normally possible. If things were working correctly I should be able to ping/traceroute to tserv1 right?

I just remembered clock.nyc.he.net clock.nyc.he.netis one of the more reliable backup ntp servers that I use and  seems to be on the same subnet as tserv. I am assuming that something must be awry if I cannot get the time from clock.nyc.he.net:

Code Select Expand



#sntp -d clock.nyc.he.net
sntp sendpkt: Sending packet to 209.51.161.238... Packet sent.
sntp recvdata: select() reached timeout (15 sec), aborting.
sntp recvpkt failed: -1.
Server unusable
on_wire failed for server 209.51.161.238!



Is anyone else experiencing problems?

[kasperd]

It works for me from three different networks. One of them even appears to be using the same path into the HE network as you.

Code Select Expand

traceroute to 209.51.161.14 (209.51.161.14), 30 hops max, 60 byte packets
5  kbn-b1-geth2-3.telia.net (213.248.66.145)  14.403 ms  14.685 ms  14.611 ms
6  kbn-bb2-link.telia.net (80.91.254.222)  14.588 ms kbn-bb1-link.telia.net (213.155.130.96)  72.018 ms  72.236 ms
7  nyk-bb2-link.telia.net (80.91.247.119)  102.701 ms nyk-bb2-link.telia.net (80.91.247.121)  111.021 ms nyk-bb1-link.telia.net (213.155.131.135)  153.688 ms
8  nyk-b6-link.telia.net (80.91.253.95)  109.846 ms  110.130 ms nyk-b6-link.telia.net (213.155.130.251)  111.126 ms
9  hurricane-ic-138361-nyk-b6.c.telia.net (213.248.67.126)  123.473 ms  122.980 ms  105.326 ms
10  tserv1.nyc4.he.net (209.51.161.14)  102.750 ms  102.036 ms  102.446 ms

Based on this I have a suspicion the problem is not with the route from you to the tunnel server, but rather with the route from the tunnel server back to you. In that case you may see that responses do come back from every hop along the way, until you reach the HE network. Though all the routers inside the HE network do send time exceeded messages back to you, they never make it back to you.

Now since you are able to post to the forum, you must obviously be able to communicate with HE somehow. So not all of the HE network is incapable of sending packets back to you.

For further debugging I suggest you try pinging different tunnel servers, to see which parts of the HE network can send packets to you, and which parts cannot. Also try to ping 209.51.161.14 again, it might be the difference between your observations and mine, just means it came back online in the meantime.

Also check, which protocol you are connecting to the forum with. Is it IPv4, IPv6 tunnel, or native IPv6?