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

    DHCPv6 Not Renewing Leases

    Scheduled Pinned Locked Moved 2.4 Development Snapshots
    3 Posts 2 Posters 1.7k 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.
    • B
      bimmerdriver
      last edited by

      I've found DHCPv6 to be flakey at the best of times and I reported a bug about them (https://redmine.pfsense.org/issues/6717). (I'm testing 2.4 on a windows 2012R2 hyper-v server with windows 10 guests.) Lately, I've noticed DHCPv6 has changed for the worse. Whereas most of the time, I could force a lease to renew by disabling and enabling the ethernet interface, that's not working. Rebooting the pc will sometimes work, as will explicitly doing ipconfig /release6 and /renew6. If I don't renew the lease using ipconfig, it will expire and not be automatically renewed. I'm wondering if anyone else has noticed this.

      1 Reply Last reply Reply Quote 0
      • I
        Inq
        last edited by

        I have the same problem. At first i thought that it was a problem with my W10 machines.
        Here is the output of  netsh int ipv6 show addresses:

        Interface 6: Ethernet

        Addr Type  DAD State  Valid Life Pref. Life Address
        –-------  ----------- ---------- ---------- ------------------------
        Public    Preferred    23h49m31s  3h49m31s 2a02:2f04:146:2500:xxxx:xxxx:xxxx:xxxx
        Temporary  Preferred    23h49m31s  3h49m31s 2a02:2f04:146:2500:911a:4e47:6ac9:d78c
        Other      Preferred    infinite  infinite fe80::xxxx:xxxx:xxxx:xxxx%6

        After ipconfig /renew6 :

        Interface 6: Ethernet

        Addr Type  DAD State  Valid Life Pref. Life Address
        ---------  ----------- ---------- ---------- ------------------------
        Dhcp      Preferred    1h59m28s  1h14m28s 2a02:2f04:146:2500::xxxx
        Public    Preferred    23h59m28s  3h59m28s 2a02:2f04:146:2500:xxxx:xxxx:xxxx:xxxx
        Temporary  Preferred    23h59m28s  3h59m28s 2a02:2f04:146:2500:911a:4e47:6ac9:d78c
        Other      Preferred    infinite  infinite fe80::xxxx:xxxx:xxxx:xxxx%6

        After 1h15 min the dhcp address usually gets deprecated.

        Standard 2.3.2 x64 install.

        Later edit:

        After some digging i've found this post on he.net forums https://forums.he.net/index.php?topic=3606.0 referring this https://social.msdn.microsoft.com/Forums/en-US/7f076f49-4e0d-494c-8d98-5dc9acbe76f5/windows-10-anniversary-update-breaks-dhcpv6-client?forum=windbg
        and this https://social.technet.microsoft.com/Forums/windows/en-US/b16e7d78-e390-4ada-a24b-3ccba60fa571/no-ipv6-dns-statelessdhcp-since-windows-10-anniversary-update?forum=win10itpronetworking

        Looks like a Microsoft bug.

        The problem with making something idiot proof is that the world keeps making better idiots.

        1 Reply Last reply Reply Quote 0
        • B
          bimmerdriver
          last edited by

          Good catch. I'll report that on the feedback hub, for what good that will do.

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