←back to thread

296 points jmillikin | 7 comments | | HN request time: 0.021s | source | bottom
Show context
simonjgreen ◴[] No.44411529[source]
Slightly misleading title, this is more “getting to the IPv4 internet via an IPv6 tunnel through a VPS”. Also just called 4in6.

Interesting nonetheless!

We find at our ISP that if we break something with IPv4 we experience a very different type of support issue to if we break IPv6. Breaking v4 results in, broadly, a pretty hard “down” state. While folks are unhappy, it is at least simple. Breaking v6 results in weird, and a partial down, which manifests for the users as partial outages, slow starts due to fall back, etc. Especially if their gateways believe there is v6 when there isn’t.

replies(4): >>44411884 #>>44412095 #>>44412377 #>>44413734 #
1. jeroenhd ◴[] No.44412377[source]
When my IPv4 died last time, I noticed it mostly because Github didn't work anymore. These days, most consumer websites just work on IPv6. That said, people whose routers were only provisioned IPv4 DNS servers did have a full outage.

If Microsoft would get off their incompetent assets already, my biggest concern would've been remembering the mDNS hostname I've assigned to my router so I could log in and see if IPv4 is back already.

replies(4): >>44413445 #>>44414697 #>>44414850 #>>44416451 #
2. mananaysiempre ◴[] No.44413445[source]
The POSIX bug tracker is not accessible over IPv6, either, because their AWS setup does not support it. The website administrators refused to fix this[1].

[1] https://austingroupbugs.net/view.php?id=1623

3. elcritch ◴[] No.44414697[source]
The Meta Quest software also sucks at this. You’d expect an essentially new platform struggling with this. Valve is basically all IPv4 afaict too.

Pretty annoying and lazy if you ask me.

replies(1): >>44423381 #
4. mikepurvis ◴[] No.44414850[source]
My ISP (TekSavvy) manages to semi regularly screw up ipv4 and what I notice is that "big" sites like Amazon, Google, Facebook, SO, etc all work as before, but it's the in-between sites, someone's blog on a search result, etc— that's the stuff that breaks.
5. immibis ◴[] No.44416451[source]
It's easy enough to port forward v6 on some server to v4 GitHub - i'm doing it right now but can't remember the address. Think there's any demand for this, considering you can save $0.50-$2 per month per server by not having v4?
replies(1): >>44423416 #
6. jeroenhd ◴[] No.44423381[source]
The Valve stuff is extra infuriating because a lot of their assets seem to be hosted on CDNs that do have IPv6, but their backend servers are stick with IPv4. When IPv4 breaks, you can look and buy games, but actually playing them will fail because of DRM checks.
7. jeroenhd ◴[] No.44423416[source]
Some VPS providers already provide free IPv4 solutions.

Setting up a server works fine for server stuff, but it'd get you blocked and banned everywhere for having a data center IP while just browsing or trying to watch Netflix.

For my servers I could do it the other way around and save a dollar per month, but then I'd be sending emails from a residential IPv4 address, which will never ever make it past any spam filter.