Recent posts

#1

Questions & Answers / Re: hongkong ipv6 tunnel serve...

Last post by greyhound - July 18, 2025, 07:02:07 AM

Same here.

Code Select Expand

PING 216.218.221.6 (216.218.221.6) 56(84) bytes of data.
^C
--- 216.218.221.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9240ms
Although https://tunnelbroker.net/status.php shows that tserv20.hkg1 is Up without issue.

Now the status shows tserv20.hkg1 is down, with reason "hardware failure, no ETR".

#2

Questions & Answers / Re: hongkong ipv6 tunnel serve...

Last post by jslhk - July 16, 2025, 06:39:30 PM

Same here.

Code Select Expand

PING 216.218.221.6 (216.218.221.6) 56(84) bytes of data.
^C
--- 216.218.221.6 ping statistics ---
10 packets transmitted, 0 received, 100% packet loss, time 9240ms
Although https://tunnelbroker.net/status.php shows that tserv20.hkg1 is Up without issue.

#3

Questions & Answers / Re: hongkong ipv6 tunnel serve...

Last post by XQZR - July 15, 2025, 09:03:13 PM

I am also having the same issue.

I opened a ticket(in email)'[HE#6647982]',but 72h+ No response.

I don't think the issue is caused by the underwater cable disruption. This is because the tunnel server is local, and tserv1 (216.218.221.2) is functioning properly.

#4

Questions & Answers / Re: hongkong ipv6 tunnel serve...

Last post by chonwingcong - July 15, 2025, 12:33:13 AM

ping per subnet ip ok，server ipv4 and ipv6 is down
PING 216.218.221.2 (216.218.221.2) 56(84) bytes of data.
64 bytes from 216.218.221.2: icmp_seq=1 ttl=58 time=3.29 ms
64 bytes from 216.218.221.2: icmp_seq=2 ttl=58 time=3.58 ms
64 bytes from 216.218.221.2: icmp_seq=3 ttl=58 time=3.27 ms
64 bytes from 216.218.221.2: icmp_seq=4 ttl=58 time=3.42 ms
64 bytes from 216.218.221.2: icmp_seq=5 ttl=58 time=3.39 ms
64 bytes from 216.218.221.2: icmp_seq=6 ttl=58 time=3.50 ms
^C
--- 216.218.221.2 ping statistics ---
6 packets transmitted, 6 received, 0% packet loss, time 5007ms
rtt min/avg/max/mdev = 3.267/3.406/3.578/0.108 ms

#5

Questions & Answers / Re: hongkong ipv6 tunnel serve...

Last post by binnychan - July 14, 2025, 09:14:14 PM

I am also having the same issue, is it related to the broken submarine cable?

Ref : https://smc.peering.tw/
Ref : https://www.facebook.com/seadog007/posts/pfbid02vhq9ZAQD1LPu1TcKY163bocsjwJHeqHNwwWgitnDUDsh2JRmspAFP5DaV3ueqJddl

#6

Questions & Answers / hongkong ipv6 tunnel server do...

Last post by chonwingcong - July 14, 2025, 05:50:42 PM

PING 216.218.221.6 (216.218.221.6) 56(84) bytes of data.

^C
--- 216.218.221.6 ping statistics ---
33 packets transmitted, 0 received, 100% packet loss, time 32753ms

#7

Questions & Answers / access from yggdrasil

Last post by BABUT - July 04, 2025, 07:04:36 AM

could you please be available from yggdrasil? i understand that all your clients have a white static ipv4, and often ipv6, and they come to you purely for fun, and not to solve the problem of nat and other limited access, but maybe you can think a little about the poor and wretched?

#8

General Questions & Suggestions / Re: DNSSEC support?

Last post by Gee-Gee - June 13, 2025, 03:32:53 AM

It 2025 now and we still lack support for DNSSEC :-(

#9

Questions & Answers / no answer from peer at he.net

Last post by rsokoll - June 08, 2025, 02:23:35 AM

Hi,

I use an Ubiquity ER-X and to my best knowledge, everything is configured properly. Tunnel end is 216.66.80.30 which is tserv1.fra1.he.net.
The tunnel interface is up. But I cannot see (tcpdump) any answers to icmp6 ping requests to anywhere. When I tcpdump on the IPv4 interface for traffic from/to 216.66.80.30, I only see outgoing packets. My router's IP is set correctly in the web interface at tunnelbroker.net.

Any ideas?

#10

Questions & Answers / Re: Problems on fra1? (216.66....

Last post by therrmann - June 06, 2025, 05:27:49 AM

I did not get a final answer from HE so far; but currently, the tunnel seems to be in a usable state again.