WAN_DHCP6 Pending
-
I implemented pfSense 9 days ago. It seems to be working quite well. However, yesterday, my WAN_DHCP6 gateway started registering "Pending" for "RTT," etc for the first time and has stayed in that state for nearly 24 hours. Because everything seems to be working correctly, I wonder what this means and how do I correct (I have not rebooted, yet). Thanks.
-
Do you have IPv6? Is it pulling an address as expected?
Pending like that usually means it's set to dhcpv6 and has no gateway to monitor yet.
Steve
-
Thanks for the quick response. I do have IPv6 address (fe80::..........:6efc). I rebooted the device and rejoiced!
All is good now. -
That fe80 address is called link local. The question was about whether you have IPv6 service from your ISP, where you'd get an address and prefix via DHCP. Every IPv6 capable device has a link local address, but that does not mean you have IPv6 available from your ISP.
-
@JKnott Thanks for educating on this. It does look like my modem (Netgear C7100V) has that set up.
-
@elliott32224 said in WAN_DHCP6 Pending:
I implemented pfSense 9 days ago. It seems to be working quite well. However, yesterday, my WAN_DHCP6 gateway started registering "Pending" for "RTT," etc for the first time and has stayed in that state for nearly 24 hours. Because everything seems to be working correctly, I wonder what this means and how do I correct (I have not rebooted, yet). Thanks.
I am having the exact same issue and it is driving me mad. Currently on Comcast.
-
@sarrasine What version of pfSense are you running?
-
@traveller Hi, 21.02
-
@sarrasine I also have Comcast for an ISP.
Before the update, I found that I had to Save the WAN settings (no changes needed) to get the IPv6 sorted.
With the update (which I have not yet done due to other concerns), it seems that you need to manually specify the upstream target (looking at the Diagnostics > Routes will provide the current upstream router) for the IPv6 Gateway Monitor.
Related topic: https://forum.netgate.com/post/965293
-
@traveller Thank you! That seems to have fix it until there is an official bug squash.
