9 ms·
I tried living on IPv6 for a day
- sybercecurity 1y agoThread was pretty much a greenfield deployment at the time, so it use of IPv6 was easy to specify. There was now legacy IPv4 to support or otherwise it would probably be a mess as well.
- WarOnPrivacy 1y agoturning off IPv4 ... was harder than I expected it would be This is followed by reasonable reasons they struggled to unwind themselves from IPv4 (for the experiment) - but eventually got it worked out. Conversely: When I hotspot from my phone, T-Mobile frequently makes that an IPv6-only experience.
- evaXhill 1y ago‘Considering the pool of available IPv4 addresses has been exhausted for quite a while now, and was running out for public use years ago’ I thought it was logical that most systems that have adopted IPv6. Crazy to think that it turns out it wasn’t, but shout out to apple and their stringent dev requirements bc they require support IPv6-only networks.
- mike_d 1y agoThe pool is not exhausted, the IPv6 cabal realized after 20 years that actively fighting against freeing up more space was the only way they could drive adoption. If we just stop listing 240/4 as a bogon we could be allocating from it in a few years.
- wredcoll 1y agoWow, that would get us a whole... 6 months of extra runway!
- redox99 1y agoNowadays I consider IPv4 address scarcity almost a feature, because of rate limiting and DDoS mitigation in general.
- chasing0entropy 1y agoThis guy cyber securities. Last thing I want are an infinite number of additional attack vectors on what will inevitably be a feeding frenzy of zero day exploits(not in the protocol but the implementation)
- TacticalCoder 1y ago> Nowadays I consider IPv4 address scarcity almost a feature ... The real godsend of IPv4 is that it accidentally forced NAT. This saved, through the decades, hundreds of millions of vulnerable machines from being directly exposed and owned. I consider IPv4 saved us from Windows botnets affecting nearly the entire world. No, NAT is not security. But accidentally it prevented oh-so-many machines from getting owned. When I got my first Internet connection I could literally access other people's Windows machine for my ISP was putting me on the same LAN as other people. I'd do silly things like have "Your Windows machine is insecure" printed on their printers. This was in IPv4 times: my ISP would put me on a subnet with 256 other machines (I'm talking about times where a 28.8 modem was still a thing btw). I cannot being to imagine the total and complete chaos had IPv6 existed back then. People don't understand how insecure and wild things were back in the days. IPv4 saved the Internet, accidentally, thanks to NAT.
- 7bit 1y agoThe only thing NAT achieved is that it leads people like you, who know little about it to believe it somehow increased security, which is completely wrong. Any Firewall can simply block all incoming traffic and it would have the same effect as NAT, without the computational overhead that NAT incurs...
- PaulKeeble 1y agoI recently switched ISP to one that supports IPv6 and I have had nothing but problems. I have had DNS servers going missing from OpenDNS, I have seen all sorts of really weird routing errors and transient problems, its barely usable at all. Linux seems to be more strict about how it handles IPv6 and I found my server couldn't find its upgrade packages because some of their mirrors are broken for IPv6 routing. All in all it was a mess and I turned it off. My ISP must be partially at fault but it was clear Debian was too as was OpenDNS and most of my problems no one could explain what was happening or why.
- commandersaki 1y agoHehe, it's kind of funny to contrast the IPv6 evangelists and the Linux desktop evangelists push hard for adoption, only for it to fall flat for ordinary users.
- thescriptkiddie 1y agoi have at&t fiber and their ipv6 worked perfectly fine for years, until a one day they started dropping packets like mad and it never got better
- erinnh 1y agoI find these experiences really interesting, because in Germany all major ISPs have been doing IPv6 for years and years now. I dont think any normal person thinks about IPv6 or IPv4 here.
- deathanatos 1y agoEven in America, ISPs fall roughly in two buckets: no IPv6 support at all, or IPv6 is supported and Just Works, like your case. The parent poster's case is unusual. Normal people here don't think about v6 either, and the majority of people have a v6 connection.
- throw0101d 1y ago> I recently switched ISP to one that supports IPv6 and I have had nothing but problems. I was previously with an ISP that support IPv6 and had zero problems. In fact IPv6 worked "too well" at one point: I had put "facebook.com" in my /etc/hosts file pointing to 0.0.0.0 at one point to reduce tracking. I then noticed I got the little FB icons again at some point and couldn't figure out why things were 'broken' (i.e., not blocking). Turned out that after IPv6 was enabled I had to add ::1. That blocked FB again. IPv6 made connectivity to FB work again.
- throw0101d 1y ago> Thankfully, Verizon FiOS rolled out IPv6 support to my area a while ago; otherwise, this whole thing would have ended here. Hurricane Electric (for one) offers IPv6 tunnels: * https://ipv6.he.net https://ipv6.he.net You can configure it on your router: * https://openwrt.org/docs/guide-user/network/ipv6/ipv6_henet https://openwrt.org/docs/guide-user/network/ipv6/ipv6_henet * https://docs.netgate.com/pfsense/en/latest/recipes/ipv6-tunnel-broker.html https://docs.netgate.com/pfsense/en/latest/recipes/ipv6-tunn... * https://docs.opnsense.org/manual/how-tos/ipv6_tunnelbroker.html https://docs.opnsense.org/manual/how-tos/ipv6_tunnelbroker.h... Or an individual host: * https://wiki.archlinux.org/title/IPv6_tunnel_broker_setup https://wiki.archlinux.org/title/IPv6_tunnel_broker_setup * https://docs.rockylinux.org/guides/network/hurricane_electric_ipv6_tunnel/ https://docs.rockylinux.org/guides/network/hurricane_electri... * https://genneko.github.io/playing-with-bsd/networking/freebsd-tunnelv6-he/ https://genneko.github.io/playing-with-bsd/networking/freebs...
- john01dav 1y agoWhen I used a small local ISP that did not support ipv6 before switching to AT&T fiber¹ I tried to set this up, but they demand an email on a non-gmail domain, and I wasn't going to pay to set that up nor was I going to use my work email. It's a bad assumption that any non-malicious user cares enough about websites to have one. 1: I'd prefer to have stayed with the local ISP despite the lack of ipv6, but they wanted $8,000 to bring fiber to my new place and that was not worth it with at&t fiber being present.
- johnklos 1y agoGmail is a cesspool, and Google couldn't give the slightest bit of a shit. So does it really surprise you that people who share free services might not want to give those free services to people who use the cesspool service that doesn't care about abuse?
- dazilcher 1y agoGMail is the most popular email provider by a wide margin. Denying service to the largest cohort of email users is indeed surprising, ridiculous, and self-defeating.
- ghusto 1y agoWhat are the advantages of IPv6 if I don't want direct routing (NAT is a feature for me, not a workaround)?
- rasguanabana 1y agoThe only thing that comes to mind for me is simpler header, but not sure if it makes much of a difference anyway.
- some_bird 1y agoYes, it makes a difference: about 8 milliseconds. Properly implemented IPv6 has a lower latency. (and is more efficient, though i believe the energy savings are negligible) See this map: https://stats.labs.apnic.net/v6perf https://stats.labs.apnic.net/v6perf
- wmf 1y agoNone.
- eddythompson80 1y agoCheaper IPs?
- yjftsjthsd-h 1y agoIf someone doesn't want direct routing, why would that matter?
- wmf 1y agoIPv6 is cheaper but also you can't access half the Internet.
- simoncion 1y agoI've had "native" IPv6 service for something like twenty years. I've not had a problem with accessing any of the internet. If you're hinting that roughly half of the internet-connected servers don't have IPv6 addresses, then my reply is "so what?". Only idiots are suggesting that folks who aren't running an experimental lab (or ISPs that have the expertise required to set up the NATs needed to reach the IPv4 internet from v6-only service) go IPv6-only.
- IshKebab 1y agoI feel like a more interesting question is what proportion of users can connect to an IPv6-only server?
- some_bird 1y agoAlmost 50% according to google: https://www.google.com/intl/en/ipv6/ https://www.google.com/intl/en/ipv6/ (But other measurement statistics project a lower value.)
- tialaramex 1y agoWhen I bought a new gaming PC recently it default configured on my home network with IPv6 but not IPv4. It was interesting which features Microsoft considers crucial (and so worked on IPv6) and which were not important (and so they just didn't function, claiming that there's no Internet even though of course there is and e.g Google works) Advertising for example, was essential. Spewing garbage I don't want, absolutely critical to Microsoft's bottom line apparently. But registration so that I can turn off that advertising? Not important, so that was not available until I gave the machine IPv4.
- herczegzsolt 1y agoMy networks are IPv6 only for a couple of years, but I do have to run NAT64 (jool) and use a DNS64 resolver (i use a google-provided, but you could run your own) It had very little benefits at the beginning, but having dedicated publicly routed addresses started to become really conevinent. IPv6 with a regulary changing dynamic prefix still sucks though to this day ... :-(
- hnlmorg 1y agoHow do manage dynamic prefixes? This is the problem that’s prevented me from adopting IPv6.
- mshroyer 1y agoYou can additionally set up ULA: https://en.wikipedia.org/wiki/Unique_local_address https://en.wikipedia.org/wiki/Unique_local_address The way I do this, my internal DNS resolves hosts to their fixed ULA addresses. For the handful that are accessible externally, public DNS resolves to their address on the current public prefix.
- herczegzsolt 1y agoI did try that, but it ended in an infinite fight with the source address selection algorithm and DNS caches. Also, unique-local addresses are deprecated as far as I know.
- simoncion 1y ago> ...it ended in an infinite fight with the source address selection algorithm and DNS caches... What did this fight look like? For the past fifteen, twenty years, I have NATted IPv4, globally-routable IPv6, and ULA IPv6 addresses on all of my machines attached to the internet-accessible VLANs on my LAN. The only trouble I've noticed was when ISP maintenance caused me to lose the globally-routable prefix for a little while and my franken-router started passing ULA traffic out the WAN interface. [0] I'd love to hear what you've been seeing, so I can see if there's trouble that I've been overlooking. > ...unique-local addresses are deprecated as far as I know. ULAs are not deprecated. You may be thinking of site-local addresses. See the first paragraph of section 1 here: [1] [0] The obvious firewall rule fixed that. [1] <https://www.ietf.org/archive/id/draft-ietf-v6ops-ula-usage-considerations-05.html https://www.ietf.org/archive/id/draft-ietf-v6ops-ula-usage-c...>
- apitman 1y agoIPv4 is never going away barring massive adoption of p2p protocols to drive the switch. Sadly NAT and SNI solve most of the problems well enough for things to limp along indefinitely. The only orgs with the power to fix this from the top down are incentivized to maintain the centralized status quo. So get out there and p2p
- Hizonner 1y agoNAT and SNI are some of the major things that prevented widespread adoption of P2P to begin with.
- apitman 1y agoYep. And the reason they were successful is because you can solve the problem on your end without the other end needing to do anything. IPv6 requires both parties to do something. So now we're stuck with NAT and SNI.
- 7bit 1y ago> IPv6 requires both parties to do something. Please explain
- Hizonner 1y agoIf I run out of IPv4 addresses for my own network, I can install NAT and make that problem (sort of, mostly, vaguely) go away. If I want to use IPv6 to solve my IPv4 address shortage problem, and I want to communicate with you, I have to wait for you to also install IPv6. SNI isn't really the same thing. For one thing it has actual positive benefits, very much unlike NAT (and no NAT is not a fucking security feature and is orthogonal to fucking firewalls don't make me come over there). And for me to use SNI, your browser (or whatever) has to send SNI, so it's still a change on only one end. But it still does let me put more than one service on a single IP address, and you only have to upgrade one program, probably a program you were going to upgrade anyway, rather than change your whole networking structure. The way this should have worked was that IPv4 should have been turned off completely in the public Internet around 1997 or 1998. But ISPs didn't want to tell the much smaller number of much more sophisticated admins back then that they had to, you know, change things. So people just kept baking IPv4 into more and more things, and throwing in more and more NAT, and not even bothering learn or teach IPv6... and ignoring all the things they were breaking. Many (not all!) of the things they were breaking were things that really came into play if you were trying to do P2P. Like, for instance, the ability to, you know, actually make a connection to any random peer. There are hacks, but they work poorly when they work at all. So since NAT was everywere, P2P didn't have a chance. There were other forces at work too, but basically everybody's business model and expectations gelled around centralization in a way that might have had a chance of not happening if there hadn't been NAT all over the place.
- habibur 1y agoMaybe it's me, but I think IPv6 should have been 8 bytes instead of 16 and somewhat backward compatible with IPv4. Like how 2-byte Unicode was struggling and UTF-8 saved it.
- yjftsjthsd-h 1y ago> and somewhat backward compatible with IPv4. How would it be at all backward compatible other than what NAT64 already does?
- sedawkgrep 1y agoI suspect the thinking is that all of IPv4 could have been a contained within the IPv6 space. Perhaps at at the very beginning or very end of it. Any time you would reference an IPv4 address when v6 enabled, the stack would simply fill in the remaining bits and forward your packets down the line. This had to have been thought about though, and I suspect the architects of v6 felt it would've been sub-par to what we have. No idea if that's true though.
- yjftsjthsd-h 1y ago> I suspect the thinking is that all of IPv4 could have been a contained within the IPv6 space. Perhaps at at the very beginning or very end of it. They actually went with 64:ff9b::/96 as the default (though IPv6 is so big that you can just pick another area if you want in ULA space or whatever). > Any time you would reference an IPv4 address when v6 enabled, the stack would simply fill in the remaining bits and forward your packets down the line. There are actually multiple implementations, depending on OS and whether you want it in kernel space or user space. > This had to have been thought about though, and I suspect the architects of v6 felt it would've been sub-par to what we have. No idea if that's true though. They thought about it, named it NAT64 ( https://en.wikipedia.org/wiki/NAT64 https://en.wikipedia.org/wiki/NAT64 ), published it, and it's in wide use. It frequently is combined with 464XLAT ( https://en.wikipedia.org/wiki/IPv6_transition_mechanism#464XLAT https://en.wikipedia.org/wiki/IPv6_transition_mechanism#464X... ) to make the transition mostly invisible to users/applications.
- SoftTalker 1y agoWork is exclusively IPv4 and nobody's talking about changing. Everything at home is IPv4 and I'm not even curious about IPv6. When I have to be, I'll figure it out. Until then, things seem to be working fine.
- kacesensitive 1y agoI did this for a couple days when Comcast's DNS was fucking up when I moved into a new place and was stuck with their modem/router/AP for a bit (which was locked to like 6.6.6.6 or whatever it was). Tried explaining it to several customer support techs but they all just gave up eventually. Was fixed when I ended up getting my own modem and router/AP. But those were an interesting few days. My partner was annoyed they couldn't use Pinterest but YouTube loaded fine. Google search worked but our local pizza joint's site didn't.
- CaliforniaKarl 1y agoOut of curiosity, I had a look at one of our service's login nodes, to see where SSH connections were originating from off-campus. What I found was that approximately 30% were over IPv6. Anecdotally, during weekday working hours, the percentage of IPv6 is higher than (typically over 50%).
- waynesonfire 1y agoWhen an ISP assigns an IPv6 prefix, home networks / homelabs can use that prefix for internal addressing. But if the ISP later changes the prefix, all internal devices using the old addresses break. This makes the concept of globally unique IPv6 addresses seem problematic for end-users. Is there something I’m misunderstanding about how this is supposed to work?
- wredcoll 1y agoI think the main issue is "why is the prefix changing"?
- dogcow 1y agoI recently decided that it was high time to stop ignoring IPv6 after 30 years of computing and actually learn how it is supposed to work. So I started digging in, and there's definitely a lot to like. But I see two big problems that are showstoppers in my opinion, at least for my home network (not even considering the fact that very few residential ISPs even support v6 at this point): 1. Generally speaking, the IPs of your LAN are based on the prefix assigned by the ISP. Most residential ISPs don't offer static prefixes. This means that every time your prefix changes, the IPs of all your devices on your LAN change. Seems like this "feature" was developed in a more idealistic era when people probably thought everyone would be getting static IPv6 addresses, since shortages would never be an issue. Unfortuantely, they failed to foresee the fact that most major ISPs are terrible, greedy organizations that either outright refuse to offer static assignments, or continue treating them as if they were scarce IPv4 resources, charging a premium or requiring business-class service to even get them. 2. The ISPs that do support v6, like Comcast/Xfinity in the USA, are only allocating one /64 prefix. This means you can only have one subnet (VLAN) on your LAN! Why are they being so stingy? I would love to migrate to IPv6, but these two issues alone make it feel like a clown show for home users.
- easterncalculus 1y agoCouple of things - if you want prefixes to stay the same you can use ULAs for your home network. Not ideal but it's available. The 'right' way to manage this is to use DNS, and just have the prefixes auto-update there, or mDNS. For prefix sizes you should be getting a /56 most of the time, especially from major US ISPs. If you're getting a single /64 it's almost definitely an issue with your router's PD setup.
- dogcow 1y agoYeah, I know about the workarounds, but that just kind of defeats the purpose for me. Also, I've read comments from folks stating they were having a hard time getting a larger prefix from Comcast using PD... don't know how universally true that is. Using DNS to resolve everything solves part of the problem, but firewall rules are another issue. The router would need to have the capability to update everything dynamically when the prefix changes. I think this in the works for pfSense, but I'm not sure if its actually supported yet. It looks like you might have to mess around with some 3rd-party script to make it work. I guess I'm just generally disappointed that the whole process seems unnecessarily messy. I don't have a v6-compatible ISP right now anyway. I was thinking about trying a tunnel, but I'm not seeing the benefit in it right now.
- easterncalculus 1y agoGoogle global IPv6 traffic hit the highest ever percentage 49.76% on July 26th. 50% any day now. https://www.google.com/intl/en/ipv6/statistics.html https://www.google.com/intl/en/ipv6/statistics.html
- easterncalculus 1y agoReplying here to say that it hit 49.84% on August 2nd 2025
- mistyvales 1y agoMy ISP still only gives 6rd..
- ectospheno 1y agoWhen PlayStation and Nintendo support ipv6 only then you may see consumers care.
- tonymet 1y agoI've done a few ipv6 migrations. The IPv6 fan community (e.g on reddit and other forums ) needs to accept a dual-stack world and the doubling of complexity required to operate that way. All effort should be about education and support for dual stack. That will be the only successful path to ipv6 adoption. Sure ipv6 has some better features, but dual-stack means you are doubling all of your config (ACLs, naming, firewalls, routing) test cases and vulnerability surface. Moreover, ipv6 is not as intuitive. Shaming people into ipv6 will never work. More effort should be invested into best practices, patterns, migration guides, support communities & more to assist in operating in a dual-stack environment for the foreseeable future. Pure ipv6 will never happen because the weak link breaks the chain. How many people set up an ipv6 VPC with great excitement, and late in the project they deploy from github with "NS lookup failed".
- deleted 1y ago[deleted]
- throw0101d 1y ago> Pure ipv6 will never happen because the weak link breaks the chain. Define "pure". Jen Linkova has been running IPv6-only networks on Google's corporate networks for several years now: * https://www.youtube.com/watch?v=UTRsi6mbAWM https://www.youtube.com/watch?v=UTRsi6mbAWM She is a chair of the 6man WG (and involved in the v6ops WG), and has authored ten RFCs: * https://datatracker.ietf.org/person/furry13@gmail.com https://datatracker.ietf.org/person/furry13@gmail.com Microsoft also is IPv6-only on corporate networks (so more of their IPv4 addresses can be moved to Azure to produce revenue): * https://www.arin.net/blog/2019/04/03/microsoft-works-toward-ipv6-only-single-stack-network/ https://www.arin.net/blog/2019/04/03/microsoft-works-toward-... The author of that article, Veronika McKillop, is head of the UK IPv6 Council: * https://www.youtube.com/@ukipv6council468/videos https://www.youtube.com/@ukipv6council468/videos where you'll find lots of videos on ISPs and other institutions doing IPv6-only or IPv6-mostly (especially nowadays with DHCPv4 Option 108, RFC 8925).
- tonymet 1y agothat's what I'm talking about