Delete



  • Thread hijacked


  • Banned

    @Double:

    thereby eating up the pool of DHCPv6 addresses.

    Yeah, there are only 18,446,744,073,709,551,616 IPv6 addresses in a /64, you might deplete the pool soon.  ::) :o



  • @Double:

    PS - The reason why I don't want the XBOX One to get a DHCPv6 address from the pool is because it changes it's DUID on every boot, thereby eating up the pool of DHCPv6 addresses.

    Now THAT is wrong, it breaks RFC 3315. The windows 10 dhcpv6 client doesn't have that behaviour (but they managed to break it in another way). It seems Microsoft doesn't have a working dhcpv6 client atm.


  • Banned

    +1 on both points. The time here would be better spent by nagging MS to fix their shit.



  • Supposedly there will be a fix in March.


  • Banned

    Did they tell you which year? (Been waiting for W10 1607 DHCPv6 fix for almost a year, and nothing happened.)



  • Thread hijacked



  • @doktornotor:

    Did they tell you which year? (Been waiting for W10 1607 DHCPv6 fix for almost a year, and nothing happened.)

    Good one. I believe they were referring to the current march. I'm running insider preview version 1607 build 15042.0 and it appears to be fixed. I just booted the system so there hasn't been time for the lease to expire yet. I'll keep an eye on it and update when I have seen evidence of the lease expiring and renewing automatically.



  • My system updated to version 1606 build 15046.0 yesterday and dhcpv6 is working properly. Looks like they finally fixed the problem.


  • Banned

    Wow, impressive. Perhaps we'll see a hotfix in another 6 months or so for the people on LTSB branch unwilling to be a guinea pig for MS.



  • @doktornotor:

    Wow, impressive. Perhaps we'll see a hotfix in another 6 months or so for the people on LTSB branch unwilling to be a guinea pig for MS.

    It's part of the "creators update".


  • Banned

    As said, LTSB is all that I'm interested in (or, any business unfortunate enough to have W10 boxes).



  • @doktornotor:

    As said, LTSB is all that I'm interested in (or, any business unfortunate enough to have W10 boxes).

    I hear you. How they can break something that should have been stable for years is beyond me.

    I'm running version 1607 build 14393.693 (windows home, not preview) on another system and dhcpv6 seems to be working. I'll keep an eye on it.

    What is the latest version / build you using where it's not working?



  • @bimmerdriver:

    @doktornotor:

    As said, LTSB is all that I'm interested in (or, any business unfortunate enough to have W10 boxes).

    I hear you. How they can break something that should have been stable for years is beyond me.

    I'm running version 1607 build 14393.693 (windows home, not preview) on another system and dhcpv6 seems to be working. I'll keep an eye on it.

    What is the latest version / build you using where it's not working?

    The dhcpv6 lease renewed again, so the problem appears to be fixed.