• Welcome to Hurricane Electric's IPv6 Tunnel Broker Forums.

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Main Menu

Recent posts

#31
Questions & Answers / Re: IPV6 tunnel and MTU issue ...
Last post by snarked - July 20, 2025, 10:47:15 PM
Your understanding is incorrect.

1280 bytes is the minimum size of an IPv6 packet.
Typical IPv6 in IPv4 encapsulated packets have an MTU of 1480 bytes (1500 bytes less 20 for the IPv4 outer header].

Try increasing your IPv6 MTU to 1480 bytes first.  Worry about the rest only if this doesn't solve your problem.
#32
Questions & Answers / IPV6 tunnel and MTU issue ?
Last post by moeller - July 20, 2025, 07:13:18 AM
Hi Forum,

  I am experimenting with IPV6 and run into an issue when using an HE as IPV6 tunnelbroker. As far as I understand the MTU of the tunnel interface will be 1280 instead of the usual 1500. Now when I connect to a TLS encrypted side I see that I can connect via IPV4 but not with IPV6. I noticed that the TLS Server Hello packet is > 1280 bytes long ( over IPV4 ) and wonder if the HE tunnel endpoint sends ICMP DF to the server to split the TLS packet. Can someone confirm that that will be done and if the server blocks ICMP I get this issue ?

Thank you
Markus
#33
Questions & Answers / Re: hongkong ipv6 tunnel serve...
Last post by greyhound - July 18, 2025, 07:02:07 AM
Quote from: jslhk on July 16, 2025, 06:39:30 PMSame here.
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".
#34
Questions & Answers / Re: hongkong ipv6 tunnel serve...
Last post by jslhk - July 16, 2025, 06:39:30 PM
Same here.
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.
#35
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.
#36
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
#37
Questions & Answers / Re: hongkong ipv6 tunnel serve...
Last post by binnychan - July 14, 2025, 09:14:14 PM
#38
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
#39
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?
#40
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 :-(