Hurricane Electric provides free IPv6 tunnels. They will give you a /48 if you request it. I used them for several years before I got native IPv6. It does require a public IPv4 address, so it won’t work with CGNAT.
I had heard of them before but thought it had some bandwidth limits. A brief search right now makes me think I had the wrong impression. I will consider giving them a try. Thanks!
All my hardware supports IPv6; my router and modem support IPv6; my ISP supports IPv6.
And yet… I can’t use IPv6 because my ISP won’t turn it on if your modem is in bridge mode; they want to control the entire stack before they’ll let me use it. They only route it from their own hardware.
That’s an “advantage” of IPv6; your local IP addresses now belong to the ISP, so the router can’t do anything like policy based routing. If your device is using a Starlink IPv6 address, the only route to it is Starlink. If both ISPs are giving you a delegation, your devices need to get IPs on both networks and then it’s up to each device/OS to implement any policy you want, not the router.
This is, of course, a massive pain in the arse. It breaks VPNs, policy based routing, and high-availability/failover, unless you do address translation at the router - but in that case, you might as well just use IPv4, since address translation is the great bear you’re using IPv6 to avoid. All for the highly dubious benefit of exposing all your internal infra directly to the Internet.
IPv6 is great for public traffic, but way more trouble than it’s worth for internal networks.
You are not logged in. However you can subscribe from another Fediverse account, for example Lemmy or Mastodon. To do this, paste the following into the search field of your instance: [email protected]
This is the official technology community of Lemmy.ml for all news related to creation and use of technology, and to facilitate civil, meaningful discussion around it.
Ask in DM before posting product reviews or ads. All such posts otherwise are subject to removal.
Rules:
1: All Lemmy rules apply
2: Do not post low effort posts
3: NEVER post naziped*gore stuff
4: Always post article URLs or their archived version URLs as sources, NOT screenshots. Help the blind users.
5: personal rants of Big Tech CEOs like Elon Musk are unwelcome (does not include posts about their companies affecting wide range of people)
6: no advertisement posts unless verified as legitimate and non-exploitative/non-consumerist
7: crypto related posts, unless essential, are disallowed
I’m interested in running ipv6 for my home but my ISP doesn’t support ipv6 yet heh. Maybe I’ll send them this graph.
Hurricane Electric provides free IPv6 tunnels. They will give you a /48 if you request it. I used them for several years before I got native IPv6. It does require a public IPv4 address, so it won’t work with CGNAT.
I had heard of them before but thought it had some bandwidth limits. A brief search right now makes me think I had the wrong impression. I will consider giving them a try. Thanks!
All my hardware supports IPv6; my router and modem support IPv6; my ISP supports IPv6.
And yet… I can’t use IPv6 because my ISP won’t turn it on if your modem is in bridge mode; they want to control the entire stack before they’ll let me use it. They only route it from their own hardware.
My SMB router doesn’t support ipv6 for many functions including policy routing between isps
Imagine my surprise to see my ipv4 through T-Mobile and my ipv6 through Starlink.
That’s an “advantage” of IPv6; your local IP addresses now belong to the ISP, so the router can’t do anything like policy based routing. If your device is using a Starlink IPv6 address, the only route to it is Starlink. If both ISPs are giving you a delegation, your devices need to get IPs on both networks and then it’s up to each device/OS to implement any policy you want, not the router.
This is, of course, a massive pain in the arse. It breaks VPNs, policy based routing, and high-availability/failover, unless you do address translation at the router - but in that case, you might as well just use IPv4, since address translation is the great bear you’re using IPv6 to avoid. All for the highly dubious benefit of exposing all your internal infra directly to the Internet.
IPv6 is great for public traffic, but way more trouble than it’s worth for internal networks.