71–80 of 107 posts
Earlier quoted context omitted.
What CDNs don't support IPv6?
At this point most of them do, but also require customers to explicitly opt-in. I think cloudflare is the only exception there, it won't even let you opt out unless you're on a paid plan.
kinda ironic how this paints ipv4-only with a premium flair
IPv6 has barely a carrot and no stick. Does anyone give me more money for using IPv6? Sure I might be able to save some money by not using IPv4 but that is rare. Government doesn't incentivize it. Ad networks don't either. There is very little penalty (financial or otherwise) for not going to IPv6. IPv6 will not happen until those sticks and carrots get bigger.
Just now on the frontpage also: a link to Hetzner's announcement of v4 address prices. Stick is coming on the hosting side.
What gets bundled and what doesn't is somewhat† a matter of company preference. And once IPv4 exhaustion was on the horizon, charging IPv4 separately made a lot of sense yet very few providers did it.
† The EU hates "hidden fees". If your product claims to cost €100 but actually there's no way to only buy the €100 product, you need "delivery" for €25 more because there's no practical way to avoid getting it delivered - that's not legal. Likewise if you claim it costs €100 but there's no way to pay cash, and all card payments have a 5% surcharge, you're going to either have to eat that surcharge, or advertise the price including the card surcharge.
Can someone explain to me what does IPv6 offer that's IPv4 doesn't? Apart from way more addresses. A good article would suffice.
My own connectivity at home doesn't support v6 due to my ISP. At work, v6 is so badly managed it's the first thing we rule out when diagnosing connectivity issues.
Kind of a sad state really. I wish v4 prices increased tenfold, not barely double.
It seems this site relies on a check for the domains' AAAA records to see if they support IPv6. Doesn't have anything to do with IPv6 in the products/apps that those sites offer.
AAAA records are necessary for that to happen.
I will start thinking about supporting IPv6 when Docker supports it out of the box. Hopefully, then I can test an individual application by running it in a container with "docker run -p [::1]:80:80 ...". I don't want to go down the rabbit hole of fiddling with the docker demon and setting up a custom network.
IPv6 has barely a carrot and no stick. Does anyone give me more money for using IPv6? Sure I might be able to save some money by not using IPv4 but that is rare. Government doesn't incentivize it. Ad networks don't either. There is very little penalty (financial or otherwise) for not going to IPv6. IPv6 will not happen until those sticks and carrots get bigger.
Kind of, IPv6 addresses are cheaper than IPv4 addresses, so you'll save some money at least.
> There is very little penalty (financial or otherwise) for not going to IPv6.
Soon you're not gonna have a choice. Better to prepared for when that happens.
Earlier quoted context omitted.
> A good article would suffice. https://en.wikipedia.org/wiki/IPv6#Main_features
None of that is actually true though? > It simplifies aspects of address configuration I assume this is referring to SLAAC? SLAAC is...fine. Most managed networks will want the extra control offered by DHCP though and DHCPv6 is currently in a much much worse state than DHCPv4. Also a single interface having at least 2, usually 3 or more (link-local, autogenerated, privacy) v6 addresses on the network is definitely no…
1) Ability to get a personal prefix as a private individual or a small company (not a LIR or LIR-sponsored)
2) Ability to use that prefix with any ISP I choose - similar to how a consumer can migrate their cellphone number to a different provider.
3) RFC 6275 actually implemented
There are other bits and pieces, but I believe if these with 3 things were done, IPv6 would actually have a "killer app" which would make a strong argument for migrating over to v6.
Earlier quoted context omitted.
Could you give a brief overview of your current understanding? I'm curious as to why /60 would be too limited, and how it's different from IPv4.
[not OP, but hey…] There’s no need for DHCP with IPv6. Clients choose the last 64 bits of an address randomly. The address space is huge — zero probability of a duplicate address . The first 64 bits therefore identify the network. If your ISP routes a /60 to you then you get to split that into 16x /64s. That’s probably fine, but the IETF recommendation is to dish out a /56 to small sites and give them a /48 if they a…
Not necessarily, there could be a flawed SLAAC implementation where the programmer just hard coded the default address after getting the PD. Or other some such silliness.
Yes it breaks spec. But there's enough devices out there that break the link local configuration spec that I would not be surprised one but if someone pushed out a broken implementation of SLAAC on a commercial product.