4 ms·

> IPv6 has some quirks that make it harder to digest. Almost every point in your list is wrong. > - link local gateway address, makes it hard to understand wh

by teddyh 6mo ago

> IPv6 has some quirks that make it harder to digest. Almost every point in your list is wrong. > - link local gateway address, makes it hard to understand why the subnet does not have a gateway from the ssme address space IPv4 has link-local addresses, too. Those are the 169.254.X.X addresses that you see on Windows machines. IPv6 adds nothing new. > - privacy extensions: it is very hard to explain to people why they have 3-4 IPv6 addresses assigned to their computer Well then, don’t use them. Configure the machines with one address each, just like before. If you want the (arguable) advantages of the privacy extensions, they are available, but not mandatory. > - multicast instead of broadcast IPv4 always had multicast, too. IPv6 is simplified by considering the broadcast concept to be a kind of multicast. > - way too many ways for autoconfiguration (SLAAC, DHCPv6) SLAAC is just link-local addresses, which you already mentioned above. Did you mean NDP with router advertisements? If you did, you do have a small point, but DHCP6 is still there like always. IPv6 just offers an additional feature for the simple cases where a host just needs an IP address, netmask and a router address. > - no real tentative mapping to what people were used to. Every IPv6 presentation I did had to start with “forget everything you know about IPv4” That’s the complete opposite of my experience. Almost everything in IPv6 works exactly the same as with IPv4.

patmorgan23 6mo ago
You're being obtuse. Every point in the original comment is correct, you just disagree they're issues. The original comment also doesn't state they are issues just that they are differences. • link local addresses .Auto configuration addresses are in V4 but they are used entirely differently. Interfaces do not have link local addresses if they have a DHCP or statically configured address, in V6 it is extremely common to use a link local address as the gateway, in V4 this basically never happens.
- teddyh 6mo ago
  > The original comment also doesn't state they are issues just that they are differences. My point is that, in most cases, these aren’t differences, since IPv4 does the same thing as IPv6. Therefore, the claim that IPv6 “has some quirks that make it harder to digest [than IPv4]” is incorrect. > Interfaces do not have link local addresses if they have a DHCP or statically configured address I could be wrong, but I seem to recall that Windows machines always have a IPv4LL address? > in V6 it is extremely common to use a link local address as the gateway What? I have never seen this.
  - apple4ever 6mo ago
    > What? I have never seen this. What? Never? Is extremely common. I just checked both my Mac and Windows desktops and they both show a link local gateway. It makes me question whether you've used IPv6 all that much.
    - teddyh 6mo ago
      Every single machine I use, both at home and at work, has IPv6. Exactly none of them use a link-local address as the gateway address.
apple4ever 6mo ago
>> IPv6 has some quirks that make it harder to digest. > Almost every point in your list is wrong. You missed the point and almost every counterpoint in your list is wrong. >> - link local gateway address, makes it hard to understand why the subnet does not have a gateway from the ssme address space >IPv4 has link-local addresses, too. Those are the 169.254.X.X addresses that you see on Windows machines. IPv6 adds nothing new. That's not what the OP said. Note it says gateways. IPv4 when DHCP'd will show 192.168.1.1 for example when it has a 192.168.1.55 address. IPv6 will show fe23::166:8f2c:9a21:96de when it has a 2001:921:61c:aef:78f:7190:1ca2 address, despite the gateway actually being 2001:921:61c:aef::1. So its highly confusing for no good reason. >> - privacy extensions: it is very hard to explain to people why they have 3-4 IPv6 addresses assigned to their computer > Well then, don’t use them. Configure the machines with one address each, just like before. If you want the (arguable) advantages of the privacy extensions, they are available, but not mandatory. While you can configure not use them, by default DHCP'd devices WILL have a bunch. Again confusing for no good reason. >> - no real tentative mapping to what people were used to. Every IPv6 presentation I did had to start with “forget everything you know about IPv4” > That’s the complete opposite of my experience. Almost everything in IPv6 works exactly the same as with IPv4. It's the complete opposite experience for most people, including network engineers.

by teddyh 6mo ago

patmorgan23 6mo ago

You're being obtuse. Every point in the original comment is correct, you just disagree they're issues. The original comment also doesn't state they are issues just that they are differences. • link local addresses .Auto configuration addresses are in V4 but they are used entirely differently. Interfaces do not have link local addresses if they have a DHCP or statically configured address, in V6 it is extremely common to use a link local address as the gateway, in V4 this basically never happens.

teddyh 6mo ago
> The original comment also doesn't state they are issues just that they are differences. My point is that, in most cases, these aren’t differences, since IPv4 does the same thing as IPv6. Therefore, the claim that IPv6 “has some quirks that make it harder to digest [than IPv4]” is incorrect. > Interfaces do not have link local addresses if they have a DHCP or statically configured address I could be wrong, but I seem to recall that Windows machines always have a IPv4LL address? > in V6 it is extremely common to use a link local address as the gateway What? I have never seen this.
- apple4ever 6mo ago
  > What? I have never seen this. What? Never? Is extremely common. I just checked both my Mac and Windows desktops and they both show a link local gateway. It makes me question whether you've used IPv6 all that much.
  - teddyh 6mo ago
    Every single machine I use, both at home and at work, has IPv6. Exactly none of them use a link-local address as the gateway address.

apple4ever 6mo ago

>> IPv6 has some quirks that make it harder to digest. > Almost every point in your list is wrong. You missed the point and almost every counterpoint in your list is wrong. >> - link local gateway address, makes it hard to understand why the subnet does not have a gateway from the ssme address space >IPv4 has link-local addresses, too. Those are the 169.254.X.X addresses that you see on Windows machines. IPv6 adds nothing new. That's not what the OP said. Note it says gateways. IPv4 when DHCP'd will show 192.168.1.1 for example when it has a 192.168.1.55 address. IPv6 will show fe23::166:8f2c:9a21:96de when it has a 2001:921:61c:aef:78f:7190:1ca2 address, despite the gateway actually being 2001:921:61c:aef::1. So its highly confusing for no good reason. >> - privacy extensions: it is very hard to explain to people why they have 3-4 IPv6 addresses assigned to their computer > Well then, don’t use them. Configure the machines with one address each, just like before. If you want the (arguable) advantages of the privacy extensions, they are available, but not mandatory. While you can configure not use them, by default DHCP'd devices WILL have a bunch. Again confusing for no good reason. >> - no real tentative mapping to what people were used to. Every IPv6 presentation I did had to start with “forget everything you know about IPv4” > That’s the complete opposite of my experience. Almost everything in IPv6 works exactly the same as with IPv4. It's the complete opposite experience for most people, including network engineers.