Best Practices to Obtain IPv6 Address Upon Restarting LAN Interface
-
Hi All,
If anyone has a spare moment, could you point me to a resource (bug post, forum post, etc) that explains if/how to re-establish an IPv6 address on a LAN interface normally obtained by tracking the WAN interface. I had been occassionally struggling to understand this back in the 2.1.x builds but never resolved it. I did find a bug report https://redmine.pfsense.org/issues/3514 that very closely matches the behavior I am seeing, even if the underlying cause doesn't appear to be the same.
In the latest 2.2 RC builds, all my IPv6 settings have been configured via the pfSense GUI, though I am comfortable editing configuration files by hand, if required. All I am doing to trigger the issue is to view the configuration page for an LAN interface and click "Save". Regardless of whether any changes were made or not, this action will cause the interface to loose its IPv6 address. Is this still a known issue in 2.2.x or am I just "doing it wrong?" Thanks in advance!
R/
wbedard -
I have the same issue. My ISP (Comcast) provides the LAN prefix via DHCP+PD. As a result, when the LAN IPv6 prefix (and resulting address) are lost, a simple release/renew on the WAN interface usually brings things back to normal.
-
You sir, are the man! We have the same ISP and at least a similar DHCP+PD approach on our routers. No surprise then that your suggestion worked perfectly. Thank you so much for your time in providing the guidance…:>)
R/
wbedard -
Yes, that works… but it is a hack solution nevertheless. pfSense should recover the interface on its own.
-
Yes, that works… but it is a hack solution nevertheless. pfSense should recover the interface on its own.
While I won't disagree, I also understand why making a change to a LAN interface wouldn't automatically initiate any actions on the WAN interface.
So maybe the action should be… if you Track Interface for IPv6 on an interface, when changes are applied, the interface being tracked is also released/renewed. If possible, release/renew ONLY IPv6 on the tracked interface, so as to not affect any IPv4 traffic, and since it's only IPv6 that has connectivity issues.
The only issue I can see is that there are other instances where "Track Interface" is used on the LAN side where DHCP+PD isn't used on the tracked interface… so maybe there should be an even more detailed check to see how the tracked interface is doing IPv6 before any action is taken.
