Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: General IPv4 routing issues to your tunnel servers this morning?  (Read 639 times)

AndrewButterworth

  • Newbie
  • *
  • Posts: 37
General IPv4 routing issues to your tunnel servers this morning?
« on: February 20, 2021, 01:29:05 AM »

Just noticed my tunnel is not up to the Paris server.
If I try and ping the server I either get time outs or expired in transit:
Code: [Select]
Z:\>ping 216.66.84.42

Pinging 216.66.84.42 with 32 bytes of data:
Request timed out.
Request timed out.
Reply from 62.115.135.225: TTL expired in transit.
Reply from 62.115.135.225: TTL expired in transit.

Ping statistics for 216.66.84.42:
    Packets: Sent = 4, Received = 2, Lost = 2 (50% loss),

I have tried pinging some of the other European servers and I get the same results:
Code: [Select]
Z:\>ping -4 tserv1.lon1.he.net

Pinging tserv1.lon1.he.net [216.66.80.26] with 32 bytes of data:
Reply from 62.115.116.169: TTL expired in transit.
Reply from 62.115.116.169: TTL expired in transit.
Reply from 62.115.116.169: TTL expired in transit.
Reply from 62.115.116.169: TTL expired in transit.

Ping statistics for 216.66.80.26:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

Z:\>ping -4 tserv1.ams.he.net
Ping request could not find host tserv1.ams.he.net. Please check the name and try again.

Z:\>ping -4 tserv1.ams1.he.net

Pinging tserv1.ams1.he.net [216.66.84.46] with 32 bytes of data:
Reply from 62.115.116.169: TTL expired in transit.
Reply from 62.115.116.169: TTL expired in transit.
Reply from 62.115.116.169: TTL expired in transit.
Reply from 62.115.116.169: TTL expired in transit.

Ping statistics for 216.66.84.46:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),

So I think its a more fundamental IPv4 routing issue?

I can reach the IPv4 address of he.net and forums.he.net though?
Code: [Select]
Z:\>ping -4 he.net

Pinging he.net [216.218.236.2] with 32 bytes of data:
Reply from 216.218.236.2: bytes=32 time=141ms TTL=57
Reply from 216.218.236.2: bytes=32 time=140ms TTL=57
Reply from 216.218.236.2: bytes=32 time=140ms TTL=57
Reply from 216.218.236.2: bytes=32 time=141ms TTL=57

Ping statistics for 216.218.236.2:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 140ms, Maximum = 141ms, Average = 140ms

Z:\>ping -4 forums.he.net

Pinging forums.he.net [64.62.222.3] with 32 bytes of data:
Reply from 64.62.222.3: bytes=32 time=139ms TTL=57
Reply from 64.62.222.3: bytes=32 time=139ms TTL=57
Reply from 64.62.222.3: bytes=32 time=140ms TTL=57
Reply from 64.62.222.3: bytes=32 time=139ms TTL=57

Ping statistics for 64.62.222.3:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 139ms, Maximum = 140ms, Average = 139ms

Looks like there is a routing loop in Telia ?
Code: [Select]
Z:\>tracert -d 216.66.84.42

Tracing route to 216.66.84.42 over a maximum of 30 hops

  1     2 ms     2 ms    <1 ms  192.168.80.30
  2     1 ms    <1 ms    <1 ms  192.168.120.14
  3     *        *        *     Request timed out.
  4     6 ms     6 ms     6 ms  149.6.9.57
  5     6 ms     6 ms     8 ms  130.117.48.145
  6     8 ms     7 ms     8 ms  154.54.60.13
  7     8 ms     8 ms     7 ms  154.54.57.162
  8     7 ms     7 ms     7 ms  62.115.185.38
  9    15 ms    15 ms    15 ms  62.115.120.74
 10    16 ms    15 ms    15 ms  62.115.113.210
 11    16 ms    16 ms    20 ms  62.115.136.195
 12    34 ms    35 ms    36 ms  62.115.136.194
 13     *        *        *     Request timed out.
 14    36 ms    35 ms    35 ms  62.115.135.225
 15    38 ms    38 ms    38 ms  62.115.116.168
 16    39 ms    39 ms    39 ms  213.155.136.167
 17    38 ms    39 ms    38 ms  62.115.137.65
 18    58 ms    58 ms    58 ms  62.115.136.194
 19     *       58 ms     *     62.115.134.97
 20    58 ms     *        *     62.115.135.225
 21    62 ms    61 ms    62 ms  62.115.116.168
 22    61 ms    62 ms    62 ms  213.155.136.167
 23    61 ms    61 ms    62 ms  62.115.137.65
 24    81 ms    81 ms    80 ms  62.115.136.194
 25    80 ms    81 ms   105 ms  62.115.134.97
 26    81 ms    81 ms    94 ms  62.115.135.225
 27    84 ms    84 ms    84 ms  62.115.116.168
 28    85 ms    84 ms    85 ms  213.155.136.167
 29    84 ms    85 ms    85 ms  62.115.137.65
 30   103 ms   103 ms   104 ms  62.115.136.194

Trace complete.

According to the MRTG graph for my tunnel interface it looks like this started at midnight UTC - I can't upload a screenshot of the graph for some reason (failed security?)

Hopefully this won't last for long?

Andy
« Last Edit: February 20, 2021, 02:21:47 AM by AndrewButterworth »
Logged

AndrewButterworth

  • Newbie
  • *
  • Posts: 37
Re: General IPv4 routing issues to your tunnel servers this morning?
« Reply #1 on: February 20, 2021, 09:21:53 AM »

Looks like it got fixed around 15:50 UTC today.
The MRTG graph for my tunnel starts showing traffic around then.
Code: [Select]
Z:\>tracert -d 216.66.84.42

Tracing route to 216.66.84.42 over a maximum of 30 hops

  1     6 ms    <1 ms    <1 ms  192.168.80.30
  2     1 ms    <1 ms    <1 ms  192.168.120.14
  3     *        *        *     Request timed out.
  4     6 ms    15 ms     6 ms  149.6.9.57
  5     6 ms     6 ms     7 ms  130.117.48.145
  6     8 ms    10 ms     8 ms  154.54.60.13
  7     9 ms     7 ms    10 ms  154.54.57.162
  8     8 ms     8 ms     8 ms  62.115.185.38
  9    15 ms    15 ms    16 ms  62.115.120.74
 10    16 ms    15 ms    15 ms  62.115.113.210
 11    15 ms    15 ms    15 ms  62.115.136.195
 12    14 ms    15 ms    14 ms  213.248.72.146
 13    20 ms    20 ms    23 ms  184.105.81.109
 14    74 ms    20 ms    20 ms  216.66.84.42

Trace complete.
« Last Edit: February 20, 2021, 04:06:18 PM by AndrewButterworth »
Logged