WAN_DHCP6 Stuck Pending / Unknown
Around May 8th, updated pfSense test system running development snapshot. Was working fine before update. After update, WAN_DHCP6 Stuck Pending / Unknown. Intermittently, IPv6 not working for 15-20 minutes after restart, but spontaneously started working with no obvious associated messages in the logs. Prior to updating, had not updated for several weeks.
Downloaded most recent development snapshot as of May 17th and installed on new VM, created from scratch.
Here is the version:
built on Sun May 17 20:08:47 EDT 2020
With this version, IPv6 appears to be working properly after restart, but WAN_DHCP6 Stuck Pending / Unknown.
The only message pertaining to the gateway is the following:
May 18 10:13:12 php 377 rc.bootup: Gateway, none 'available' for inet6, use the first one configured. 'WAN_DHCP6'
There are no messages for this gateway in the Gateways tab.
Here is a link to a thread about this on the forum: [[https://forum.netgate.com/topic/153404/wan_dhcp6-stuck-pending-unknown]]
#1 Updated by Jim Pingle 8 months ago
- Category set to Gateway Monitoring
- Status changed from New to Rejected
There isn't enough information to suggest it's a bug. Around that time is when the base OS moved to FreeBSD 12.1-STABLE but there isn't enough detail anywhere here or in the thread to lead to anything actionable. We need more than "It doesn't work". Keep it on the thread until something more definitive can be determined.
#2 Updated by Thomas Clark 7 months ago
I just upgraded from 2.4.5 to 2.4.5-RELEASE-p1 and now I am seeing the same issue. I have 3 gateways--ipv4 and ipv6 to Comcast and ipv4 to Verizon wireless. Comcast ipv4 said Pending for a long time but eventually correctly showed Online. Verizon showed Latency for a long time and eventually moved to Online. The Comcast IPv6 status showed Pending for several minutes, then Unknown where it has remained for at least 12 hours. there were no other changes in configuration, and the system was working as expected prior to the upgrade. IPv6 appears to be working as expected with clients even though the gateway status is wrong.