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

    pfSense 23.01 bug : Unable to set DUID from DHCPv6 Leases

    Scheduled Pinned Locked Moved IPv6
    4 Posts 2 Posters 771 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.
    • chaseC
      chase
      last edited by chase

      My pfSense 23.01 DHCPv6 Router mode is set to "Managed".

      My objective is to visit "Status / DHCPv6 Leases" to setup a static IPv6 assignment for Plume.com devices so that I can better monitor their communication traffic.

      In the "Status / DHCPv6" leases, I find one of the Plume devices there. It has a DUID of 00:03:00:01:60:b4:f7:f0:7e:ca.

      I click the "+" button for "Add a static Mapping" which opens a tab to "Services / DHCPv6 Server & RA / WIFI / DHCPv6 Server / Edit Static Mapping"

      pfSense already pre-populated DUID field with 00:03:00:01:60:b4:f7:f0:7e:ca. Upon completing the other fields (IPv6 Address, Hostname, Description) and clicking "Save", I get an error "The prefix (upper 64 bits) must be zero. Use the form ::xxxx:xxxx:xxxx:xxxx"

      QUESTIONS:

      1. What should be the proper DUID value to enter there?
      2. Why isn't pfSense already applying the mask and conversion of its DUID from "Status / DHCPv6" over to this field?
      Bob.DigB 1 Reply Last reply Reply Quote 0
      • Bob.DigB
        Bob.Dig LAYER 8 @chase
        last edited by

        @chase You don't set DUID but an IP-address. Make a screenshot so that we can see what you did wrong there.

        chaseC 1 Reply Last reply Reply Quote 0
        • chaseC
          chase @Bob.Dig
          last edited by chase

          @bob-dig

          Bob ... okay .. thanks for the push-back here. Upon reflection, I was associating pfSense's error [1] with the DUID entry value rather than the "IPv6" value I supplied -- see the following (altered) examples of IPv6 values I tried:

          WRONG: 2602:15:c011:e390::1:3ed8
          WRONG: ::e390::1:3ed8
          CORRECT: ::e390:0000:0001:3ed8

          Now that I'm correctly specifying the correct IPv6 address within the context of my delegated prefix, I'm successfully tracking those Plume.com devices.

          My one regret is that I cannot change the subject of this posting to more accurately title it as :

          In DHCPv6 static mappings, the error "The prefix ... must be zero" means you have the wrong IPv6 value in there.

          NOTES:
          [1]"The prefix (upper 64 bits) must be zero. Use the form ::xxxx:xxxx:xxxx:xxxx"

          Bob.DigB 1 Reply Last reply Reply Quote 1
          • Bob.DigB
            Bob.Dig LAYER 8 @chase
            last edited by

            @chase My wording isn't the best, glad you figured it out.

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