Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

IPv6 Watch

ipv6.watch

Post reply on HN
Print view View original

51–60 of 107 posts

Re: IPv6 Watch

#51

Post by divros »

The low Ipv6 domain adoption is due (in my opinion)

To not every one have Ipv6 so in your dns you need to have ipv4,to not lost this audience.

After it can be related to protection system like waf. The majority of isp give a /60 cidr to every one so it's easy to have a lot of ip. Some company like cloudflare have a mapping system from Ipv6 to ipv4 (of course with a lot of collision) and low number of procetion service provide a good detection system for Ipv6 one So majority of system in customer stack is not ready for Ipv6

I can understand you will not consume some time for low number of benefits.

(Ipv6 it help a bit all tracking system )

Re: IPv6 Watch

#52

Post by peanut-walrus »

loeg wrote: post #11
obedm wrote: post #5

Can someone explain to me what does IPv6 offer that's IPv4 doesn't? Apart from way more addresses. A good article would suffice.

> 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 not simpler in any way. Also clients still have not figured out which configuration methods they should actually support - Linux network managers generally default to SLAAC-only and DHCP needs to be explicitly enabled, for Windows setting managed flag in RA works, I believe. Android does not support DCHPv6 at all.

> network renumbering and router announcements when changing network connectivity providers.

Absolutely not. Network renumbering is a breeze when all you need to change is the public address of your gateway and the local network keeps the same local addresses. Prefix translation is awful and no firewalls have good tools to handle changing your v6 prefix.

> It simplifies processing of packets in routers by placing the responsibility for packet fragmentation into the end points.

With respect to fragmentation - yes, but overall this statement is blatantly false. v6 packet processing by routers is much much harder due to the variable length headers.

> The IPv6 subnet size is standardized by fixing the size of the host identifier portion of an address to 64 bits.

Ok, this one is true. Not entirely sure why the author considers this better, but sure, I'll agree.

Re: IPv6 Watch

#53

Post by Fidelix »

The lack of IPv6 support this site shows is mainly due to lack of support from CDNs.

They won't run out of IPv4s anytime soon, so don't expect this list to change drastically in less than 10 years.

Re: IPv6 Watch

#54

Post by wmf »

Fidelix wrote: post #53

The lack of IPv6 support this site shows is mainly due to lack of support from CDNs. They won't run out of IPv4s anytime soon, so don't expect this list to change drastically in less than 10 years.

What CDNs don't support IPv6?

Re: IPv6 Watch

#55

Post by adev_ »

obedm wrote: post #5

Can someone explain to me what does IPv6 offer that's IPv4 doesn't? Apart from way more addresses. A good article would suffice.

Random one :

"When you go SLAAC, you never go back"

(sorry for that ).

IPv6 does not need DHCP on L2.

If you even experienced a DHCP clusterfuck, you do start to appreciate the stateless auto-configuration that IPv6 provides.

Re: IPv6 Watch

#56

Post by fintler »

Scene_Cast2 wrote: post #18
fintler wrote: post #15

A basic understanding of what an IPv6 world will look like really didn't click for me until I read the IPv6 Address Planning book by Tom Coffeen. Before that, I really just saw it as IPv4 with longer addresses. Once you dig into the details, you come to the realization that it's a nearly complete reinvention of IPv4. Network planning looks quite different (especially when it comes to subnets) when you plan them with…

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.

The idea is that there's SO much address space -- you should never need to consider a question like: "is /60 to /64 enough for all of my subnets?" when planning your network. Subnets should be created because they make sense from an organizational point of view. The amount of available bits shouldn't be a practical consideration.

Also, remember, NAT is highly discouraged, so you'll (maybe) eat up another subnet if you run something like Minikube on a laptop.

Re: IPv6 Watch

#57

Post by MayeulC »

cranekam wrote: post #25
obedm wrote: post #5

Can someone explain to me what does IPv6 offer that's IPv4 doesn't? Apart from way more addresses. A good article would suffice.

Not running out of addresses is the primary (and significant) offering.

This. It's liberating to assign a single IP to every service. You can move the IP around with the service, get rid of extra reverse proxies, SNI, etc.

I'd prefer it if I could really move around while keeping the IP, that's (among others) what yggdrasil offers.

Re: IPv6 Watch

#59

Post by ATsch »

selfhoster11 wrote: post #46
gorgoiler wrote: post #31

Earlier quoted context omitted.

[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…

Some way of automatically propagating that network prefix to anything connected to the network would be nice. Otherwise we're just stuck punching in IP addresses like barbarians.

Not sure what you mean, but there's definitely no need to type addresses anywhere.

Router Advertisements propagate the subnet information (prefix, dns server, etc.) to clients in the network. Prefix delegation allows downstream routers to request subnets from upstream routers. MDNS lets network devices announce their services to the subnet.

Post reply on HN