A lot of sites out there are still not supporting IPv6 because ... you'll never guess, but dealing with DDoS on IPv6 where your attackers can rotate through addresses quickly is not easy. Amazon Cloudfront and Cloudflare have recently failed to block simple IPv6 attacks for us lately which would not have happened if we only ran IPv4
This is interesting. If you only had IPv4, you’d block a ddos by filtering ip ranges. If some of those ranges were CGNat, you’d be cutting access to possibly millions of innocent addresses or even entire countries.
As IPv4 addresses become more scarce and more people get on IPv6, so more people end up behind IPv4 gateways to reach your IPv4 only service, the greater the chance that they’d be cut off for someone else’s bad behavior.
> cutting access to possibly millions of innocent addresses or even entire countries.
It seems to me, that everybody fine with this, and they don’t care. Even without DDoS. Using VPN or just using Apple’s relay can cut you from large parts of the internet.
> A lot of sites out there are still not supporting IPv6 because ... you'll never guess, but dealing with DDoS on IPv6 where your attackers can rotate through addresses quickly is not easy.
So now everyone should acquire as many IPv6 addresses as possible so they can spread their services over many /64s so if their server gets compromised and put on a blacklist somewhere they can just burn that /64 and move on to another?
Mostly that the coffee shops are the customer of the captive portal solution and the shop runners don't know, don't care, some combination of both that the coffee shop users have IPv6 right now so there is no incentive for the captive portal software or vendor to push the matter. Typically at this point "allowing IPv6" also really means "running two versions of the captive portal and intercept stack" rather than "moving from IPv4 to IPv6".
You get what you pay for. Non-revenue generating services are setup and maintained as cheaply as possible. They're not going to buy extra IT labor to test IPv6. In fact they go in the opposite direction by locking down ports to just ports 53, 80, and 443. Other ports are blocked because non-web traffic includes bandwidth hogs like BitTorrent & Zoom, spam over port 25, and copyright infringement letter generating activities. The most annoying networks even force DNS and HTTP through a proxy leaving TCP 443 as the sole pinhole to the Internet.
My ISP forced a switch maybe a year ago or so. Everything broke and I couldn't connect to anything. I had to change the router and I think then my computer (though that doesn't make sense in hindsight, maybe I just needed a reboot) to force v4 again. I'll hold out as long as I can.
ISPs cannot "force" a switch to IPv6. If they could we'd be on 90% adoption now.
Maybe you need to troubleshoot more and confirm it's actually IPv6 and not just your router failing to e.g. establish a PPPoE session for your IPv4 connection.
Buddy idk what to tell you. One day ai came home from work, nothing could connect out, all my devices had ipv6 addresses and my router (which I rent from my ISP) was set such that every 4/6 option was 6. I don't know why you think the poorly regulated almost-monopolies can't do whatever they want to the router they have remote access to.
Just switched off IPv6 on home network…and that fixed multiple hard to troubleshoot issues I’ve been having. (Eg specific parts of some iPhone apps not loading)
As much as I want to love it…still more hassle than it’s worth
I wonder how whether it's that turning off IPv6 actually improved your connection or just the good old restart-o-jutsu showing its powers again. Many routers soft-reboot or, at the very least, reestablish internet connection which often fixes stuff.
I have enabled IPv6 for years and my conclusion is that IPv6 is never the problem. People simply never consider whether there is a confounding variable involved, and immediately jump to the conclusion that disabling IPv6 == problem solved.
Rediscovered the GitHub version of the problem recently when setting up some new IPv6-only VMs. They couldn't pull any code from our GitHub repos, making those VMs entirely useless.
