Hacker News new | ask | show | jobs
by throw0101c 360 days ago
If anyone wants to try / use IPv6, but their ISP does not provide it, Hurricane Electric (HE) has offered a tunnel service for many years now:

* https://tunnelbroker.net

* https://ipv6.he.net

There are scrips available to bring up a tun device on your system (or router) and route traffic over it:

* https://fedoraproject.org/wiki/IPv6_tunnel_via_Hurricane_Ele...

* https://brandonrozek.com/blog/obtaining-ipv6-address-hurrica...

* https://wiki.dd-wrt.com/wiki/index.php/IPv6_setup_Hurricane_...

* https://forum.mikrotik.com/t/auto-update-script-for-hurrican...

* https://docs.rockylinux.org/guides/network/hurricane_electri...

4 comments

One annoying caveat with these is that for streaming services, you will need to figure out how to disable those tunnels, because they're blocked as if they're VPNs for getting around region restricted content blocks.

Still works great, though. Thanks to the power of RAs, you can get all of your devices hooked up with an IPv6 address even if your router doesn't support HE tunnels, just have any device in your network advertise a /64 and it'll become an IPv6 router (assuming your router doesn't filter out RAs for security reasons).

Very useful for hosting stuff from within your home network without actually needing to mess with port forwarding rules.

Hurricane Electric is great, but as more and more people have ISP provided IPv6, 'normal' users leave the tunnels, and network services have been flagging he.net tunnels as abuse.

I had to stop using ipv6 for most of my network because too many sites decide to put up barriers or simply refuse to work.

aspect worth noting: up to my knowledge HE's tunnel will work only if you're assigned public IPv4 by your ISP. if you're behind a carrier grade NAT - too bad, you'll need to use another solution to get IPv6 to your home.
Strange. This sounds like something Hurricane Electric specifically limited. There’s nothing in CGNAT that would naturally break such a tunnel
HE is using plain stateless IPv6 in IPv4 tunnel - it's neither TCP nor UDP, it's not NAT'able.

it's relatively simple for them to implement [ the stateless part ] but due to that puts some requirements on the party establishing the tunnel.

I use tunnels all day like this with cgnat on multiple devices.
Go Fiber (Shentel) is one such ISP, and they will gladly switch you to a public IP for no cost if you contact their support. Sadly they don’t support IPv6 yet.
Happy "customer" here. I've been using their free 6in4 tunnel through OpenBSD for about five years and have had no mentionable problems. I configure mine solely with OpenBSD's network interface files, e.g. /etc/hostname.gif0:

  tunnel <my current IPv4> <HE's IPv4 endpoint>
  inet6 <my desired IPv6 address> 128 alias <HE's IPv6 gateway>
  !route -n add -inet6 default <HE's IPv6 gateway>
I use the connectivity to reach a cluster of VPSes in AWS deliberately set-up without public IPv4 addressing, which would otherwise represent a large part of the monthly costs because of buttholes like Jeff Bezos actively monetizing IPv4 address space.
> because of buttholes like Jeff Bezos actively monetizing IPv4 address space.

IPV4 addresses are finite and rapidly being depleted. What other solution do you have to manage demand of a finite resource other than charging for it?

My stance is that common connectivity shouldn't cost an additional $3.70 a month on top of already egregious traffic costs. The price per IP today is about $30. The lifetime of the investment is infinite and upkeep is in the grand scheme of things nothing. The markup profit is insane. It's a new behavior, pure usury, seizing an opportunity to profit on a crisis. To offer some contrast (without getting into the sizes of their respective turfs) Oracle doesn't charge a dime.
We are in crisis precisely because nobody charged for IPv4 addresses in the past, and so overwhelming majority of those are wastefully allocated. What you want would exacerbate the crisis.
We're in this crisis because we failed to anticipate the explosive growth of the Internet. It took a bit into the 2000s until we stopped doling out generously oversized networks to everyone who asked. Vetting the need would've been the right requirement. Shutting the door for organizations with not enough money would've hampered progress.
Don't worry, we've learned nothing and will repeat the same mistake with IPv6:

https://news.ycombinator.com/item?id=42671847

https://www.theregister.com/2024/12/06/apnic_huawei_ipv6/

Yes, and why did people ask for these oversized networks? That’s right, because addresses were free.