Windows 10 experiences network outages under IPv6 dynamic RA prefix conditions, while Ubuntu continues to function normally.

Hi Amelia Jones,

How is your issue going? Has it been resolved yet? If it has, please consider accepting the answer as it helps others sharing the same problem benefit too. Thank you :)

VP

Hi Amelia Jones,

The network disconnects you are experiencing highlight a known behavioral difference between the Windows and Linux networking stacks when handling extreme IPv6 Router Advertisement frequencies. When your core gateway continuously broadcasts new prefixes without explicitly invalidating the old ones, Windows 10 dutifully complies with standard Stateless Address Autoconfiguration protocols. It generates a new IPv6 address, default gateway, and routing entry for every single advertisement. Because these dynamically generated routes accumulate much faster than their designated time-to-live values naturally expire, the Windows routing table becomes severely bloated until the network interface simply stops functioning. Your Ubuntu servers handle this network segment gracefully because the Linux kernel employs aggressive route garbage collection limits to drop excess routing data before memory exhaustion occurs.

The resolution requires adjusting the core gateway so it either stabilizes the prefix or broadcasts a zero valid lifetime for deprecated prefixes, as continuous rotation violates standard enterprise design. To demonstrate this routing exhaustion to your IT director, open an elevated PowerShell prompt on a failing Windows machine and run the Get-NetRoute -AddressFamily IPv6 command to display the massive accumulation of redundant routes. You can also monitor the interface behavior by inspecting the HKLM\SYSTEM\CurrentControlSet\Services\TCPIP6\Parameters registry key, which houses the core IPv6 protocol configurations.

If you need to keep the Windows machines online temporarily while the network infrastructure is corrected, you can run Set-NetIPInterface -InterfaceAlias "Ethernet" -RouterDiscovery Disabled in an elevated PowerShell prompt, substituting your actual adapter name. This command forces the adapter to ignore incoming advertisements and halts the route accumulation. You will, however, need to assign a static IPv6 address and default gateway manually to maintain connectivity during this interim period.

Hope this answer brought you some useful information. If it did, please hit “accept answer”. Should you have any questions, feel free to leave a comment.

VP