-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Description
Is there an existing issue for this?
- I have searched among all existing issues (including closed issues)
screenshots or captures
When a device connects via DHCP with the same hostname as an existing static host entry but a different MAC address, the DHCP leases view in LuCI displays the MAC address from the static host configuration rather than the actual MAC address from the DHCP lease file (/tmp/dhcp.leases).
This causes the lease entry to show incorrect hardware address information. If a user clicks "Make Static" on this entry, the resulting static host entry is created with the wrong MAC-to-IP binding, which can cause dnsmasq to restart with a conflicting configuration and trigger LuCI's rollback timer.
Actual behaviour
The MAC address from the matching static host entry (matched by hostname) is displayed instead of the real lease MAC.
Expected behaviour
The DHCP leases view should display the MAC address from the actual lease record, regardless of hostname matches in static host entries.
Steps to reproduce
Have a static host entry for MAC-A/hostname-X, then connect a different device (MAC-B) that sends the same hostname-X via DHCP. The lease view shows MAC-A instead of MAC-B.
Additional Information
{
"kernel": "6.6.119",
"hostname": "pi-route",
"system": "ARMv8 Processor rev 3",
"model": "Raspberry Pi Compute Module 4 Rev 1.1",
"board_name": "raspberrypi,4-compute-module",
"rootfs_type": "ext4",
"release": {
"distribution": "OpenWrt",
"version": "24.10.5",
"revision": "r29087-d9c5716d1d",
"target": "bcm27xx/bcm2711",
"description": "OpenWrt 24.10.5 r29087-d9c5716d1d",
"builddate": "1766005702"
}
}What browsers do you see the problem on?
No response