13 ms·
The IPv6 Transition
- Kelteseth 2y agoI've mentioned this previously. Without government-mandated standards, implementation could take years. We apply this approach to numerous areas; why should IP be an exception?
- robocat 2y agoA world of being told what to do was not the "dream" of freedom for the internet. If you want the government to mandate standards, vote with your feet and move to China where it has been mandated. I thought the point of the article is that perhaps IPv6 is ultimately unnecessary: worse is better? Why are we engineers so attracted to authoritarianism? The idea of just telling everyone to use the new version seems attractive to me too. Then again I often deeply admire practical engineering compromises. (edited: clarified)
- Kelteseth 2y agoAgreeing on a common standard is not authoritarianism.
- x3n0ph3n3 2y agoGovernments _mandating_ it sure is.
- robocat 2y agoYou said "government-mandated" - do you think your words matter? That doesn't sound like agreement. Agreement is how we have arrived at the imperfect solution we have now... Agreement between various technical and non-technical parties.
- orangeboats 2y agoConversely, blindly categorizing all government mandation as authoritarianism sounds like a highway to all kinds of logical fallacies! Is mandating a fair market (by e.g. punishing monopolies) authoritarian? A sensible person would answer no. Similarly, mandating an Internet Protocol that doesn't require centralization (you know, NAT) and renting an address from the Big Boys (AWS etc) sounds like a perfectly sensible decision to me. > Agreement is how we have arrived at the imperfect solution we have now... I disagree. What we have now is not an explicit agreement, it's a status quo which can be broken by an external force.
- robocat 2y agoA sentence written by a pedant that doesn't help communicate. Followed by another sentence. Ending with a quote that implies a worldview that the government should use violence without any balance "it's a status quo broken by an external force".
- orangeboats 2y agoI don't think you understand what "pedant" means.
- kortilla 2y agoWe have agreed on a common standard. It’s IPv6. Forcing people to use it is authoritarianism.
- Kelteseth 2y agoYou are also forced to use a seat belt. Calling it authoritarianism when we want to enforce a standard is absurd.
- kortilla 2y agoSeat belts have a reason. If I want to communicate with some computers using IPv4 or IPX, that’s my choice. Putting laws on what I can put inside of Ethernet is absolute stupidity
- agubelu 2y agoI fail to see how mandating ISPs to implement and use IPv6 is equivalent to "putting laws on what you can put inside of Ethernet"
- kortilla 2y agoMaybe don’t talk about stuff you don’t have any experience with then. Many ISP products are carrying Ethernet frames (metro Ethernet, the fabric at an exchange) or are even just leasing fiber. In order to force IPv6 and ensure nobody is using IPv4, you absolutely are putting laws on what goes over those Ethernet frames.
- immibis 2y agoPresumably the proposed law is about normal Internet service. If you have Internet then you have IP6. If you don't then what you have isn't Internet. If your company cannot provide IP6 then you are not an internet service provider because you do not provide Internet service. Why do people immediately assume that any possible regulation will be the stupidest possible regulation? Corporate brainwashing?
- Affric 2y agoPick up the benefits of ending IPv4 development sooner. One less thing to ship with every bit of network software. One less learning outcome taught in every networking course. One less piece of organisational complexity in every ISP. Fewer rent seekers in the IP address space. But these benefits are network effects and we only achieve them once IPv4 is relegated to the archaics of the internet tech stack.
- thayne 2y agoThe government has more levers to pull than just a mandate requiring adoption. For example: - require support for ipv6 in order to qualify for government grants to ISPs to build or expand - Require ipv6 support from any SaaS sold to the government - require government websites to be served on ipv6, possibly exclusively on ipv6 by a certain deadline, although that might be too aggressive. - grant tax exemptions on costs to upgrade equipment to support ipv6 - levy a tax on ipv4 None of those removes your freedom to use ipv4, they just provide incentives to use ipv6.
- jonathanlydall 2y agoWhile legislation would be way to actually make IPv6 transition happen, what is the justification for such legislation and cost it would impose on the industry? And that is the point of this article, for most participants of the internet the benefits don’t presently justify the involved cost. Peer to peer networking is important to rare users like me so I can do things like host a private Minecraft server from my house for my brothers and I to play on, but this is not yet a problem for me on IPv4. Interestingly a few years back while I was moving and had no internet for a few weeks I temporarily moved the Minecraft server to my brother’s house and we discovered he was on CG NAT which was a total nonissue before then. I sent an email to the ISP saying we wanted to expose a port and asked how to do so and they changed my brother’s account to be given a public IP no questions asked or extra costs. And I found this policy okay because probably 99.999% of internet users don’t do anything over the internet where a public IP would make any difference to their life. I expect once enough of the internet is on IPv6 the cost benefit pendulum will swing the other way, but we're not there yet and it’s not clear when it might happpen.
- Affric 2y agoStatic IP here in Australia costs AUD 5 per month for residential users… I think it’s just a price signal to entirely disincentivise it to anyone who doesn’t need it.
- thayne 2y agoIn the US, if you want a static IP you often need to purchase a business connection, which is usually significantly more expensive (and residential connections are already expensive), and may not even be available if you live in a residential area.
- BenjiWiebe 2y agoIIRC, when talking to our (USA) ISP, we need to upgrade to a business plan before we can then pay an extra fee per month for the static IP.
- 2y ago
- AndrewDucker 2y agoThe DoD mandated v6 a few years back. The US government could easily dictate that all of their supplied software had to support it.
- aidenn0 2y agoI suspect that (nearly) all of the supplied software already supports it. Software support for ipv6 is nearly ubiquitous; configuration for ipv6 is the holdup.
- ndriscoll 2y agoAs far as I know, the US federal government does have a mandate that agencies be ipv6-only by end of 2025. Systems that are not converted by then require justification for why they cannot do so along with a replacement plan. See https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-07.pdf https://www.whitehouse.gov/wp-content/uploads/2020/11/M-21-0...
- lucw 2y agoIPv6 adoption will take place overnight when either google chrome, Android or iOS start showing a warning on IPv4-only networks. ISPs and tech companies will start to get flooded with support calls asking about it and will choose to roll out IPv6 to make the problem go away. Chrome forced the web to go 100% https, the same thing will happen eventually with IPv6.
- gorgoiler 2y ago> In 2024 it’s estimated that 20 billion devices use the Internet, yet the Internet’s IPv4 routing table only encompasses 3.03 billion addresses … sharing each individual IPv4 address across an average of 7 devices. …but the graph below that text shows 40% of traffic is IPv6, so the v4 space is only shared across 12e9 devices? In my experience the big holdouts these days are corporate networks. All my domestic ISPs (cell, home, data centre) provide IPv6 and most devices use it by default. Meanwhile at the office we’re struggling to bring up a new internal service because our v4 IPAM is a legacy mess where the most you can calve off is a “class A” /27.
- alexchamberlain 2y agoFWIW, domestic ISPs in the UK are lagging on IPv6; I'm with Vrigin Media and, afaict, there is no immediate plan to deploy it either.
- Woansdei 2y agoLast time I called Virgin media to get from the loyal customer (extra high) rate to something closer to what new customers get they just said no. I switched to Vodafone which is cheaper and double the speed and got me IPv6. I think it might just be Virgin sitting on a large amount of IPv4 addresses and not wanting to spend any money on supporting v6 when they can just overcharge their loyal customers.
- smallupdate 2y agoBoth BT and Sky are fully IPv6, many altnets are too, it's actually Virgen Media that is the problem in the UK. In the case of Sky they are now running MAP-T and starting the transition to IPv6 only.
- Semaphor 2y agoGermany, Vodafone. They support it, so I could get v6, but chances are that that'll switch me to CGNAT for v4, so I'm not willing to risk it.
- 2y ago
- dfboyd 2y agohttps://cr.yp.to/djbdns/ipv6mess.html https://cr.yp.to/djbdns/ipv6mess.html still as relevant as the day it was written
- Plasmoid 2y agoTime has not been kind to this article. It's basically a compete list of fallacies that people believe about ipv6.
- x3n0ph3n3 2y agoOh, is IPv6 now backwards compatible with IPv4? No? I guess not a complete list of fallacies.
- growse 2y agoI can route to v4 endpoints on my v6-only network just fine. Shrugs
- kortilla 2y agoThey aren’t compatible. There is a device in the middle doing a translation for you. That’s like saying HTTP can talk to FTP servers as long as there is an HTTP to FTP proxy. The only thing that makes them seem compatible is there is a well formed address space in v6 that clients send v4 requests to. But it’s still v6 and a 64 proxy needs to have an actual IPv4 address to translate the source to before sending it via v4 to the actual destination.
- growse 2y agoI'm aware there's a middle box. My point is that the middle box is a compatibility layer which, by definition, has the effect of enabling compatibility (at least in one direction). The usual "they should have designed it to be compatible" nonsense usually comes from the crowd with zero suggestions of how to have a 32-bit addressed device send to packets to something with an address outside its universe. Point is that djb was as wrong then as they are now.
- commandersaki 2y ago> This is the same as looking at a linear trend line placed over the data series used in Figure 1, looking for the date when this trend line reaches 100%. Using a least-squares best fit for this data set from January 2020 to the present day, and using a linear trend line, we can come up with Figure 2. > This exercise predicts that we’ll see completion of this transition in late 2045, or some 20 years into the future. Anyone willing to place a bet on this? > While the design of IPv6 consumed a lot of attention at the time, the concept of transition of the network from IPv4 to IPv6 did not. > Given the runaway adoption of IPv4, there was a naive expectation that IPv6 would similarly just take off, and there was no need to give the transition much thought. In the first phase, we would expect to see applications, hosts and networks adding support for IPv6 in addition to IPv4, transforming the internet into a dual stack environment. In the second phase we could then phase out support for IPv4. I really don't understand this, how do you not make a transition plan the #1 requirement for selecting the next IP. (But the article goes on to say...)
- kortilla 2y ago> Anyone willing to place a bet on this? Ill bet against it. The tail on this one is going to be super long. There are embedded systems today that are shipping in things expected to last 30 years with IPv4 only. The logistics of the bet are going to be hard. I do see a world where IPv6-only becomes the default for ISPs and IPv4 becomes an add-on you pay for either from your ISP or from another via a tunnel. Does that world mean v4 is dead yet?
- tialaramex 2y agoThe long tail doesn't matter. Once IPv4 traffic is a small fraction, the big transit providers will make it cost too much to bother with, and their customers (retail ISPs) will just cut it. Only global IPv4 matters. If in fifty years there's still a device that insists on speaking IPv4 with the address 10.20.30.40 that will still work and it still won't matter to the Internet any more than it does now. The appropriate comparison is leaded gasoline. In my country this was never formally banned. You can't buy a new car which consumes it of course, they banned that, but the fuel itself is legal and for a while enthusiasts would travel to a retailer which still sold it, there might be one in the next town, or the next. Of course with fewer customers the price went up, further reducing customers and squeezing more retailers out, soon enough you might have an hour's drive to buy fuel. The wholesalers were next, if you sell a tanker of ordinary unleaded every five minutes, and a tanker of "high performance" unleaded every hour, why bother making the leaded fuel that shifts only one tanker per week across the whole market? It's not even worth reconfiguring your mixers to make it. So you mark it "No longer available" and gradually across the market the retailers can't buy more and there is no more leaded gasoline. You can make your own leaded gasoline, but the volumes involved mean it no longer makes any meaningful difference, you could make your own lead paint too, if you're crazy, it doesn't make a noticeable difference to the world.
- vaylian 2y agoGitHub is still not accessible on the IPv6-only internet: https://isgithubipv6.live/ https://isgithubipv6.live/
- AStonesThrow 2y ago[flagged]
- mannyv 2y agoHe is always with us.
- blueflow 2y agoConsider codeberg.org as alternative: Has full IPv6 support, is not owned by Microsoft, does not force 2FA on its users and is a non-commercial enterprise.
- cls59 2y agoYup. GitHub alone killed my last effort to go all-in on IPv6 for my personal cloud. Sure, I could have hacked my way through it. But, that was more work than just paying the extra few cents a month for IPv4.
- kijin 2y agoI think the article's diagnosis is spot on. The urgency of IPv6 adoption was predicated on the assumption that every connected device, both server and client, needs a unique and stable IP address. Back when IPv6 was first discussed, you couldn't even host two HTTPS sites on the same IP/port combination! That was such a colossal waste of IP addresses. Another thing that changed on the server side was that, thanks to AWS and the like, it became trivial to set up a massive private network. Nowadays you can have a cluster of thousands of virtual machines that communicate with one another entirely within a VPC. Only machines that need to communicate with external entities get a public IPv4 address. This kind of setup not only frees up a /20, but also has the benefit of being more secure. Meanwhile, on the client side, the rise of mobile internet means that devices can no longer assume that it will have any given address for any length of time. Even if we had plenty of addresses to go around, like with IPv6, what can we do when the device moves across the country? It's easier to assign a new address than to try to route the old address to an entirely different ISP. Reducing the complexity of the routing table was one of the goals of IPv6, after all. Insisting on a unique and stable IP address for each mobile device would defeat that purpose. As a result, most new applications are being built with the assumption that the IP address doesn't matter. You rent a few ports on someone else's IP for a few minutes to fire off a bunch of requests, just like you'd rent CPU cycles on someone else's machine to run some functions.
- somat 2y agoit is unfortunate that tcp and ip are as interlocked as they are, by which I mean, there is no way to keep your tcp connection while swapping out the underlying ip addresses. This is not actually a real problem, we do just fine without it, it can be solved at higher or lower layers. But it would have been nice to have.
- kijin 2y agoYeah, it would have been nice to have, but that's all. Instead of requiring IPv6, the internet has evolved in a direction that tolerates disconnects and reduces its own IPv4 address consumption. It will probably work fine for the next 20 years at least. In the 19th century, New Yorkers worried that the city would soon be buried in horse shit because of increasing demand for transportation. The horse shit apocalypse never materialized, because transportation evolved in a way that stopped relying on horses. Now we have a different problem, of course.
- AdamH12113 2y agoI’ve often wondered if going with 64-bit addresses with a dotted quad hex notation would have eased the roll-out. I remember a lot of resistance when IPv6 was first announced along the lines of “I can’t memorize/type in giant addresses and I don’t want to have to use DHCP and DNS everywhere.” It felt like IPv6 never recovered from a bad first impression.
- growse 2y agoI'm not sure I've ever heard this view expressed by serious, competent network engineers. I have heard it a lot from the home hobbyist though, but I'm not sure how much that demographic matters in the grand scheme of things.
- chgs 2y agoThe vast majority of ip4 only networks are enterprise, that’s where I hear the complaints from. The people who say autoconf (dhcp etc) is bad and that dns is bad.
- nikanj 2y agoSerious, competent network engineers are not created in vacuum from platonic ideals and TCP fragments. They're home hobbyists who grew up hating ipv6, and won't magically learn it overnight when their previous networking guy quits and they get handed the keys to the server cage
- growse 2y agoThese people are neither competent nor serious. In the real world, people who design and operate large networks are the very same people who staffed the working groups who designed IPv6. It's their design.
- jiggawatts 2y agoA key aspect of IPv6 is that the address space is big enough that 'carving it up' for subnets is dramatically simpler even at the largest scales. You don't need to be frugal with network sizes, and you don't need central coordination to avoid conflicts. This is huge! E.g.: If I want to deploy a cloud VPC (or vNET), then I have to go find "the guy with the spreadsheet" and peel off a tiny(!) private IPv4 address space. If he's away from his desk or on holidays, my 1-minute automation script will now take 1-10 working days until he's back and responding to requests. With IPv6 this just disappears as a bottleneck.
- hairyplanter 2y agoI have fully implemented IPv6 in my home network. I have even implemented an IPv6-Only network. It fully works, including accessing IPv4 only websites like github.com via DNS64 and NAT64 at my router. The only practically useful thing about my IPv6 enabled network is that I can run globally routable services on my lan, without NAT port mapping. Of course, only if the client is also IPv6. Other than this one use case, IPv6 does nothing for me. It doesn't work from most hotels, nor from my work lan, nor many other places because most "managed" networks are IPv4 only. It works better at Cafes because they are "unmanaged" and IPv6 is enabled by the most common ISPs, like ATT and Comcast and their provided routers. Based on this experience, I think IPv6 is less valuable than us HN audience thinks it is. Private networks, NAT, Carrier Grade NAT are good enough, and internet really doesn't care about being completely peer-to-peer. I think the adoption rate reflects this--it's a linear growth curve over the last 25 years. It should have been exponential. I think cost of IPv4 reflects this--it is now below the peak, and has leveled off. As surprising as it seems, IPv4 exhaustion has not been a serious problem. Internet marches on. IPv6 is still a solution looking for a problem, and IPv4 exhaustion wasn't one of them.
- Dylan16807 2y agoNAT is mostly okay, but carrier grade NAT where you can't forward a port causes real problems. IPv4 exhaustion is a real problem, it's just not enough to motivate people much.
- saurik 2y agoHave you tried using PCP to forward the port? I was under the (maybe-incorrect, and if so I would really like to learn) impression that most major CG-NAT setups supported it.
- Dylan16807 2y agoI suppose I can try that some time. I can find absolutely zero mentions of that for the ISP, just the option of buying a static IP.
- 2y ago
- Uptrenda 2y agoThese charts that show IPv6 adoption really don't mean shit. The thing is: every single device out there isn't being used directly by a human bean (and a real hero.) They include things like sensors, smart lights, fridges, washing machines, a huge huge number of mobile devices, company networks, ... apparently even tooth brushes? Look at another sector and the story is ((quite horrible.)) I'm talking a regular fixed home network. Start by looking at routers for IPv6 support. And what do you see? Total crap across the board. Here's some of the issues I've seen. Routers that have no IPv6 support (common for ISP provided routers.) Routers that have NO FIREWALL for IPv6. Routers that crash every 3 minutes after assigning an address. Routers that don't support the exact combination of network details to setup IPv6 on your network (there are multiple ways to deploy IPv6.) What about if you want to use features like UPnP with IPv6 (something that would probably be useful for some software given that IPv6 is supposed to give you public addresses but firewall it on the router.) What I've found is there's really just one UPnP library that every router uses even though it sucks. miniupnpd. This is a library that can barely manage to handle different types of addresses. It's really a mixed bag whether an IPv6 firmware will have miniupnpd enabled and if its built for IPv6 (and if anyone bothered to test it.) The odds go down dramatically. If you manage to get a router with IPv6 at home working alongside other useful Internet standards made for it (since 2010) color me impressed. You probably buy a lottery ticket at that point. Because if testing IPv6 deployments for the past 2 years has taught me anything: its that no one really cares about this shit. Present day, present time. You still hear people telling others to turn IPv6 off for some vague reason ('security', 'bad', 'problems.') These people don't really have a clue. It's all just a massive cope because they tried to get it to work and failed. And after the shit I've said I can't say I blame them. But I also want to note that their conclusions are BS.
- brnt 2y ago> They include things like sensors, smart lights, fridges, washing machines, Now you gave me an excellent reason to make my home network v6-only.
- jeroenhd 2y agoAll routers I've ever encountered have a default deny rule for IPv6, replicating the port forwarding setup people have come to expect from NAT. Except you can use multiple Xboxes in the same network now, of course. Even the mini router I bought for 15 bucks five years ago does IPv6 addressing just fine. Just announcing a prefix (or two, local network stuff over ULAs and all that) is enough to make SLAAC do its thing. Never had any problem with DHCPv6 PD for automatic subnetting either. I haven't looked into UPnP on IPv6 much, but the ones that did UPnP all seem to do IPv6 fine after 2015 or so. I usually turn it off because I don't want random crap manage my firewall unauthenticated (and many router manufacturers have had vulnerable implementations that would accept UPnP packets from the internet so screw that). Brands that I've successfully used IPv6 with without any hassle include TP-Link, D-Link (don't buy from them), AVM, Mikrotik, and Netgear. The most annoying part I find about routers is actually that they don't let you disable ALGs anymore it seems. Every few years Samy Kamkar writes up a way to bypass most IPv4 firewalls by abusing the hackery we've accumulated around NAT and the easiest fix ("let FTP/SIP/H363/PPTP be broken on IPv4") doesn't seem to come with routers anymore. It took a while, but router manufacturers seem to have realised that the world is moving towards "CGNAT or IPv6" and not having usable IPv6 breaks networks in those cases. The most broken IPv6 deployments I've seen were from people who tried to turn it off though weird hacks like firewall rules which subsequently got IPv6 from their ISP. Had they actually disabled IPv6 they would've just been stuck OK IPv4 like regular, but their weird hacks made half the TCP connections need to time out before they could access the internet.
- kalleboo 2y agoThe internet stopped being a network of peers where everyone needed an address and is now a split into producers (a handful of large companies) and consumers (everyone else). The consumers are not expected to need a public address where they can be reached - in fact, having a public address is actually a security and privacy risk.
- redprince 2y agoThat was in fact one of the promises of IPv6: Restore the network of peers where every host is in principle a server and a client and communication between peers is unhindered unless a policy is enforced saying otherwise (on the machine, on a firewall, etc.). > having a public address is actually a security and privacy risk. Services can be turned off or a firewall instructed not to pass traffic from the internet (by default). That represents exactly the same attack surface as having a service enabled and nobody being able to get to it from the internet because of NAT. The privacy risk is mitigated by RFC4941 "Privacy Extensions for Stateless Address Autoconfiguration in IPv6". Granted that does not deal with the (delegated) prefix staying the same and when there are only one or very few users in that prefix, some individual behavior could be inferred. Because of that at least in Germany we have the peculiar horror of getting the IPv6 address and all delegated prefixes changed on every redial. That eliminates all privacy concerns while also continuing to make residential internet connections useless for hosting any services. Anyway. The internet is already way down the road of functioning only as the delivery conduit for a few cloud / service providers mediating all user communication and access to content.
- Affric 2y ago> in Germany we have the peculiar horror of getting the IPv6 address and all delegated prefixes changed on every redial. This is oh so very German. In normal times it is massively overkill. I have to wonder if, heaven forbid, the things these sort of German things are meant to mitigate come to pass again if they will make any difference or if they are a largely symbolic act designed to demonstrate ideological opposition to such things.
- 2y ago
- Animats 2y agoChina's IPv6 transition is 74% complete.[1] Conversion to IPv6 was specifically called out in China's 14th Five Year Plan, which gives the goal high visibility within the government and the Party. Conversion is quite far along. The current goal is everything IPv6 enabled by 2025, IPv4 turns off in 2030. 99% of the top 100 mobile applications in China are on IPv6. China Mobile's backbone is now IPv6 only. [1] https://www.china-ipv6.cn/#/ https://www.china-ipv6.cn/#/
- abhinavk 2y agoIndia is also around 75%. Both of them cover quite a bit of humanity. The regions where growth is going to happen don't own a lot of blocks so they will focus on IPv6.
- throw0101c 2y agoVietnam (pop. 98M) has mandated moving to IPv6, with goals for migration between 2025 and 2030: * https://www.theregister.com/2024/10/14/vietnam_digital_infrastructure_policy/ https://www.theregister.com/2024/10/14/vietnam_digital_infra...
- jiggawatts 2y agoMeanwhile in Australia I called my ISP to enable IPv6 and they asked me to justify why I needed it. Because "it's the Internet" and has been a standard since the year 2000 doesn't seem to be sufficient reason to bother...
- bigstrat2003 2y agoThat is a wild response to give a customer. I'm surprised they are still in business if that's how they treat fairly reasonable customer requests.
- wmf 2y agoYeah, a normal ISP would just say "we don't have it".
- imaguska1 2y agoAll big German internet providers (DTAG, Telefonica, 1&1, Vodafone) are IPv6 Dual Stack or CGNAT'ed for many many years now. Same for all mobile providers. So everybody is using IPv6 in their home networks without problems.
- Semaphor 2y agoLegacy account on Vodafone (from Kabel Deutschland days), no v6, no CGNAT.
- Kelteseth 2y agoOur local German teledata internet provider uses CGNAT, and it is a mess of random timeouts.
- kalleboo 2y agoI could see that that's how IPv6 adoption happens. ISPs realize that selling their old squatted IPv4s to Amazon/Google/Azure more than pays for the transition to IPv6 + CGNAT with a tidy profit on the side. Then to save more money, they cheap out on the CGNAT so that IPv4 connections have poor performance. Customers complain to the slow websites (since google/cloudflare sites all load quickly, it must be the site's fault) and they have to adopt IPv6 for that reason.
- v20 2y agoVodafone refused to enable dual stack on my DSL connection. I got to pick from either keeping dual stack with CGNAT or completely disabling IPv6 but get a reachable IPv4. My mobile provider doesn't allow IPv6 connections. So ironically, to be reachable from everywhere, I had to turn off IPv6.
- froggerexpert 2y agoIn spite of its wider adoption issues, it's valuable for my personal infrastructure: each of my services/machine has an IPv6 globally routable address. Why bother, when I could just do TLS SNI reverse proxying via nginx? * Some services don't use TLS, or even TCP. * A reverse proxy is yet another intermediary in the chain. * Plain IPv6 routing is simpler than reverse proxying, and I already need a network layer anyway. There are downsides: * some software doesn't support IPv6. I haven't experienced this on the Linux servers I run. * in a dual stack network, now you have two networks! I use NAT64/PREF64 like https://labs.ripe.net/author/ondrej_caletka_1/deploying-ipv6-mostly-access-networks/ https://labs.ripe.net/author/ondrej_caletka_1/deploying-ipv6... to have most clients only be on IPv6. They get IPv4 connectivity over IPv6 via NAT64. * If I'm in another country then I often don't have IPv6 connectivity. In this case I use any VPN that offers IPv6 (and have one available via my home, via Wireguard). * Learning IPv6 takes time, but not much. It's one-off. It's not more complex than IPv4, but it is different. If anything, it's simpler. (SLAAC rather than DHCPv4; IP reachability rather than NAT/port forwarding).
- kjuulh 2y agoI'd like to use ipv6, if only to avoid having to pay for an ipv4 address for some private vpcs (with public address for reasons). I remember having issues with fly.io as well, because they're ipv6 by default if I remember correctly. Currently Denmark has worse support than I expected: > Liste over danske udbydere (List of Danish providers) > Internetudbydere på listen: 41 (ISPs on the list) > Internetudbydere med fuld IPv6-understøttelse: 17 (41%) (ISPs with full IPv6) > Internetudbydere med delvis IPv6-understøttelse: 10 (24%) (ISPs with partial IPv6) > Internetudbydere uden IPv6-understøttelse: 14 (34%) (ISPs with no IPv6) source: https://ipv6-adresse.dk/ https://ipv6-adresse.dk/
- shmerl 2y agoIt's ridiculous how slowly it goes.
- uobytx2 2y agoPeople posting have mentioned that IPv4 is working for what they use the internet for. But of course it is. When NATs has been required for your whole life, how could the internet have built features that needed p2p routing? Just convince businesses to build something that requires special router configuration? And still wouldn’t work on phones or with ISPs that require CG NAT? You got what worked out of the box. You obviously couldn’t use what didn’t exist.
- theamk 2y agoWhy do people assume IPv6 means "easy p2p"? Even if NAT will be gone one day, the stateful firewalls won't. Every every home router would still ship with "deny all incoming" by default, and every corporate network would have the same setting as well. Same as IPv4, IPv6 serving would still need registration with border device, either manual by user, or via UPnP-equivalent.
- numpad0 2y ago"everything gets a global IP, no more NAT headaches" was one of marketing talking points for IPv6. Not necessarily the case nor welcomed by everyone, but that was the intent.
- mike_d 2y agoWide scale deployment of NAT (the "home router" that allowed you to connect multiple devices) was the greatest leap in internet security we ever made. I remember the days when we had "everything gets a global IP," and we do NOT want to go back to that. Look up Conficker, Code Red, Blaster, etc. People naively assume the large IPv6 address space somehow hides your computer on the internet. That isn't true. Both because v6 host discovery is a solved-ish problem for attackers, and worms have near unlimited resources to throw at the wall.
- bigstrat2003 2y agoI remember those days too. They had nothing to do with computers not being behind a NAT.
- nemetroid 2y agoIf the US had the same IPv4 scarcity as the rest of the world (specifically, if major US ISPs were using CGNAT), the IPv6 transition would be happening much faster.
- freeone3000 2y agoThe addresses were allocated equally geographically, and then sold. The US will hit ipv4 scarcity when the US stops being the richest country.
- WorldMaker 2y agoPrior to the establishment of the RIRs (Regional Internet Registries) the IANA handled IPv4 allocations directly and without regard for geography. During that time most of the early adopters with US government, US Universities, and US Corporations. Several US Universities and Corporations (for easy examples, GE and MIT) simply asked early enough for IP addresses and got entire /8 allocations. Sure, when the RIRs were built they were assigned roughly equal shares of the remainder of IPv4 space, but it certainly failed to account for those early years of early adopter allocations, which did accidentally favor the US heavily.
- Hilift 2y agoThat's probably true for consumers. For large, global corporations, IPv6 is a million miles away. I've worked with several, and they all have poorly managed kit, vulnerabilities everywhere, poor documentation/diagrams, poor performance, millions of firewall rules, tons of vendors to connect with, outsourced wireless vendors, remote access solutions that are a byzantine security mess, ... IPv6 is suicidal for most large organizations beyond ok we can speak IPv6 for a small part of the infrastructure. Add to this the recent deluge of VPNs everywhere (probably due to WireGuard) and container networking, IPv6 would be a recipe for disaster. Security is difficult in this scenario, in part due to the people implementing this stuff don't have a good handle on what they are doing.
- WarOnPrivacy 2y agoFiber providers here are incapable of providing IPv6. Frontier, Optyx, Sumo, Evolution, Intellipop, Starlight, Legacy, Yandoo, Voonami, Infinity all serve this area. Zero have IPv6.
- briffle 2y agoShould probably clarify the location of ‘here’
- WarOnPrivacy 2y agoDoes that change the point of the discussion? Because all of those ISPs are in multiple markets. The point being that ISPs remain a primary stall-point of IPv6 adoption. There is eagerness to hand-wave that away - and that is part of the reason IPv6 stays underdeployed.
- xescure 2y agoI’ve never heard of any of those.
- TacticalCoder 2y agoOne of my biggest issue is: how do you even detect exfil when ICMP is mandatory in IPv6 for the other protocols to even just work? IPv6 looks so Rube-Goldbergy to my eyes that if I squint just a little tiny bit and put a very thin thinfoil hat on, I could nearly swear this complexity is there by design. For example so backdoors allowing exfil through ICMP are impossible to detect. IPv6 is chatty. So chatty. There are networks where a single unaccounted for packet means something abnormal is going on (and at the very least requires enquiry): how does that work with IPv6? An issue with these big design-by-committee thinggies is that often one or two in the committees are little rats working for the man.
- kstrauser 2y agoICMP is required for IPv4 to work correctly, too. It's often completely blocked by cargo culting net admins who then wonder why their things fail that ICMP would have fixed.
- jiggawatts 2y agoI have a laundry list of issues like this: Firewalls stopped sending RST packets (or any other kind of error) by default on all ports more than a decade ago. This is great for Internet-facing security, but has converted from easily diagnosed instant failures on internal networks to 30 second timeouts... which are indistinguishable from "host is down". Don't worry! Just ping the host... err... can't do that either because of overly paranoid admins like you mentioned. Next, spend a week trying to figure out why packets seem to go only one way through a cloud VPN only to discover that Path MTU Discovery uses ICMP and without which VPNs are basically broken. Fun.
- thayne 2y agoMy ISP is only couple years old. And yet, surprisingly to me, they don't support IPv6, only ipv4.
- gosub100 2y agoPardon if this is an ignorant question, but could the "backhaul providers" help expedite v6 by simply adding a small-but-annoying tax on carrying v4 traffic? I know it sounds ridiculous to want to pay more, but it might help "rip the band-aid" off if, in order to keep costs down, ISPs had to pay a little more for the deprecated protocol.
- skywhopper 2y agoThe premise is completely wrong here. IPv6 is not just an “incremental change” that would have represented an easy uptake. Instead, pretty much every practical detail of existing IPv4 infrastructure, both hardware and software, was broken. Massive swaths of extra management and security tools were rendered useless. It was a massive miscalculation. In the meantime, we figured out how to make things work without the extra address space. And the dream of a point-to-point Internet turned out to be a terrible idea after all. IPv6 pushers love to hate on NAT, but it’s actually a really good design choice that’s fundamental to basic network security.
- xvilka 2y agoNAT doesn't ever provide security, only pretending to.
- iso8859-1 2y agoWhy is there a difference in captcha exposure between IPv4 and IPv6 then? Maybe there is no actual security, but the people deploying these captchas seem to think there is a need to deploy them for IPv6 users.
- einsteinx2 2y agoI’ve seen this sentiment repeated over and over in this thread without a single explanation. Please explain how NAT on IPv4, as used in practice, does not increase security vs connecting machines each directly to a publicly accessible Internet address? I’m having a hard time understanding how this statement can possible be true.
- xvilka 2y agoHere is the very simple but practical explanation why: https://0day.work/an-example-why-nat-is-not-security/ https://0day.work/an-example-why-nat-is-not-security/ And more high-level explanation as well: https://www.f5.com/resources/white-papers/the-myth-of-network-address-translation-as-security https://www.f5.com/resources/white-papers/the-myth-of-networ...
- tptacek 2y agoThe original “end-to-end” architecture of the Internet assumed that every device was uniquely addressed with its own IP address [...] That may indeed have been an assumption of the original architecture, but it's orthogonal to the end-to-end argument in Internet design, which is about moving logic out of the network entirely and into applications (more precisely, about recognizing that the boundary between network and application is productively debatable, and had, up to the point where Saltzer and Clark and Reed wrote the paper, been defaulting too much towards the network). An end-to-end-architected networking application can be oblivious to its addressing, or even the network layer below it. If anything, my intuition is that the unreasonable effectiveness of CGNAT --- which is exactly what Huston is writing about --- is strong evidence that the end-to-end paper was deeply correct.
- akira2501 2y agoIsn't the encoded assumption here is that clients rarely act as servers? This may be either because that's outside the typical use case or because providers explicitly do not want them to, but this factor is the reason CGNAT can be viewed as "effective."
- tptacek 2y agoEnd-user retail endpoints can still act as servers, but the way you have them to that in 2024 is different (and yes, more complicated) than it was in 1996.
- Schnitz 2y agoAsus routers still ship with IPv6 disabled by default, to this day. It makes perfect business sense, as everything still works just as well with v4 but single stack is less complexity so less support costs, etc. I’ve been running my home LAN dual stack for close to a decade, so I have native v6, but then on the other hand I ignore it for my networking stuff, ie I only set an A record in my dynamic DNS and never bothered figuring out how to make phoning home from other networks work over v6. It’s just not a priority and my lack of deep v6 knowledge would make it likely less secure.
- rr808 2y agoWhen AWS started charging for IPv4 addresses I started switching to IPv6. I spent a few days getting it all up and running. I thought it was OK but my router kept crashing every day, then I noticed I can't get working from some places like my office. Gave up, never again its just not worth it. I moved to another hosting service that didn't charge.
- pmarreck 2y agoIs it possible that the problems came about because you were running dual networks and not IPv6-only? > Gave up, never again its just not worth it. Maybe when you upgrade your router to one that cares about IPv6 it will work. Never say never. Also... > I moved to another hosting service that didn't charge. That's not going to last. The price of having an IPv4 address must go up over time since demand will continue to increase and it will (already is at some places such as Hetzner and other managed hosts) cost more than IPv6 which is usually a free address.
- cullumsmith 2y agoFor my entire life, the networking nerds have been shaming us for not using IPv6. Back when I had a NeoPet in middle school, IPv6 was was "just around the corner." I'm now raising my own children and still listening to the same IPv6 talking points. Every company I've ever worked for has completely disabled IPv6 on the corporate network. My own ISP still doesn't offer it. Disabling it is often the quickest fix for a variety of networking issues. At some point we must admit failure. There is no conspiracy to limit IPv6 adoption. If the technology was truly useful, you'd see far more in our profession advocate for it.
- orangeboats 2y ago> Disabling it is often the quickest fix for a variety of networking issues. In a way, you disabling it now is the reason why others are disabling it later. A lot of IPv6 deployment issues are precisely caused by middleboxes/clients disabling or misconfiguring it.
- otabdeveloper4 2y agoYes, and? Don't make excuses for shitty technology. The mental model of what the "future Internet" (aka the one we're using now) would look like is completely insane in IPv6.
- orangeboats 2y agoI am saying a lot of "IPv6 issues" are not because of the protocol itself, but rather it is self-inflicted pain. You quickly assuming IPv6 is a "shitty technology" means that you are part of the problem. Congratulations, you just proved my point. >the one we're using now The one we are using now is held by a bandaid. It's insane that, for me to connect to other computer, I need a middleman (STUN or other coordination services) to help me with it.
- otabdeveloper4 2y ago> It's insane that, for me to connect to other computer, I need a middleman It's not insane, it's the default and correct assumption. I certainly don't want random computers connecting to mine just because they want to. STUN is a shitty solution to this problem, but IPv6 doesn't provide any solution at all, so a shitty solution wins here. Sorry.
- dopylitty 2y agoI gotta say don't sleep on this article thinking it's just another article about IPv6 adoption stats. There's a lot of interesting thought in the second half about what the Internet fundamentally is and where it's going. The author argues that the use of TLS and SNI has fundamentally changed the internet from a number based routing network to a network based on DNS names and SNI where the numbers involved don't really matter anymore. > Where is this heading in the longer term? We are pushing everything out of the network and over to applications. Transmission infrastructure is becoming an abundant commodity. Network sharing technology (multiplexing) is decreasingly relevant. We have so much network and computing resources that we no longer have to bring consumers to service delivery points. Instead, we are bringing services towards consumers and using the content frameworks to replicate servers and services With so much computing and storage the application is becoming the service, rather than just a window to a remotely operated service.
- Peteragain 2y agoYes, I read the article as well! I'd still love to have a dedicated IP address associated to the house so I didn't need a contract to dish up a blog & photos for my 3 friends. I'm sure P2P would make it much harder to extract money from people.
- cyberax 2y agoIPv6 is _still_ not at the feature parity with IPv4! I'm not kidding. For example, Android doesn't support stateful DHCPv6. And DHCPv6 doesn't have the _basic_ feature of DHCPv4: hostnames. You can't easily use it to do a quick survey of your network. Then you have that @#&(^(&!@^ that is ULA. With IPv4 we have a very useful pattern: you create an "internal" network that is stable and predictable. It's routed to the outside world through NAT. If the external connection goes down, the internal network is unaffected. With IPv6 you're supposed to have ULA and the global routed addresses in parallel. So now the external connection goes down, and the router withdraws the prefix from the router advertisement. Half of the hosts lose their external addresses, but keep the ULAs. Half of the hosts don't implement prefix withdrawal, and keep both their ULAs and the normal addresses. Congrats, now these hosts can't talk to each other due to the ULA addresses being less preferred. And of course, IPv6 hasn't improved on the PMTU. So if you're running an Internet service, you need to use something like 1400 MTU to make sure some of the misconfigured tunneled clients don't get shafted. There's now an RFC that makes it useful: https://datatracker.ietf.org/doc/html/rfc9268 https://datatracker.ietf.org/doc/html/rfc9268 , but it's Experimental and it'll need ~20 years to be deployed anyways. IPv6, a story of recursive utter failure at all levels...
- matrix2003 2y ago> Congrats, now these hosts can't talk to each other due to the ULA addresses being less preferred. What do you mean by this? Are you taking about mDNS still referencing the withdrawn prefix?
- cyberax 2y agoIf two hosts have both mutually accessible ULA and GUA addresses, they will prefer _GUAs_ to talk to each other. So the connection will be susceptible to the prefix withdrawal if the upstream goes down (BTW, IPv6 did nothing sane for multihoming either). > Are you taking about mDNS still referencing the withdrawn prefix? That too.
- matrix2003 2y ago
- pie_flavor 2y agoI have IPv6 disabled on my computer because it solves many mysterious service interruptions. Comcast claims to support it, but there have been many times when IPv6 was dog slow and IPv4 was very fast.
- dpkirchner 2y agoComcast used to issue me an IPv6 block but silently stopped at some point. Others reported the same problem. Thankfully everything I use still supports IPv4 so I didn't notice until I went looking. One day it'll be worth my time to figure out the problem, but I predict that day is far in the future.
- AStonesThrow 2y agoMy ISP has given me a quite stable /64 network that's lasted for months and months. I am curious though: my IPv6 network begins with 2600::, which I feel is not an accident or mere coincidence. For a long time, Facebook would never "trust" my device, and I suspected it was because of the IPv6 thing. Now, "2600" is actually a hex number and doesn't mean 2600 decimal, but 2600 is an interesting prefix for a stable address. Could it mean that my ISP has permanently branded me as some sort of "hacker", and "2600" is network admin code for "please don't trust these devices"? We should compare notes and see if other HN users have come up with stable prefixes like this, or different prefixes that aren't "2600".
- kevvok 2y agoAccording to the IANA assignment list, 2600::/12 is assognrd to ARIN. https://www.iana.org/assignments/ipv6-unicast-address-assignments/ipv6-unicast-address-assignments.xhtml https://www.iana.org/assignments/ipv6-unicast-address-assign...
- AStonesThrow 2y agoYes, that's correct -- I'm in the USA, and not in Europe or Africa. What is your point with this? ARIN has, of course, delegated my assigned IPv6 network to my ISP; you do realize that this is SOP for ARIN?
- kevvok 2y agoThe point was a prefix from 2600::/16 isn’t special; it’s just from one of the blocks assigned to ARIN. One ISP I know of with an allocation in that range is Verizon, which announces a number of prefixes over BGP in 2600:1000::/24
- AStonesThrow 2y agoUhm, anyone with an ISP in the United States is going to have a block delegated from ARIN. That's the whole point of ARIN, isn't it? Nothing they delegate is inherently special, because ARIN administers all of the allocations for their region. I'm saying that perhaps the 2600::/16 delegation is especially reserved for a certain class of user in order to tag us as something. Surely, my own ISP holds more delegations than that slice alone. It's certainly standing out like a sore thumb to anyone analyzing logs. As I said, it can't be merely a coincidence. Interestingly, I also subscribe to mobile voice/data service from the same ISP, and activating mobile data here at home gives me, sure enough, another 2600::* delegation.
- xvilka 2y agoGitHub and Microsoft Azure still aren't IPv6-ready.
- jiggawatts 2y agoAzure is... getting there. Slowly. The Portal now loads for me on IPv6, which then blocks me from accessing certain PaaS resources because they only work with IPv4 rules in their firewalls. Speaking of which, it grinds me gears that every Azure PaaS service implements firewall rules in a unique and special way. The syntax is different, the parameters are different, the capabilities are different, and the output logs are also incompatible just for extra fun.
- jakeogh 2y agoIPv4 is valuable, there are reasons to not be able to uniquely id/tag/censor every endpoint. It's much harder to block a country than a user.
- camgunz 2y agoI'm pretty naive about this stuff, but IMO IPv6 is a lot more empowering than v4. You aren't dependent on some owner of v4 addresses for access, you don't need to manage--and aren't forced into--NAT, and you (probably) get to use all of your ports. My conspiracy theories about why v6 hasn't taken off are: people make money off v4 leases, and email spam blacklists become pretty useless in v6. But again, very naive here.
- wakeupcall 2y agoThe more likely reality is that we have a lot of v4-only hw in place with lifespan of 20+ years. Those devices won't go away. Heck, I work on embedded, and having a dual-stack system is just a PITA to deal with. If v6 would have been fully retro-compatible this wouldn't have been something to think about, but you can't drop v4 and there's no future in sight where v6 will be the only choice (we'll have dual-stack for a looooong time), so we just push the problem up the chain. There are plenty of systems being developed _now_ which are still v4 only as a result.
- camgunz 2y agoTotally agree. I'm a little embarrassed by it tbh; to me it feels like a big failure of nerd governance. We should be able to manage this, but I think we're pretty close to having to admit that we can't.
- SmartHypercube 2y agoI've always wanted to give IPv6 more chances to see if I can take advantage of its features early, but every attempt has left me very disappointed. Issues I noticed during my recent research: - GitHub does not support IPv6. - Docker containers do not have IPv6 by default. - Many programs default to listening on 0.0.0.0 or 127.0.0.1 when they start, which means they only listen on IPv4. On Linux, listening on :: defaults to listening on both IPv4 and IPv6 simultaneously, but few programs do this. Python asyncio even disabled this feature[1]. - I've always heard that using IPv6 can sometimes lead to high latency or low bandwidth on certain websites, or even resource loading failures. Why isn’t there a convenient tool to compare these differences? It would be great if browsers could switch between IPv4-only, IPv6-only, and dual-stack modes. I’d like to seriously compare the effects on some websites rather than being silently affected. - Two large ISPs, Hurricane Electric and Cogent, do not have IPv6 peering[2], so they are not interconnected, and many other ISPs have similar issues. - Very few VPS providers offer /64 IPv6 addresses, which would allow different containers to be assigned freely within a machine. Some only provide a single /128, while others offer very few addresses per machine. - Many people might only know how to use iptables/nftables for firewalls and forget about IPv6, leading to situations where using IPv6 can bypass the firewall. I’m not talking about issues caused by the lack of NAT (NAT is not a good firewall!), but more generally about cases where you want to disable forwarding between two network interfaces. I stumbled upon two old posts that I found quite amusing: In 2011, someone said[3] “It's not terribly useful to have IPv6 only websites at the moment. Check back in 5-10 years though ;)” In 2014, someone said[4] “The Internet is growing really fast, in a few years, the IPv6 network will be bigger than IPv4, so, with IPv4, you'll be out of the real Internet. Go ahead man! Upgrade your IP!! Change is a good thing.” [1]: https://github.com/python/cpython/blob/5f5c0b9c23238dc0a1fdb764f625ae0cc5604519/Lib/asyncio/base_events.py#L1587-L1589 https://github.com/python/cpython/blob/5f5c0b9c23238dc0a1fdb... [2]: https://adminhacks.com/broken-IPv6.html https://adminhacks.com/broken-IPv6.html [3]: https://www.reddit.com/r/ipv6/comments/gnh69/what_ipv6only_web_sites_do_you_know_of/ https://www.reddit.com/r/ipv6/comments/gnh69/what_ipv6only_w... [4]: https://askubuntu.com/questions/309461/how-to-disable-ipv6-permanently https://askubuntu.com/questions/309461/how-to-disable-ipv6-p...
- billpg 2y agoI'd be convinced that IPv6 is done when large companies deploy servers on IPv6 only without an IPv4 fall-back.
- rwmj 2y ago> The rather bizarre economics of financing 3G infrastructure meant that dual stack infrastructure in a 3G platform was impractical, so IPv4 was used to support the first wave of mobile services. What's he referring to here?
- johnisgood 2y agoThis may be a random question, but do any of you have a working code (preferably C or Lua, without regexes but with regexes works too) for: 1) checking if a given string is a valid IPv6 address, and 2) checking if this IPv6 address is in the range? It should handle both IPv4 and IPv6. It must handle edge cases (number of chunks being 8, numbers must be less than 65535 if I am correct, then there is some stuff regarding ":::", etc.). There seemed to be too many edge cases, but maybe I was wrong. The range check should be in the form of "isIPInRange(ip, cidr)", e.g. isIPInRange("192.168.0.255", "192.168.0.0/24"). It is trivial for IPv4, but not so trivial for IPv6. If you are wondering why I am not asking LLM this, that is because when (at the time) I did attempt, it failed spectacularly, plus hey, it is HN, someone may find it useful and the more eyes the better anyways (to spot bugs, issues, what have you).
- alwayslikethis 2y agoYou probably just shouldn't try to do string matching here and just use one of the conversion function to get them to binary, apply the mask, and see if they match
- ianburrell 2y agoIPv4 has problems with the non-standard formats that use octal or combine octets. Like 192.168.1 is 192.168.0.1, 127.0.0.1 is 127.1.
- muhammadn 2y agoThe last few parts of this article reminds me of what i had been working on for the past few years. It's called "Named-Data Network".
- kyledrake 2y ago> The design of IPv6 was intentionally very conservative. To a first level of approximation IPv6 is simply “IPv4 with bigger addresses”. I don't agree with this take. I think it's actually quite a bit more complex, and this is a large part of the reason adoption has been slow. In retrospect, I think it would have been better off in practice to just literally extend the size of IPv4 addresses, and make it as simple as converting all IPv4 systems to hold a larger address.
- James_K 2y agoI feel like the hard part there is actually accessing all the IPv4 systems to change how they handle addresses. I don't know the full scope of difference, but I feel like once you can do a software update to all of your devices, the cost of increased complexity in protocol would be relatively constant between a minimal and actual v6. You are just pushing different data through the update.
- TabTwo 2y agoAs long as you have enterprise products like zscaler, that do not support IPv6. Or switches and routers that are broken in different ways with every update. Userproperties in Active Directory that are to short to insert an IPv6 address. Why should any enterprise company move to it? Why should any enterprise (at least) double the cost by having to support two protocols when most problems can be solved by various types of NAT?
- sebazzz 2y ago> As long as you have enterprise products like zscaler, that do not support IPv6 ZScaler is a burning piece of privacy-violating garbage that as a developer rather get rid of than have. Nice for non-IT collegues who were previously protected by the corporate proxy server while working in the office, now work at home or other places, and are prone to scamming and visiting forbidden [by the employer] sites. As a developer a system-wide MITM SSL-decrypting proxy server is a major pain in the ass. Every runtime of developer tools, python, Node, .NET, Docker, Linux (WSL) flavors, etc have their own way to trust root certificates, and as a web developer you do tend to touch a lot of different tools. Secondly, when you do a bit of devops, you can't even check basic things like checking if a website has the correct (valid) SSL certificate without RDP-ing to some server which doesn't have ZScaler installed. Sorry for my rant. But I'm not allowed to disable ZScaler - but am forced to live with it.
- aidenn0 2y agoI'll admit that while I run dual-stack for the public internet, I still haven't figured out a good way to manage my LAN with ipv6. For ipv4, I have a DHCP server on the same machine as my DNSH server, which lets me configure my network in a single place. With IPv6 I'm still not sure exactly how to configure this. It seems like if I use SLAAC for a ULA, at least some hosts will still apply RFC 4941 (or maybe 8981; I'm not sure), which makes DNS unfeasible. So I guess maybe DHCPv6 is the answer (short of manually configuring each host)?
- Dagonfly 2y agoMost hosts will generate both a stable and a temporary address when using SLAAC. The temporary address will be used for outbound traffic but the stable address will accept incoming traffic. So there usually is a stable ULA or link-local that you can put in a local DNS AAAA record. The PITA is that many services prefer GUA over ULA if available and don't gradually fall back to ULA if the WAN goes down. And you will still need dynDNS to VPN into your network because ISPs are allergic to stable IPv6 prefixes.
- deleted 2y ago[deleted]
- pwarner 2y agoAnycast and SNI mean someone like cloud flare only needs one IPv4 for their entire public facing service? Is that the gist? Obviously I exaggerate but I think that's their point?