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

News:

Welcome to Hurricane Electric's Tunnelbroker.net forums!

Main Menu

Recent posts

#1
IPv6 on Windows / nexthop not working
Last post by cnsh - February 10, 2026, 04:40:43 PM
Hello. I removed an IPv6 tunnel I had before and made a new one, and even though the previous tunnel worked just fine, this new one won't. I did all the configuration process as same as before. When I do tracert -6 google.com, the nexthop seems to not function.
Tracing route to google.com [2404:6800:400a:1001::66]
over a maximum of 30 hops:

  1     *        *        *     Request timed out.
  2     *        *        *     Request timed out.
  3     *        *        *     Request timed out.
  4     *        *        *     Request timed out.
  5     *        *        *     Request timed out.
  6     *        *        *     Request timed out.
  7     *        *        *     Request timed out.
  8     *        *        *     Request timed out.
  9     *        *        *     Request timed out.
 10     *        *        *     Request timed out.
 11     *        *        *     Request timed out.
 12     *        *        *     Request timed out.
 13     *        *        *     Request timed out.
 14     *        *        *     Request timed out.
 15     *        *        *     Request timed out.
 16     *     ^C
although I can reach the gateway
Pinging 2001:470:35:287::1 with 32 bytes of data:
Reply from 2001:470:35:287::1: time=105ms
Reply from 2001:470:35:287::1: time=112ms
Reply from 2001:470:35:287::1: time=109ms
Reply from 2001:470:35:287::1: time=122ms

Ping statistics for 2001:470:35:287::1:
    Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
    Minimum = 105ms, Maximum = 122ms, Average = 112ms

and yes, I did delete the old tunnel interface; ipconfig -all shows only one tunnel interface.
#2
General Questions & Suggestions / Does not work site dns.he.net
Last post by worknd - February 02, 2026, 01:18:46 AM
I can not get access to site dns.he.net
#3
Questions & Answers / Re: rwhois.he.net:4321 is down...
Last post by idealneck - January 29, 2026, 10:25:32 AM
Cloudflare does the following for their WARP service:

$ whois 104.16.0.0
% IANA WHOIS server
% for more information on IANA, visit http://www.iana.org
% This query returned 1 object

refer:        whois.arin.net

inetnum:      104.0.0.0 - 104.255.255.255
organisation: ARIN
status:      ALLOCATED

whois:        whois.arin.net

changed:      2011-02
source:      IANA

# whois.arin.net

NetRange:      104.16.0.0 - 104.31.255.255
CIDR:          104.16.0.0/12
NetName:        CLOUDFLARENET
NetHandle:      NET-104-16-0-0-1
Parent:        NET104 (NET-104-0-0-0-0)
NetType:        Direct Allocation
OriginAS:
Organization:  Cloudflare, Inc. (CLOUD14)
RegDate:        2014-03-28
Updated:        2024-09-04
Comment:        All Cloudflare abuse reporting can be done via https://www.cloudflare.com/abuse
Comment:        Geofeed: https://api.cloudflare.com/local-ip-ranges.csv
Ref:            https://rdap.arin.net/registry/ip/104.16.0.0

QuoteComment:        Geofeed: https://api.cloudflare.com/local-ip-ranges.csv
#4
Questions & Answers / Re: rwhois.he.net:4321 is down...
Last post by idealneck - January 29, 2026, 10:18:26 AM
I thought the whois referral might have a link to https://tunnelbroker.net/export/google.

I asked a geoip provider (forgot which, I had submitted to various different geoip providers asking for my geolocation to be updated; most have done so at this point) to fetch https://tunnelbroker.net/export/google but one of them stated that it had to be linked to in the whois data before they would trust it.
#5
Questions & Answers / Re: rwhois.he.net:4321 is down...
Last post by snarked - January 26, 2026, 02:26:09 AM
What makes you think that most geoip databases follow the whois referral or RFC 8805 data to begin with?  Some only list the info from the RIRs in their address allocation databases.  All of this is up to each geoip feeds' discretion.

As long as your own info is correct in each publishing of the above original sources, you have done all that you can do.
#6
Questions & Answers / rwhois.he.net:4321 is down; co...
Last post by idealneck - January 22, 2026, 01:42:58 AM
The geoip for my address range is out of date in most geoip database for a week now and I'm wondering if the cause is that the whois server isn't responding. It is actually correct at https://tunnelbroker.net/export/google

I am not exactly sure how geofeeds work but my understanding is that the whois server would reference the geofeed URL in the whois and geoip providers end up ingesting that. I am thinking that the whois being down means they are no longer checking that geofeed.

rwhois.he.net:4321 is specifically down, the web interface is https://rwhois.he.net up but the whois server itself gets a connection refused response.
#7
Questions & Answers / Re: Move tunnel to another com...
Last post by evantkh - January 16, 2026, 07:32:25 AM
Quote from: Parodper on January 15, 2026, 06:20:55 AMSo uh, I didn't do anything, and now it works? Sorry for the noise.

@evantkh, thanks for the tip, although I didn't get to try it.

Looks like you need to wait for NAT mapping expiration (for protocol 41) before you can use on another computer.
#8
Questions & Answers / Re: Move tunnel to another com...
Last post by Parodper - January 15, 2026, 06:20:55 AM
So uh, I didn't do anything, and now it works? Sorry for the noise.

@evantkh, thanks for the tip, although I didn't get to try it.
#9
Questions & Answers / Re: Move tunnel to another com...
Last post by evantkh - January 15, 2026, 05:26:56 AM
Try rebooting the router.
#10
Questions & Answers / Move tunnel to another compute...
Last post by Parodper - January 15, 2026, 03:33:23 AM
Hi,

I'm trying to move a tunnel, from one machine (A) to another (B). I set up the 6in4 in B, and removed the tunnel from A, but I can't get B to work. Both machines are in the same LAN, behind NAT. The config is the same in both machines, except for the local endpoint, which is the machine's private IP.

A worked without issue, and if I do a portscan, I can see that A still receives ICMP Request and SYN. ICMP Request from B don't get any response.

I tried unplugging A for a while, using the WAN address, and switching the Client IPv4 Address around, to see if I could invalidate whatever cache there is, but nothing worked.