I sure wish Starlink supported IPv6. They're a brand new ISP planning for millions of customers and decided from the start they couldn't get enough IPv4 addresses for everyone. Fair enough! But we're stuck with Carrier Grade NAT and it is a drag.<p>On Starlink it's impossible to host a server socket directly, which makes any peer to peer networking a PITA. Geocoding IP addresses doesn't work so I have to bend over backwards to convince, say, Youtube TV that I'm in the Sacramento metro and not LA where the POP is. Also the shared IP addresses seem to trip a lot of DDOS protection; I fill out 10x as many CAPTCHAs on Starlink as I do on my other ISP. And I sometimes get random network stability problems; a few weeks ago Starlink screwed something up so no one could keep a persistent connection up more than a few minutes. Seems to be fixed now, but I bet it was their CGNAT system.<p>I realize half the world lives with CGNAT. It's not unusable, at least web browsing works more or less. But IPv6 would solve all these problems. A little surprised that a new ISP created in 2021 wouldn't have IPv6 support as one of their launch features. There's hints they are trying to get it working but it's not an official thing now. Some discussion: <a href="https://www.reddit.com/r/Starlink/comments/tjr90n/starlink_ipv6_in_2022/" rel="nofollow">https://www.reddit.com/r/Starlink/comments/tjr90n/starlink_i...</a>
Meanwhile, Github is completely unreachable via IPv6 to this day.<p>Found that out the hard way the other week when I went to order a build server without an IPv4.
Its mostly impossible to run servers only with IPv6 since for some reason Canonical/Ubuntu decided to require IPv4 for snap, after years of not having any issues with IPv6 only deb mirrors.<p>Go is also basically bound to IPv4 since it depends on github to pull packages<p>its time to make hall of shame for software that does not allow developers to build IPv6 only going forward.
My website has a few hundred thousand users.<p>My development is completely user driven.<p>I get hundreds of feature requests and other emails regarding my site per month.<p>So far, not a single user mentioned IPv6.<p>So I never added an AAAA record.<p>The codebase has grown for over 10 years now.<p>God knows what subtle breakages would happen when IPv6 requests come in.<p>I wonder if I ever will add IPv6 or just leave the site running on IPv4 forever.
Question for the peanut gallery: Suppose I have a legacy ipv4 host which simply cannot do ipv6. Why couldn't I put some black box on my network connection in between my host and my uplink, which translates my host's IPv4 into a 4-over-6 IPv6 address? The black box can accept either v6 traffic and translate it for my host, or v4 and pass it straight through. The host only ever sees v4 traffic. V6-only clients can resolve an AAAA record against my host, and V4 clients can still resolve an A record.<p>As long as there is sufficient penetration of these black boxes, virtually everything should be able to talk to everything over v6, and the v4 shim can be removed.<p>I imagine this black box could be a relatively inexpensive ASIC or FPGA that could be a stand-alone widget, baked into hardware network adapters, or just built into routers, middleboxes, etc.
At waipu.tv (Video streaming) we have 64% of users connected via IPv6. Compared to 2021 adoption has stalled. 2020 was 56%. waipu.tv is germany-only traffic.
In the UK at least one of our main providers Virgin Media has still not enabled support for IPv6, to the extent that websites such as <a href="https://www.havevirginmediaenabledipv6yet.co.uk/" rel="nofollow">https://www.havevirginmediaenabledipv6yet.co.uk/</a> exist to vent frustration
I appreciate IPv6 link local. mDNS + ipv6 ll addresses on my home network means I can connect to local devices, by name (mydevice.local) regardless of whether or not the router or DHCP/RA+DNS is working.
Anyone go out of their way to disable IPV6 on all their systems, even at the hardware level, like on routers etc? What's a good reason to avoid IPV6?
My guess is mostly mobile traffic?<p>I run a personal tech website containing OSS projects, and have been supporting v6 for more than a decade. Currently seeing few hundred unique visitors per day.<p>IPv6 has been steady at ~15% of all inbound requests for the past 5 years, with zero signs of increase.<p>Both my own fixed adsl service and a different mobile carrier do not offer v6, so I have to jump through hoops to verify my server setup.
I realize there are a million ways to leak addresses, but in theory is a private ipv6 space brute forceable? ie: I have every service listen on a port on some IP, they all discover each other through some specific channel (like dns). Assuming the attacker doesn't have access to that channel, they would have to start scanning every ip to try to discover services, yeah?
I'd be using IPv6, but it's not directly supported by Sonic Fiber in the bay area, strangely enough. Need to use 6in4 tunnelling if you want it.
What happens to games and in general applications, which are old and only have an IPv4 input field? How is it bridged to IPv6? If a friend only has an IPv6 address, how can I connect to them?<p>I guess I will have to set up a VPN, which internally uses IPv4 addressing?
I am surprised of such a low number. ISP and mobile carriers have been supporting ipv6 for years already.<p>Is it because a large portion of the traffic is done through corporate enterprise networks and proxies? Enterprises are the ones slowing down the adoption of ipv6.
Around 2008, my university (utwente.nl) supported IPv6. Google contacted us, asking if they could wishlist our network for IPv6 Google services. We agreed.
In my country, an ISP giving an IPv6 is rare, but using CG-NAT is incredibly common. I think they don't want to update the routers in the main nodes.
iCloud Private Relay is helping here. The network I’m on right now doesn’t have IPv6 but with iCloud Private Relay enabled visiting the IPv6 testing sites shows IPv6 in use.
Why can't we paste aan ipv6 address into the browser address bar and have it go to that address? I'm forced to open [long brackets ] and the it works. Why!????<p>Ipv4 address just works without the hitch
The whole removal of nat and directly connecting to the destination with the source address seems like a privacy and security nightmare.. imo..<p>The security extension thing seems a bit wack. I'd still like all my traffic to originate from a single source and be tagged with that address only. This possible?
None of the computers I own personally use IPv6. IPv6 is a bad idea. IPv6 is a straight connection from the Internet through everything in the network, right to the individual machine.<p>Give my IPv4 and NAT or turn the Internet off.
“In December 1998, IPv6 became a Draft Standard for the IETF,[2] which subsequently ratified it as an Internet Standard on 14 July 2017.”<p>40% adoption after 25 years? Really highlights how terrible IPv6 is in terms of backwards compatibility.<p>What we needed was an internet protocol with the benefits of IPv6 that runs as an extension to the IPv4 stack.<p>The current approach to duplicate everything into IPv6 is wasteful and time consuming, proven by the extremely slow adoption rate.