Bug #4451
open
Status DHCP Leases shows double entries for static entries without IP address
0%
Description
Forum: https://forum.pfsense.org/index.php?topic=89043.0
Add a "Static Mapped" DHCP entry for some MAC address but do not specify an IP address. This can be useful when you want to provide some special DHCP parameters to a client but are happy for it to get an IP address from the pool.
Connect the client. It has a dynamic IP from the pool.
Status->DHCP Leases - the client MAC is shown in 2 rows of the table - one row as the dynamic data, one row as the "static" entry without an IP address.
1) The dynamic data has the "+" button displayed at the end - that is not appropriate because there is already a static entry. The edit button that is on the end of the static row is the appropriate one.
2) Could not display the dynamic row, and put the current dynamic IP from the pool into the IP address box on the static row. That would keep the information available and remove confusion from having 2 rows. Need to think what to do about the Lease Type column - the 2 rows have "active" and "static" in them. In a sense this entry is both at once.
Some useful screenshots are on that forum post.
Files
.png){kind=link}
Updated by Phillip Davis over 11 years ago
Forum post is actually: https://forum.pfsense.org/index.php?topic=89072.0
and I do not see any buttons that allow me to edit the body of an issue I posted, or any updates of mine.
Updated by Kris Phillips over 4 years ago
This is still the case today in pfSense Plus 21.05.2 and likely in pfSense CE 2.5.2. See attached screenshot.
Updated by Kris Phillips about 4 years ago
This is still present in 22.01 and 22.05-BETA build from May 20th.
Updated by Bryan Allen 19 days ago
- Status changed from New to Feedback
Was not able to reproduce this on 26.03. Can you check to see if this is still an issue.
Updated by Christopher Cope 17 days ago
- File Screenshot(94).png Screenshot(94).png added
Tested on
26.03.1-RELEASE (amd64) built on Wed May 20 11:19:00 EDT 2026 FreeBSD 16.0-CURRENT
The behavior seems to still match the screenshot, but the + is to add a WOL mapping not to add a static mapping, so that doesn't seem incorrect to me.
I suppose we could combine them, but that doesn't seem like a bug and more of a feature request. I'll leave it in feedback in case I'm missing something.