Bug #15746
open
IPv6 is not deprecated on PPPoE Periodic Reset
0%
Description
Hi,
corresponding forum post: https://forum.netgate.com/topic/190058/ipv6-addresses-not-deprecated-on-pppoe-periodic-reset/4
When a periodic reset is set on the PPPoE interface, pfSense does not release the IPv6 prefixes advertised to the clients via RADVD before the reset time. After the PPPoE periodic reset, RADVD advertises a new prefix to the clients.
This means, that the clients need to wait for the preffered lifetime on the "old" prefix to be over, to use the new (and valid) IPv6 prefix that has been advertised after the PPPoE Periodic Reset.
If you reboot pfSense, RADVD deprecates the prefix just fine. After pfSense is back online it advertises the new prefix and clients use it right away as the old prefix was deprecated from pfSense.
You can check this using "netsh interface ipv6 show addresses", both after a PPPoE periodic reset, as well as a pfSense reboot.
Setup is using SLAAC, IPv6 is on Track Interface WAN, delegated prefixes from a /56 assigned by the ISP.
pfSense 2.7.2 (amd64), I think other versions are affected as well, but it was not tested.
-> Is this by design, maybe add a "release IPv6 on periodic reset" option then?
Thank you
Updated by Uwe Verwey 18 days ago
I have the same issue and could test any potential fix in my environment.
Issue in general: Invalid auto-configured (Stateless Address Auto-Configuration (SLAAC)) Pv6 addresses are not marked deprecated after an IPv6 prefix change on LAN Interfaces.
It is working correctly if DHCPv6 is used on the LAN subnets.
It's not related directly to PPPoE. The issue occurs if a prefix changes on a LAN interface.
Thanks.
Updated by Johannes Rohde about 9 hours ago
Same issue here as well. Unfortunately most consumer isps are handing out dynamic prefixes…There is actually an option for radvd in the config to solve this issue.