Recent posts

#31

Questions & Answers / Re: Tunnel auto deletion / exp...

Last post by kcochran - April 16, 2026, 09:47:27 AM

The ping is nice, but we usually check the actual traffic received from the other side of the tunnel.  If we've seen zero bytes from the remote end in that time period, the tunnel is eligible for removal.  Our routine ping checks should run that up if the remote side is configured, so functionally not too far off.

#32

Questions & Answers / Re: IPv6 tunnel and GeoIP

Last post by supergvozd - April 15, 2026, 06:59:24 AM

Login to your https://dns.he.net/ account and add LOC and the coordinates for your location.

Please clarify, should I have my own registered domain? Does it matter where I register domain?

#33

Questions & Answers / Re: Tunnel auto deletion / exp...

Last post by snarked - April 15, 2026, 12:54:14 AM

Your tunnel must respond to pings, and if it is silent for 90 days, it is deleted.  I don't remember whether the pings are via IPv4 or IPv6, but it is considered "best practice" to allow both.  For IPv6, the tunnel endpoint is used, not the routed /64 or /48.  I do not recall whether changing the IPv4 tunnel endpoint also resets the timeout period.

#34

Questions & Answers / Tunnel auto deletion / expiry ...

Last post by paver - April 14, 2026, 02:54:56 AM

Hi,

I've been a user of the service for a year or two now and noticed that my tunnel had recently been deleted (within the past 2 weeks or so).

Could it be because I'd not updated my IP there for some time? I have a script running on my Mikrotik which will auto update the tunnel when my public ipv4 changes, but it hasn't for some time.

What is the official policy on inactivity & deletion?

Thanks

[**how**]

#35

IPv6 on Windows / Re: unreachable from outside

Last post by cnsh - March 30, 2026, 01:47:50 AM

YES. So tell me **how**. Please. Redefining doesn't help, mate.

#36

IPv6 on Windows / Re: unreachable from outside

Last post by snarked - March 27, 2026, 01:57:00 PM

Doing protocol 41 in IPv6 yields IPv6 encapsulated in IPv6.  That is not what you want.  You want IPv6 encapsulated in IPv4.

#37

IPv6 on Windows / Re: unreachable from outside

Last post by cnsh - March 25, 2026, 04:41:48 PM

Nope. Setting the protocol number to 41 automatically snaps protocol type to IPv6. There's not even a choice to set a protocol type to IPv4

[IPv4]

#38

IPv6 on Windows / Re: unreachable from outside

Last post by snarked - March 23, 2026, 12:38:29 AM

what do you mean by 41 for IPv4? There isn't a selection for which whether I accept 41 on IPv4 or IPv6. Just a "Protocol 41".
Can you tell me where I can allow protocol 41 on IPv4? redefining doesn't help...

Set protocol type to IPv4.
Set protocol number to 41.
There are no ports for the protocol.
Allow that.

#39

IPv6 on Windows / Re: unreachable from outside

Last post by cnsh - March 19, 2026, 04:30:41 AM

Brief sum up of my issue:
- IPv6 port stays closed and blocked while the same port number on v4 is opened.
- It is NOT A ROUTER ISSUE. TURNING OFF THE PC'S FIREWALL OPENS THE V6 PORT.
- It is not protocol 41 rule issue. I have already allowed protocol 41 on my firewall, with edge traversal allowed.

Someone please give me a solution, this thing has been bugging me for weeks

#40

IPv6 on Windows / Re: unreachable from outside

Last post by cnsh - March 19, 2026, 03:00:56 AM

minor update. I tried to run a port scan to my server, and accidently scanned port 53, the DNS port. It was open. But the server's other IPv6 port was closed while the IPv4 one open.