I would find it very helpful to have an optional toggle that limits the active DHCP lease list to devices that are not specified in the static DHCP list. This makes identifying new devices on the network much easier. As it is, the lease list always includes the static dhcp list, an it gets cumbersome when you have a few devices on the net. Being able to optionally see the "free roaming" only would be nice.
I hacked this feature into the PHP file on the previous version (v5), and it was very useful to me; I had the lease list (excluding the static ones) on top, and the static dhcp list below, with no overlap between them. I could easily move the any lease to the static list with a single click, and I never had to check if it was already there because only the "free roaming" dhcp leases showed up on the lease list. Adding a new device on the network was a breeze, I could sort the static leases by IP and easily see if there was a slot in the range for my new device.
I didn't realize php was being dropped when I updated, and after having a look I can't find a straightforward way to add this feature with the current architecture, as it seems the dhcp list api endpoint doesnt hold info about a lease being in the static list or not.
PS: maybe this could be as easy as adding an extra column to the dhcp range table, stating if the lease is static or dynamic?
In the "Network" overview you have a "First seen" column.
Isnt that one more suited to detect new devices as it includes the date plus extras?
EDIT: That one is ARP based so the device doesnt even have to use Pi-hole for DNS or get a lease from Pi-hole to be listed.
$ ip neighbor
10.0.0.11 dev eth0 lladdr 00:1e:0b:XX:XX:XX REACHABLE
10.0.0.1 dev eth0 lladdr 50:46:5d:XX:XX:XX STALE
10.0.0.2 dev eth0 lladdr b8:27:eb:XX:XX:XX STALE
Also might I ask why you're micro managing DHCP for all your clients?
The only static DHCP reservations I create are for network important devices like Pi-hole, switches, network important servers.
But thats only as a fallback in case something goes wrong (new install, firmware update, tinker error) as these devices are manually configured with static IP details.
And how are you going to micro manage IPv6?
Thanks, those help! But its not as easy as seeing the whole DHCP IP range in one table, showing IP, MAC and hostname. Maybe it would be as easy as adding an extra column (sortable) that specified if its a static lease or not.
I have a lot of iot sensors on the network, as well as a lot of retro (old macs) and Single Board Computers... I like to keep the ranges tidy. A lot of them are microcontrollers, so configuring often requires reflashing that is a pain.
I'd much rather have a centralized control over their IPs, so they are all on dhcp. I also like
About the IPv6 I'll worry about when I have to... And I'll keep ip4 static addressing for as long as I can for my home.
That sounds like a nice FR for the network overview.
Something like "lease", "reservation" or "none".
You do know that you already can change the sort order for the columns on that network overview page?
Sounds like allot of work.
I also have some SBC's for IoT tasks but dont have reservations for them.
I address them by DNS name and not via IP.
Yeah same here.
I dont like maintaining a dual stack IPv4 + IPv6 (IP's, DNS, routes, firewall etc).