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

91–100 of 107 posts

Re: IPv6 Watch

#91

Post by gorgoiler »

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.

RA: router advertisements.

The good riddance part of IPv4 DHCP is the server maintained state. The broadcast-config thing is still there. RADVD is the standard Linux daemon for this.

Re: IPv6 Watch

#92

Post by gorgoiler »

somerandomqaguy wrote: post #80
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…

> The address space is huge — zero probability of a duplicate address. 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 impleme…

DAD at the other end kills bad actors like this fast. But if the implementation at both ends is broken…?

Re: IPv6 Watch

#93

Post by [deleted] »

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…

[deleted]

Re: IPv6 Watch

#94

Post by remram »

junon wrote: post #76
cbg0 wrote: post #8

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.

That's a bit of an unfair argument. The site's intent is to show the general population's ability to organically reach those sites with ipv6. AAAA records are necessary for that to happen.

If you can reach the Steam website to buy a game and then you can't install it, because the site has IPv6 but the app doesn't, it is much worse.

Re: IPv6 Watch

#96

Post by junon »

remram wrote: post #94
junon wrote: post #76

Earlier quoted context omitted.

That's a bit of an unfair argument. The site's intent is to show the general population's ability to organically reach those sites with ipv6. AAAA records are necessary for that to happen.

If you can reach the Steam website to buy a game and then you can't install it, because the site has IPv6 but the app doesn't, it is much worse .

Why does that make a difference? You can have both.

Re: IPv6 Watch

#98

Post by floatboth »

peanut-walrus wrote: post #52
loeg wrote: post #11

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…

> the local network keeps the same local addresses

If you need that, you can assign local addresses from the ULA range. No one is forcibly taking your local addressing away. Now, yes, the "V6 ideology" is about globally routable public all the things, but you don't have to follow it.

Re: IPv6 Watch

#99

Post by adev_ »

citrin_ru wrote: post #68
adev_ wrote: post #55

Earlier quoted context omitted.

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.

You still need DHCP for more than one reason: 1. Prefix delegation 2. DDNS (DHCP server can register a client IP in DNS) I've used SLAAC in my home LAN when used IPv6 ISP. Now I use IPv4-only ISP (in my area no ISP supports IPv6) and don't miss SLAAC at all. Over the years I've used DHCP in many smallish LANs (<=100 hosts) and never had any problems with it.

> You still need DHCP for more than one reason:

1) You generally do not need prefix delegation in v6: you use IPv6 like it has been designed too: routable address everywhere, /64 per default and prefix over it.

2) SLAAC is stateless and deterministic: One MAC address will always gives you the same IP. That makes DDNS mostly useless.

But even if you really want to do it, it is also possible with SLAAC.

Re: IPv6 Watch

#100

Post by fulafel »

lovecg wrote: post #36
bejelentkezni wrote: post #12

Earlier quoted context omitted.

If I recall correctly, ipv6 addresses beginning with 0::0:ffff are mapped 1-to-1 with ipv4 addresses.

I’m mostly still annoyed about the colon. Come on, ip:port is a pretty widely used convention people! The number of parsing bugs I had to fix with the migration…

On the plus side the schedule was reasonable, you had time since the 1990s :)
Post reply on HN