Hurricane Electric's IPv6 Tunnel Broker Forums

Advanced search  


Welcome to Hurricane Electric's forums!

Pages: 1 2 [3] 4 5 ... 10
 on: July 08, 2021, 03:29:24 AM 
Started by hobbsfamily - Last post by broquea
We don't offer 6in6 tunnels with

Also Verizon doesn't learn route announcements from their residential customers, nor do we issue permission for broker users to have others announce their allocations from our system. So you can't use our IPv6 address space over your native VZ connection, they only work over the tunnel.

 on: July 08, 2021, 02:57:03 AM 
Started by hobbsfamily - Last post by hobbsfamily
Here's my situation:

I use Verizon's 5G Home Internet. I'm pretty happy with it as a service. However, I introduced a router between my modem and my network. Things are working OK, except because of the way Verizon / the modem has implemented IPv6, I am not able to get IPv6 addresses on the LAN. The way it appears to work is that the modem itself has a public IPv6 address, and I'm able to get a public IPv6 address as my WAN address on the router. However, Verizon doesn't use prefix delegation. It just hands connected devices a /128 prefix (a single address) which means I have no way to give addresses with any certainty to my LAN once the router is in place. With devices connected directly to the modem they get public IPv6 addresses because the modem is capable of handing out a single /128 at a time via DHCPv6

I started to setup a 6in4 tunnel using HE on my router (it's a Ubiquiti Dream Machine Pro), but I'm running into issues related (I believe) to double NAT and the fact that the modem doesn't appear to forward protocol 41 to a machine in the DMZ. I can get my LAN machines issued IPv6 addresses from my HE network by setting up DHCPv6 in the router but when doing a PING6 after configuring the 6in4 tunnel, I get a single packet response back and then everything stops. (not focused on that right now for this question)

Because I'm able to get a single valid IPv6 address on the router, but only one, I'm wondering if it's possible to use tunnelbroker somehow to tunnel my HE /64 or /48 via my single public IPv6 address? so like instead of making a tunnel between my LAN and HE's IPv4 server address, can I make a tunnel between my LAN and HE's IPv6 server address since I'd be able to reach that from the router itself (but not from machines on the network) My public IPv6 address is quite dynamic but I assume there's a way to update the public address similar to how I'm updating my dynamic IPv4 address..

Apologies if my question is poorly stated, I'm just starting out with this stuff and trying to figure things out.

Thanks in advance for putting up with my ignorance!

 on: July 03, 2021, 04:30:41 PM 
Started by tjeske - Last post by tjeske
Can anyone look into this?

 on: July 01, 2021, 03:33:41 AM 
Started by jthnetdkeu - Last post by helmotz
I have the same problem on Fedora 34.
Did you find a solution meanwhile?


 on: June 29, 2021, 05:36:36 AM 
Started by myon98 - Last post by myon98
Hello, I use HE even though I already have native IPv6, mostly in order to experiment with a routed /48 prefix because my ISP doesn't give any. (Or can't because of the NTT NGN)

However for some destinations the latency (and throughput) were noticeably slow when going through HE compared to my native connection, and at first I thought I should use my native IPv6 when speed is important even though it would mean chopping up my precious single /64.

But when I started to look into traceroutes I realized that on certain local destinations they tend to get routed across the pacific ocean and back, gaining hundreds of milliseconds during the trip.

The most noticeable destinations were AS2500 (WIDE) and some other academic networks. Some of the hosts inside them are popular mirrors for many open source OS distributions such as {tsukuba,nara}

I have attached traceroute results collected today, sometimes from my HE tunnel, and because I have access to a wifi hotspot inside AS2500 I was also able to collect reverse direction as well.

Thank you for providing this service and I hope this information is helpful in some way.

 on: June 28, 2021, 04:45:22 AM 
Started by tjeske - Last post by tjeske
KleyReX seems to have massive infrastructure problems for a couple of weeks now. Massive packet loss (over 50%), somewhere when changing from over to Can/should HE review their peering with AS35366 and maybe halt it until they fix their issues?

 on: June 17, 2021, 12:20:00 PM 
Started by eancode - Last post by kcochran
Not at this time.  Certain instances may go away as traffic to them drops to zero and their hardware ages, but those sites we still see reasonable traffic to will certainly continue.

 on: June 14, 2021, 08:43:14 AM 
Started by eancode - Last post by snarked
I hope not.  I still get a few packets a week coming from 2002::/16 addresses at my colocated server, and my DSL providers donít t carry IPv6.  Frontier gives out DSL modems that donít even support it.  IPv6 has been around for 20+ years now and some ISPs still donít t support it!

 on: June 14, 2021, 05:07:26 AM 
Started by eancode - Last post by eancode
Good morning,
as the 6to4 (at least the anycast part) has been deprecated, is there any plan to decommission the 6to4 gateways?

 on: June 12, 2021, 02:21:34 AM 
Started by kamil445 - Last post by kamil445
Again geolocation is wrong since maybe 6-7 days

Pages: 1 2 [3] 4 5 ... 10