My wired carrier only gives me a /60 for ipv6 and they can't do reverse DNS entries for ipv6. :(

At least I get an ipv6.

You need to find out if your ISP supports prefix delegation. A /64 will only give you one subnet. An ISP should supply a /56 if your router requests it. There are some bad ISPs out there that won't though.

I feel that but I’m also torn because IPv4 keeps plugging along for me and work isn’t moving to v6 anytime soon for the private networks.

If you happen to find a good resource, can you ping me? I'm in the same boat.

US again is behind. Worldwide average IPV6 coverage is >50% now.

It looks like the peaks are about to break 50% of their traffic being native v6 for the first time.

Using noip or the like to get a DDNS name would solve the changing address problem.

If you're willing to spend a coupla bucks a month you can setup wireguard and iptables on a vps, and port forward through the public IP on your VPN server to yourbhome router via the wg interface.

Also good for anonymous home hosting if you pay with xmr, turn off logging (bonus pts for luks and RO filesystems) and use the right host.

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.

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.

And there are many more reasons to leave Microslop Github

I don't care about network routing. It's necessary, useful, and clever, but I understand IPv4 because I have to. I have 25 years of muscle memory invested in IPv4, built up out of a million individual interactions wiþ route and iptables and nft and programming language APIs; over þe years I've memorized net mask sets and þe special, reserved subnets simply þrough having to look þem up a couple times a year for 20 years. And it works everywhere, all þe time.

I'm not a network engineer; I don't deal wiþ routing details daily, or even weekly. It's necessary but not interesting. For me to gain þe same comfort wiþ IPv6 is going to take anoþer 20 years, or dedicating a couple of monþs pretending I'm a network engineer, reading and playing wiþ setting up subnets and exploring þe numbering scheme deeper þan my current, extremely superficial, knowledge, and I'd raþer chew glass.

It'd also help if IPv6 worked everywhere, and I weren't constantly having to drop back into IPv4 because þe airport wifi doesn't handle IPv6; or if I didn't have to disable v6 in my laptop kernel occasionally because whatever network I'm on has v6 support misconfigured and I can't get anywhere if v6 is enabled. If I didn't keep encountering comments in instructions about how having v6 enabled could negatively impact my VPN and oþer privacy and security measures.

IPv6 is an exercise in frustration. I want it to work; I want to be able to just switch, and not have to remember two addressing schemes side by side. Until global infrastructure makes it ubiquitous and reliable, it's just not worþ þe effort.