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

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Main Menu

Recent posts

#1
General Questions & Suggestions / IPV6 PTR record
Last post by dizik - April 18, 2024, 10:42:35 AM
#2
Questions & Answers / Some known ipv6 websites (incl...
Last post by thebas - April 16, 2024, 04:00:53 PM
Hello, Trying to make progress on IPV6 certification, I can never pass the explorer level because the page can never identify I'm using IPV6.

I have set up a 6in4 tunnel on my mikrotik router, everything looks fine. I got an ip address on my desktop that was advertised by it.

I disabled IPV4 on network interface properties to make sure I was using IPV6.

I can access a lot of websites, like google search, gmail, youtube, whatsapp, wikipedia and some others. I can use microsoft teams, whatsapp application, microsoft outlook (can send and receive email), but some websites that I'm sure are IPV6 ready, like he.net and ipv6-test.com, does not work, the page keeps trying to load until they time out.

Does anybody knows how can I make it work, so I can finally pass the explorer level?

Thanks!
#3
Questions & Answers / AWS Public IP marked "This net...
Last post by DroidFreak32 - April 15, 2024, 05:23:24 AM
Hello

I want to use HE.net tunnelbroker on an AWS IP that falls under 13.124.0.0/14

Unfortunately I get a "This network is restricted"
Is there anyway to get around this issue? What could be the cause as I could not find this documented on this forum.
#4
Questions & Answers / Re: rDNS delegation stopped wo...
Last post by kamil445 - April 02, 2024, 10:30:40 AM
Also have this issue, delegated networks to dns.he.net disappeared from dns.he.net panel, but NS records still working, just can't edit, add or remove existing.
#5
Questions & Answers / rDNS delegation stopped workin...
Last post by bxrwtat - March 18, 2024, 11:17:52 AM
It looks like the rDNS delegation of the routed prefixes stopped working some time ago.
I did this a few years ago and I'm now trying to do so again on a new tunnel, but to no avail.
Either clicking on "delegate to dns.he.net" or setting any other namserver on tunnelbroker.net appears to work, but in fact the NS records are not being added.
#6
Quote from: kcochran on March 28, 2023, 12:25:36 PMUnder your tunnel's information page, you can set the rDNS servers.  There's a convenience link to set it to dns.he.net.  For tunnel broker ranges assigned to dns.he.net, they will show up automatically under dns.he.net when logging in with the same tunnelbroker username.

I just tried this. My DNS and Tunnelbroker usernames are the same, but the rDNS is just not showing up at dns.he.net
#7
Quote from: LucaZ on April 07, 2023, 07:03:46 AMIf yes, is "d.c.b.a.d.c.b.a.0.47.0.1.0.0.2.ipv6.arpa" the domain name to refer to in the "Add a new slave" function?

I'm trying to do the same, but I came across your questions and noticed a typo
The reverse should be d.c.b.a.d.c.b.a.0.7.4.0.1.0.0.2.ipv6.arpa
#8
General Questions & Suggestions / Re: Add new slave
Last post by 1977er - March 09, 2024, 02:21:46 PM
Had the same error message. In my case the origin was missing on the NS lines of the zonefile:

Instead of

@   IN NS   ns1.example.com.
@   IN NS   ns1.he.net.
@   IN NS   ns2.he.net.

I had

   IN NS   ns1.example.com.
   IN NS   ns1.he.net.
   IN NS   ns2.he.net.
#9
Questions & Answers / Re: Bug in tunnelbroker.net wh...
Last post by kcochran - March 03, 2024, 07:34:28 AM
That code is a simple, very basic blur(), called on every update, even the invalid IP one.  If that breaks, I'd wonder more about the Canary build having some odd issue.
#10
Questions & Answers / Bug in tunnelbroker.net when u...
Last post by sebastiannielsen - March 02, 2024, 07:32:39 PM
Noticed a weird bug when updating Client endpoint IP for my tunnel in:
Version 124.0.2437.0 (Officiell version) canary (64 bitar)

When entering the new Client IP in tunnel settings, and then clicking anywhere else to confirm, it would just do nothing. It would only react if you entered a deliberately incorrect IP (as in... 256.256.256.256 - then it would say incorrect format).

I first tought the server which sends the ICMP had changed from 66.220.2.74 (my ICMP permit firewall rule is pinned to 66.220.2.74) but then I looked in firewall logs and saw no rejected ICMP packets.

So apparently it would not fire a request to tunnelbroker's servers when updating client IP.

So I switched browser to a older version:
Version 123.0.2420.10 (Officiell version) beta (64 bitar)

THEN it worked to update client IP and the ICMP packet was sent.



So you might want to look into the page and check the javascript code that handles updating Client IP, and check why it doesn't work in:
Version 124.0.2437.0 (Officiell version) canary (64 bitar)
but does work in:
Version 123.0.2420.10 (Officiell version) beta (64 bitar)