←back to thread

296 points jmillikin | 1 comments | | HN request time: 0s | source
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 #
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 #
1. 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