Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Author Topic: tserv1.ams1.he.net does not accept pings + no IPv6 traffic  (Read 127 times)

ictd01

  • Newbie
  • *
  • Posts: 5
tserv1.ams1.he.net does not accept pings + no IPv6 traffic
« on: February 19, 2021, 12:36:28 PM »

Hello,

My tunnel doesn't seem to work at the moment. The tunnel has worked sinds 2018.

The status page shows tserv11.ams1 with a good status (up). I did try to ping the IP address 216.66.84.46 but I don't receive any replies.
I did also try to ping the IP from my VPS - but I didn't receive any replies.

I guess there are issues with tserv11.ams1 at the moment? I have everything configured in pfSense and the gateway is being reported with status down.

Any ideas? Thanks.

Regards,

Bouke
Logged

kumy

  • Newbie
  • *
  • Posts: 12
Re: tserv1.ams1.he.net does not accept pings + no IPv6 traffic
« Reply #1 on: February 19, 2021, 12:39:14 PM »

Hi,
I have asked the same thing some minutes before :) https://forums.he.net/index.php?topic=4077.0
"Glad" to hear that it's not a problem on my side.
Bests
Logged

ictd01

  • Newbie
  • *
  • Posts: 5
Re: tserv1.ams1.he.net does not accept pings + no IPv6 traffic
« Reply #2 on: February 19, 2021, 12:48:55 PM »

Hi,
I have asked the same thing some minutes before :) https://forums.he.net/index.php?topic=4077.0
"Glad" to hear that it's not a problem on my side.
Bests

The server tserv11.ams1 seems to be down at the moment. It's being reported down at https://tunnelbroker.net/status.php (at this moment I write this).
 
I am also using a routed subnet (for IPv4) and it dipped some minutes ago. Might be something at AMS-IX? Not sure... can't find much at the moment.
Logged

kumy

  • Newbie
  • *
  • Posts: 12
Re: tserv1.ams1.he.net does not accept pings + no IPv6 traffic
« Reply #3 on: February 19, 2021, 01:01:03 PM »

It's back again !  :)
Logged

ictd01

  • Newbie
  • *
  • Posts: 5
Re: tserv1.ams1.he.net does not accept pings + no IPv6 traffic
« Reply #4 on: February 19, 2021, 01:04:41 PM »

It's back again !  :)

The outage started on Feb 19 20:28:58 CET and is still going on.
Still can't ping 216.66.84.46 from home...

Edit: I can ping the IP from my VPS now. Odd it doesn't work from home. I will clear my IPS now and see if that helps.
« Last Edit: February 19, 2021, 01:08:32 PM by ictd01 »
Logged

kumy

  • Newbie
  • *
  • Posts: 12
Re: tserv1.ams1.he.net does not accept pings + no IPv6 traffic
« Reply #5 on: February 19, 2021, 01:06:37 PM »

I confirm it work from here
Code: [Select]
# ping 216.66.84.46
PING 216.66.84.46 (216.66.84.46) 56(84) bytes of data.
64 bytes from 216.66.84.46: icmp_seq=1 ttl=58 time=69.5 ms
64 bytes from 216.66.84.46: icmp_seq=2 ttl=58 time=9.44 ms


IPv6 tunnel is back and working.

Also status page is now green https://tunnelbroker.net/status.php
Logged

ictd01

  • Newbie
  • *
  • Posts: 5
Re: tserv1.ams1.he.net does not accept pings + no IPv6 traffic
« Reply #6 on: February 19, 2021, 01:16:34 PM »

I confirm it work from here
Code: [Select]
# ping 216.66.84.46
PING 216.66.84.46 (216.66.84.46) 56(84) bytes of data.
64 bytes from 216.66.84.46: icmp_seq=1 ttl=58 time=69.5 ms
64 bytes from 216.66.84.46: icmp_seq=2 ttl=58 time=9.44 ms


IPv6 tunnel is back and working.

Also status page is now green https://tunnelbroker.net/status.php

22:14 :: my tunnel is up and running too :-)

Code: [Select]
# ping 216.66.84.46
PING 216.66.84.46 (216.66.84.46) 56(84) bytes of data.
64 bytes from 216.66.84.46: icmp_seq=32 ttl=56 time=8.23 ms
64 bytes from 216.66.84.46: icmp_seq=33 ttl=56 time=7.84 ms
64 bytes from 216.66.84.46: icmp_seq=34 ttl=56 time=8.10 ms
64 bytes from 216.66.84.46: icmp_seq=35 ttl=56 time=7.44 ms
64 bytes from 216.66.84.46: icmp_seq=36 ttl=56 time=8.27 ms
64 bytes from 216.66.84.46: icmp_seq=37 ttl=56 time=7.59 ms
64 bytes from 216.66.84.46: icmp_seq=38 ttl=56 time=8.13 ms
64 bytes from 216.66.84.46: icmp_seq=39 ttl=56 time=8.08 ms
64 bytes from 216.66.84.46: icmp_seq=40 ttl=56 time=7.72 ms
64 bytes from 216.66.84.46: icmp_seq=41 ttl=56 time=7.94 ms
64 bytes from 216.66.84.46: icmp_seq=42 ttl=56 time=7.55 ms
64 bytes from 216.66.84.46: icmp_seq=43 ttl=56 time=7.40 ms
64 bytes from 216.66.84.46: icmp_seq=44 ttl=56 time=7.84 ms
64 bytes from 216.66.84.46: icmp_seq=45 ttl=56 time=48.0 ms
64 bytes from 216.66.84.46: icmp_seq=46 ttl=56 time=7.62 ms
64 bytes from 216.66.84.46: icmp_seq=47 ttl=56 time=7.94 ms
64 bytes from 216.66.84.46: icmp_seq=48 ttl=56 time=44.6 ms
64 bytes from 216.66.84.46: icmp_seq=49 ttl=56 time=7.80 ms
64 bytes from 216.66.84.46: icmp_seq=50 ttl=56 time=8.29 ms
64 bytes from 216.66.84.46: icmp_seq=51 ttl=56 time=55.6 ms
64 bytes from 216.66.84.46: icmp_seq=52 ttl=56 time=7.50 ms
64 bytes from 216.66.84.46: icmp_seq=53 ttl=56 time=7.48 ms
64 bytes from 216.66.84.46: icmp_seq=54 ttl=56 time=8.04 ms
64 bytes from 216.66.84.46: icmp_seq=55 ttl=56 time=7.49 ms
64 bytes from 216.66.84.46: icmp_seq=56 ttl=56 time=7.87 ms
64 bytes from 216.66.84.46: icmp_seq=57 ttl=56 time=7.69 ms
64 bytes from 216.66.84.46: icmp_seq=58 ttl=56 time=7.80 ms
64 bytes from 216.66.84.46: icmp_seq=59 ttl=56 time=7.74 ms
64 bytes from 216.66.84.46: icmp_seq=60 ttl=56 time=7.58 ms
64 bytes from 216.66.84.46: icmp_seq=61 ttl=56 time=7.80 ms
64 bytes from 216.66.84.46: icmp_seq=62 ttl=56 time=7.70 ms
64 bytes from 216.66.84.46: icmp_seq=63 ttl=56 time=7.77 ms
64 bytes from 216.66.84.46: icmp_seq=64 ttl=56 time=7.80 ms
64 bytes from 216.66.84.46: icmp_seq=65 ttl=56 time=7.74 ms
64 bytes from 216.66.84.46: icmp_seq=66 ttl=56 time=7.69 ms
64 bytes from 216.66.84.46: icmp_seq=67 ttl=56 time=7.84 ms
64 bytes from 216.66.84.46: icmp_seq=68 ttl=56 time=71.9 ms
64 bytes from 216.66.84.46: icmp_seq=69 ttl=56 time=7.54 ms
64 bytes from 216.66.84.46: icmp_seq=70 ttl=56 time=8.20 ms
64 bytes from 216.66.84.46: icmp_seq=71 ttl=56 time=7.82 ms
64 bytes from 216.66.84.46: icmp_seq=72 ttl=56 time=7.66 ms
64 bytes from 216.66.84.46: icmp_seq=73 ttl=56 time=7.68 ms
64 bytes from 216.66.84.46: icmp_seq=74 ttl=56 time=7.91 ms
64 bytes from 216.66.84.46: icmp_seq=75 ttl=56 time=7.62 ms
64 bytes from 216.66.84.46: icmp_seq=76 ttl=56 time=8.18 ms
64 bytes from 216.66.84.46: icmp_seq=77 ttl=56 time=7.99 ms
64 bytes from 216.66.84.46: icmp_seq=78 ttl=56 time=8.03 ms
64 bytes from 216.66.84.46: icmp_seq=79 ttl=56 time=9.00 ms
64 bytes from 216.66.84.46: icmp_seq=80 ttl=56 time=8.00 ms
64 bytes from 216.66.84.46: icmp_seq=82 ttl=56 time=12.6 ms
64 bytes from 216.66.84.46: icmp_seq=83 ttl=56 time=7.84 ms
64 bytes from 216.66.84.46: icmp_seq=84 ttl=56 time=7.71 ms
64 bytes from 216.66.84.46: icmp_seq=86 ttl=56 time=7.91 ms
64 bytes from 216.66.84.46: icmp_seq=87 ttl=56 time=7.75 ms
64 bytes from 216.66.84.46: icmp_seq=88 ttl=56 time=83.9 ms
64 bytes from 216.66.84.46: icmp_seq=89 ttl=56 time=8.06 ms
64 bytes from 216.66.84.46: icmp_seq=90 ttl=56 time=8.13 ms
64 bytes from 216.66.84.46: icmp_seq=91 ttl=56 time=8.02 ms
64 bytes from 216.66.84.46: icmp_seq=92 ttl=56 time=7.67 ms
64 bytes from 216.66.84.46: icmp_seq=93 ttl=56 time=113 ms
64 bytes from 216.66.84.46: icmp_seq=94 ttl=56 time=7.81 ms
64 bytes from 216.66.84.46: icmp_seq=95 ttl=56 time=7.74 ms
64 bytes from 216.66.84.46: icmp_seq=96 ttl=56 time=8.23 ms
64 bytes from 216.66.84.46: icmp_seq=97 ttl=56 time=7.46 ms
64 bytes from 216.66.84.46: icmp_seq=98 ttl=56 time=7.45 ms
64 bytes from 216.66.84.46: icmp_seq=99 ttl=56 time=8.01 ms
64 bytes from 216.66.84.46: icmp_seq=100 ttl=56 time=8.29 ms
64 bytes from 216.66.84.46: icmp_seq=101 ttl=56 time=7.78 ms
64 bytes from 216.66.84.46: icmp_seq=102 ttl=56 time=7.74 ms
64 bytes from 216.66.84.46: icmp_seq=103 ttl=56 time=8.09 ms
64 bytes from 216.66.84.46: icmp_seq=104 ttl=56 time=7.73 ms
64 bytes from 216.66.84.46: icmp_seq=105 ttl=56 time=8.62 ms
64 bytes from 216.66.84.46: icmp_seq=106 ttl=56 time=7.62 ms
64 bytes from 216.66.84.46: icmp_seq=107 ttl=56 time=7.81 ms
64 bytes from 216.66.84.46: icmp_seq=109 ttl=56 time=7.56 ms
64 bytes from 216.66.84.46: icmp_seq=110 ttl=56 time=8.07 ms
64 bytes from 216.66.84.46: icmp_seq=111 ttl=56 time=7.77 ms
64 bytes from 216.66.84.46: icmp_seq=112 ttl=56 time=7.79 ms
64 bytes from 216.66.84.46: icmp_seq=113 ttl=56 time=8.28 ms
64 bytes from 216.66.84.46: icmp_seq=114 ttl=56 time=8.05 ms
64 bytes from 216.66.84.46: icmp_seq=115 ttl=56 time=7.62 ms
64 bytes from 216.66.84.46: icmp_seq=116 ttl=56 time=7.66 ms
64 bytes from 216.66.84.46: icmp_seq=117 ttl=56 time=12.10 ms
64 bytes from 216.66.84.46: icmp_seq=118 ttl=56 time=7.90 ms
64 bytes from 216.66.84.46: icmp_seq=119 ttl=56 time=36.0 ms
64 bytes from 216.66.84.46: icmp_seq=120 ttl=56 time=7.85 ms
64 bytes from 216.66.84.46: icmp_seq=121 ttl=56 time=7.77 ms
64 bytes from 216.66.84.46: icmp_seq=122 ttl=56 time=23.9 ms
64 bytes from 216.66.84.46: icmp_seq=123 ttl=56 time=7.71 ms
64 bytes from 216.66.84.46: icmp_seq=124 ttl=56 time=7.70 ms
64 bytes from 216.66.84.46: icmp_seq=125 ttl=56 time=7.44 ms
64 bytes from 216.66.84.46: icmp_seq=126 ttl=56 time=7.63 ms
64 bytes from 216.66.84.46: icmp_seq=127 ttl=56 time=7.66 ms
64 bytes from 216.66.84.46: icmp_seq=128 ttl=56 time=30.3 ms
64 bytes from 216.66.84.46: icmp_seq=129 ttl=56 time=349 ms
64 bytes from 216.66.84.46: icmp_seq=130 ttl=56 time=7.72 ms
64 bytes from 216.66.84.46: icmp_seq=131 ttl=56 time=7.50 ms
64 bytes from 216.66.84.46: icmp_seq=132 ttl=56 time=24.8 ms
^C
--- 216.66.84.46 ping statistics ---
132 packets transmitted, 98 received, 25.7576% packet loss, time 1047ms
rtt min/avg/max/mdev = 7.401/16.043/348.599/37.472 ms
Logged

kisser

  • Newbie
  • *
  • Posts: 1
Re: tserv1.ams1.he.net does not accept pings + no IPv6 traffic
« Reply #7 on: February 19, 2021, 01:45:59 PM »

ping to 216.66.84.46  is working but ipv6 is still down!
Logged

ictd01

  • Newbie
  • *
  • Posts: 5
Re: tserv1.ams1.he.net does not accept pings + no IPv6 traffic
« Reply #8 on: February 19, 2021, 02:16:42 PM »

ping to 216.66.84.46  is working but ipv6 is still down!

It works for me but there seems to be some loss (time is CET).

Code: [Select]
Feb 19 22:15:08 dpinger 79698 IPV6_TUNNELV6 ::IPv6::Removed:: Clear latency 11321us stddev 12953us loss 7%
Feb 19 21:49:32 dpinger 79698 IPV6_TUNNELV6 ::IPv6::Removed:: Alarm latency 0us stddev 0us loss 100%
Feb 19 21:49:30 dpinger 79698 send_interval 500ms loss_interval 2000ms time_period 60000ms report_interval 0ms data_len 1 alert_interval 1000ms latency_alarm 500ms loss_alarm 20% dest_addr ::IPv6::Removed:: bind_addr ::IPv6::Removed:: identifier "IPV6_TUNNELV6 "
Logged

broquea

  • Sr. Network Engineer, HE.NET AS6939
  • Administrator
  • Hero Member
  • *****
  • Posts: 1742
Re: tserv1.ams1.he.net does not accept pings + no IPv6 traffic
« Reply #9 on: February 19, 2021, 04:27:16 PM »

As responded to trouble tickets opened, there was and issue with the node that was resolved after some emergency maintenance.
Logged