Bug #6717


Status / DHCPv6 Leases Issues

Added by Daryl Morse about 5 years ago. Updated almost 5 years ago.

Target version:
Start date:
Due date:
% Done:


Estimated time:
Plus Target Version:
Release Notes:
Affected Version:
Affected Architecture:


I'm running 2.3.3.a.20160815.2144 with PR 3102/1, 3102/2, 3103, 3105, 3106 and 3107, testing the fix for I'm testing on a windows 2012R2 hyper-v server using a private virtual switch and 4 x windows 10 virtual clients. The WAN connection is a bridged modem port shared by another pfsense.

I've noted several issues with Status / DHCPv6 Leases.

1. Upon booting, the message "No leases file found. Is the DHCPv6 server active?" is displayed when Status / DHCPv6 Leases is selected. This is being caused by /var/dhcpd/var/db/dhcpd6.leases being purged upon reboot. DHCPv4 leases are not being purged.

2. /var/dhcpd/var/db/dhcpd6.leases is not being updated consistently. I'm forcing creation of new leases by disable / enable of the network adapter on the PCs, verifying the new lease time using ipconfig /all. I'm noticing that dhcpv6 leases are randomly not updating on Status / DHCPv6 Leases. It occurs approximately 25-50% of the time. If I leave the system alone, when the lease expires, Status / DHCPv6 Leases usually updates correctly. DHCPv4 leases update consistently.

3. When the DHCP Service is stopped, /usr/local/sbin/dhcpleases6 stays running. When the service is restarted, /usr/local/sbin/dhcpleases6 gets killed and restarted along with dhcpd and dhcpd -6. Not really a big deal, but is there a reason it's left running or should it be killed along with dhcpd and dhcpd -6?

4. This is a feature request. It's possible to restart and stop DHCP Service using Status / Dashboard / Services Status. It's possible to restart and stop DHCPv4 by itself using Status / DHCP Leases. There is no way to stop or restart DHCPv6 by itself. It would be useful to be able to restart and stop DHCPv6 by itself.


Also available in: Atom PDF