5 ms·

I didn't RTFA but would point out that the performance problems I've run into with IPv6 aren't related to the specification itself but buggy implementation code

by jrcii 11y ago

I didn't RTFA but would point out that the performance problems I've run into with IPv6 aren't related to the specification itself but buggy implementation code from vendors, which I expect to improve with time.

shorttime 11y ago
Most definitely the case with at least Windows 8. Since I upgraded to Windows 10 I haven't experienced the problem. With Windows 8, after an uncertain period of time every app (browsers, torrents, games) would stall. It would drive me nuts until I found a post that recommended disabling the IPv6 networking protocol. It seemed to work fine until Windows 10 came along and all is good. Other devices on the network using Windows 7, android OS, didn't have any connectivity issues when the Windows 8 device did, so I'm sure it had to be Windows 8.
stock_toaster 11y ago
There are also issues with end user rollouts. For example, comcast uses prefix delegation to give you are /60 which your router (pfsense in my case) then uses for the internet network (it carves out a /64). However, this prefix changes! As it is not a statically assigned prefix, my internal devices renumber whenever it changes, it would make it a huge pain to get a consistent mapping for my internal devices (media server, printer, etc) were I to go ipv6 only. I thought about using an additional ULA subnet (ipv6 supports multiple subnets), but apparently many vendors do not yet support RFC 6724, or support it poorly with regard to ULA addresses. As such, I get mixed results with devices trying to use the ULA address for internet egress. NAT66 (npt) is another possibility, and some people end up having to use this when they have more than one ISP (multi-wan balancing) anyway, but I haven't found a good way to update the nat target when the prefix changes yet (might try moving to openbsd and try ifstated calling a script to a pf table or something).
- lmm 11y ago
  > For example, comcast uses prefix delegation to give you are /60 which your router (pfsense in my case) then uses for the internet network (it carves out a /64). However, this prefix changes! As it is not a statically assigned prefix, my internal devices renumber whenever it changes, it would make it a huge pain to get a consistent mapping for my internal devices (media server, printer, etc) were I to go ipv6 only. Part of the point of IPv6 is that your addresses reflect the real network topology - when your upstream changes, your addresses change. The right thing is to ensure that your router is also updating DNS for your internal devices, and use names to refer to them. You shouldn't expect anything to have a truly static IPv6 address.
  - stock_toaster 11y ago
    > The right thing is to ensure that your router is also > updating DNS for your internal devices, and use names > to refer to them. How does a router go about doing that with SLAAC? Running dhcp6 is something I would like to avoid. Maybe Bonjour/mDNS are just going to be far more prevalent in the ipv6 world. For most devices, a constantly changing IP is well and good (eg ipv6 privacy extensions). However, for servers it is less than desirable.
    - karlshea 11y ago
      This is the missing part for me as well. I run DNS internally and it works just fine for IPv4, but everything is using SLAAC so I can't have AAAA records. The only solution I've heard so far is to have a client on each machine that would update the DNS server with the new address, which sounds terrible. I'm just about at the point that I'm just going to install DHCPv6, but last I heard not every OS supported it?
    - lmm 11y ago
      Hah. The more I look into this the more awkward it seems; I was lucky enough to have dhcp6 Just Work on my home network but it sounds like not everything supports it.

by jrcii 11y ago

shorttime 11y ago

Most definitely the case with at least Windows 8. Since I upgraded to Windows 10 I haven't experienced the problem. With Windows 8, after an uncertain period of time every app (browsers, torrents, games) would stall. It would drive me nuts until I found a post that recommended disabling the IPv6 networking protocol. It seemed to work fine until Windows 10 came along and all is good. Other devices on the network using Windows 7, android OS, didn't have any connectivity issues when the Windows 8 device did, so I'm sure it had to be Windows 8.

stock_toaster 11y ago

There are also issues with end user rollouts. For example, comcast uses prefix delegation to give you are /60 which your router (pfsense in my case) then uses for the internet network (it carves out a /64). However, this prefix changes! As it is not a statically assigned prefix, my internal devices renumber whenever it changes, it would make it a huge pain to get a consistent mapping for my internal devices (media server, printer, etc) were I to go ipv6 only. I thought about using an additional ULA subnet (ipv6 supports multiple subnets), but apparently many vendors do not yet support RFC 6724, or support it poorly with regard to ULA addresses. As such, I get mixed results with devices trying to use the ULA address for internet egress. NAT66 (npt) is another possibility, and some people end up having to use this when they have more than one ISP (multi-wan balancing) anyway, but I haven't found a good way to update the nat target when the prefix changes yet (might try moving to openbsd and try ifstated calling a script to a pf table or something).

lmm 11y ago
> For example, comcast uses prefix delegation to give you are /60 which your router (pfsense in my case) then uses for the internet network (it carves out a /64). However, this prefix changes! As it is not a statically assigned prefix, my internal devices renumber whenever it changes, it would make it a huge pain to get a consistent mapping for my internal devices (media server, printer, etc) were I to go ipv6 only. Part of the point of IPv6 is that your addresses reflect the real network topology - when your upstream changes, your addresses change. The right thing is to ensure that your router is also updating DNS for your internal devices, and use names to refer to them. You shouldn't expect anything to have a truly static IPv6 address.
- stock_toaster 11y ago
  > The right thing is to ensure that your router is also > updating DNS for your internal devices, and use names > to refer to them. How does a router go about doing that with SLAAC? Running dhcp6 is something I would like to avoid. Maybe Bonjour/mDNS are just going to be far more prevalent in the ipv6 world. For most devices, a constantly changing IP is well and good (eg ipv6 privacy extensions). However, for servers it is less than desirable.
  - karlshea 11y ago
    This is the missing part for me as well. I run DNS internally and it works just fine for IPv4, but everything is using SLAAC so I can't have AAAA records. The only solution I've heard so far is to have a client on each machine that would update the DNS server with the new address, which sounds terrible. I'm just about at the point that I'm just going to install DHCPv6, but last I heard not every OS supported it?
  - lmm 11y ago
    Hah. The more I look into this the more awkward it seems; I was lucky enough to have dhcp6 Just Work on my home network but it sounds like not everything supports it.