After IPv6 prefix change no IPv6 connectivity on Windows host
-
Before I did PPPoE on pfSense itself I had another router in front which did it. When the Prefix changed at night times I had to reboot pfSense via cron to make sure to have IPv6 connectivity the next morning.
Now I thought these problems are fully solved but their kinda only for the most part.
Today I rebootet pfSense at daytime and, with that, got a new IPv6 Prefix. But my main Windows host didn't got it, used an old one, so it had no IPv6 connectivity, pfSense itself had no problem.On this interface I used "Stateless DHCP" or "Unmanaged", not sure anymore. What had helped was to "cycle" the NIC on the host.
So now I switched to "Assisted" in hope, that a DHCP Server will fix this problem in the future. But how likely is that?Maybe the default lease times for IPv6 should be drastically shortened on any interface which uses "track".
-
@bob-dig said in After IPv6 prefix change no IPv6 connectivity on Windows host:
Maybe the default lease times for IPv6 should be drastically shortened on any interface which uses "track".
Another way to tackle that would be to use NPt I guess. So it would be great for that, if pfSense allows to use Track Interface in the NPt options directly instead of only using it for "physical" interfaces.
