A couple days ago, I turned on the DHCP service on my pihole.
It worked pretty well. But one device wouldn't take my reserved address, so i removed the lease manually from the leases file. Then it took the reserved address.
To cut a long story short, it would be cool if we could remove/revoke the leases over the website.
Very much yes! I took dhcp away from my router, but I feel like dhcp on the pihole should have more of the dhcp related features that other devices have.
Overall, I think the settings page could use some TLC. With the newer features added, it's starting to look cluttered.
I think that the "Settings" button in the left-had pane should expand like the "Tools" and "Disable" buttons.
There should then be multiple options.
"DHCP" should be it's own page,
"DNS Settings", and
"Administration" just move
The non-editable "Networking"
"Web User Interface" options
"System Administration"
"Pi-hole Teleporter"
Doing that would leave room on the pages to get rid of the "expanding plus buttons", and make the interface nicer to use in general.
I'm definitely on board with deathbybandaid's idea. For users that take advantage of the DHCP functionality, it's a very important feature of the system, and having to go to the generic "Settings" page and expand a couple of menus makes it feel buried away.
Also, would love the ability to release leases via the GUI.
Good idea! The DHCP part should get a little more priority, cause its an important service in a network. An rearrangement of the frontend would be nice.
This gets my vote 2. I am running Pi-Hole on my Synology NAS, and it replaces the Synology SHCP server which has this functionality and I would find it very useful to have the ability to delete leases available.
True. We aim to focus on stability first, sexy features later. Something like this is actually a larger undertaking than it first appears, as it would involve a lot of smaller changes under the hood to make sure it works correctly. That said, we're not dismissing it just yet!
I don't think dnsmasq (and FTLDNS as it's an in-house fork of dnsmasq) has the ability to revoke an active lease (unless disable/delete/enable).
Editing the lease file and removing the line, will not help either with dnsmasq (or FTLDNS) active because the lease file is read at program start and after start it uses a cached version (in memory) of the file.
One would need to stop dnsmasq (or FTLDNS) edit/remove the line and then restart dnsmasq (or FTLDNS).
But disabling dnsmasq (of FTLDNS) while in use, for a lease entry removal will definitely affect the other devices.
Instead of removing a lease like that, why not use a lease time of one hour ?