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

    DHCPv6 apparently ignores static leases?

    Scheduled Pinned Locked Moved 2.1 Snapshot Feedback and Problems - RETIRED
    5 Posts 2 Posters 1.2k 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.
    • D
      doridian
      last edited by

      As you can see in the screenshot I have assigned static IPv6 addresses to the client. But the first entry shows them still getting a dynamic one?
      (And yes, that is the lease the machine gets if I run "dhclient -6 eth0 -v")

      The DHCPv6 range is set to "fd00::0001:0000" until "fd00::0001:ffff" and the Router Advertisment is on "Assisted".

      Anything I am doing wrong?
      meow.png
      meow.png_thumb

      1 Reply Last reply Reply Quote 0
      • jimpJ
        jimp Rebel Alliance Developer Netgate
        last edited by

        Funny, I had recently observed the same behavior on my setup, though it turned out that somehow my client's DUID had changed. I fixed the DUID in the static config and it picked the correct IP up once again.

        Though by eyeballing your config it does look to be the same DUID on both, so I'm not quite sure how that isn't matching.

        Anything in the DHCP log about it?

        Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

        Need help fast? Netgate Global Support!

        Do not Chat/PM for help!

        1 Reply Last reply Reply Quote 0
        • D
          doridian
          last edited by

          Nothing that looks like it isn't supposed to be.
          I attached the DHCP log anyway.

          meow.png
          meow.png_thumb

          1 Reply Last reply Reply Quote 0
          • jimpJ
            jimp Rebel Alliance Developer Netgate
            last edited by

            That's all I saw, too.

            I ended up not seeing it in the GUI (though it was staring me in the face) I did a packet capture of the port 546 IPv6 traffic and looked it over in wireshark and it hit me.

            You might also run a similar capture while doing a release/renew of IPv6 on the client, and seeing /var/dhcpd/etc/dhcpd6.conf might help as well.

            Remember: Upvote with the ๐Ÿ‘ button for any user/post you find to be helpful, informative, or deserving of recognition!

            Need help fast? Netgate Global Support!

            Do not Chat/PM for help!

            1 Reply Last reply Reply Quote 0
            • D
              doridian
              last edited by

              After a lot of fiddling around I finally managed to fix it. The clients cached their leases and somehow preferred their own cached leases toward the lease that pfSense offered them.
              (Even though I did "dhclient -v -6 eth0 -r" and then "dhclient -v -6 eth0" to release/renew). Weird.

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