Netgate Discussion Forum
    • Categories
    • Recent
    • Tags
    • Popular
    • Users
    • Search
    • Register
    • Login

    WAN_DHCP6 Pending/Unknown

    Scheduled Pinned Locked Moved DHCP and DNS
    2 Posts 2 Posters 786 Views
    Loading More Posts
    • Oldest to Newest
    • Newest to Oldest
    • Most Votes
    Reply
    • Reply as topic
    Log in to reply
    This topic has been deleted. Only users with topic management privileges can see it.
    • beremonavabiB
      beremonavabi
      last edited by

      The only thing I've found on this is:

      WAN_DHCP6 Stuck Pending / Unknown

      and its related (rejected) bug report:

      https://redmine.pfsense.org/issues/10565

      It's an old thread in the 2.5 Development Snapshots. But, I'm on the currently released 2.4.5-RELEASE-p1 (amd64) and have been seeing this same problem for months.

      Unlike that thread, I'm on Cox instead of Telus.

      It's not a very useful description of the problem, but in a nutshell, after some period of time the WAN_DHCP6 status in the Gateways section of the Dashboard will say:

      "WAN_DHCP6 Pending Pending Pending Unknown
      ~"

      The only way I've found to clear it is to either reboot the SG-4860 or go to Interfaces > WAN > SAVE > Apply Changes.

      The WAN_DHCP6 entry will then revert to something normal, but will, at some point, fail back to that Pending/Unknown state.

      This is how the WAN interface is configured:

      IPv4 Configuration Type:  DHCP
      IPv6 Configuration Type:  DHCP6
      DHCPv6 Prefix Delegation size:  56
      Send IPv6 prefix hint
      Block private networks and loopback addresses
      Block bogon networks
      

      From the previous thread, I'm unsure if the problem is supposed to be resolved. So, I thought I'd report it here.

      SG-4860, pfSense 2.4.5-RELEASE-p1 (amd64)

      T 1 Reply Last reply Reply Quote 0
      • T
        Traveller @beremonavabi
        last edited by

        @beremonavabi I'm in the exact same boat with Comcast as the ISP.

        Trigger seems to be a loss of upstream connection. IPv4 recovers, IPv6 does not.

        Remedy is to Save WAN and Apply Changes. No actual change is required.

        If I could figure out what part of Applying Changes fixes the issue, I could automate recovery.

        1 Reply Last reply Reply Quote 0
        • First post
          Last post
        Copyright 2025 Rubicon Communications LLC (Netgate). All rights reserved.