IPv6 stops the shutdown of my NAS device.
IPv6 stops the shutdown of my NAS device.
Android used to have problems with it, which I do think works fine now. However Xbox consoles change their UUID every time you power cycle them, causing their IP address to change, which is annoying when everything on my LAN has fixed IP addresses via DHCP. I also redirect various clients over different WAN links, load-balance Steam downloads, again problematic with IPv6, particularly as my backup ISP does not have IPv6 support so I have to use an L2TP link which is rate limited much slower than than WAN link, negating the point of load balancing. Rate monitoring also doesn't work properly yet in pfSense for IPv6 which I use to identify if any client is using bandwidth that I'm not expecting. Of course its an implementation issue, but I can't fix Microsoft or Netgate software not working properly.
The issue centers on DHCPv6 AFAIK as the sole method for assigning static IP addresses (besides fixed settings which Xbox doesn’t support), relying on UUIDs that change with each reboot. This approach is tied to moving away from using MAC addresses for consistent client IPs—a feature intended for privacy but currently problematic in practice. While Windows clients handle this smoothly, Xbox’s implementation seems inconsistent, possibly due to Microsoft’s decision to abandon exclusive IPv6 usage for Xbox Live. It appears counterintuitive that Microsoft would forgo IPv6 if it could simplify monitoring for cheating or improve performance. Even with IPv6 enabled, the shift suggests a strategic pivot away from its original promise. The need for UPNP/port forwarding disappears if IPv4 isn’t available, contradicting initial claims about exclusive use. Maintaining IPv6 on the Xbox seems unnecessary given the goal of eliminating uPNP and simplifying network management. For other devices, UUIDs remain stable during reboots, though they don’t require IPv6. My local server/NAS consistently uses IPv6 in its VLAN, balancing compatibility with the main LAN. This setup allows reliable remote access over IPv6 while keeping IPv4 operations intact. My desktop client uses IPv6 only for testing and activates it when needed. Netgate acknowledges traffic issues on IPv6 but is still in beta; I must manually route IPv4 data via a custom script. If SNMP support were available, it might help, but it’s unlikely to be prioritized. Until a reliable solution emerges, manually processing traffic would be impractical and inefficient.