pi-hole:development-v6
← pi-hole:new/dhcp_ignoreUnknownClients
opened 05:07PM - 30 May 24 UTC
# What does this implement/fix?
Add new `dhcp.ignoreUnknownClients` option wh…ich has been requested on Discourse. It works as follows:
![Screenshot from 2024-05-30 19-04-33](https://github.com/pi-hole/FTL/assets/16748619/71cd3710-dbca-4b1b-864f-c7a7c748f1be)
This PR also features a second commit updating forgotten changes into `test/pihole.toml` and adds a CI test to prevent forgetting to update this file in the future.
---
**Related issue or feature (if applicable):** https://discourse.pi-hole.net/t/add-checkbox-to-block-dhcp-for-unknown-hosts/70485
**Pull request in [docs](https://github.com/pi-hole/docs) with documentation (if applicable):** N/A
---
**By submitting this pull request, I confirm the following:**
1. I have read and understood the [contributors guide](https://docs.pi-hole.net/guides/github/contributing/), as well as this entire template. I understand which branch to base my commits and Pull Requests against.
2. I have commented my proposed changes within the code.
3. I am willing to help maintain this change if there are issues with it later.
4. It is compatible with the [EUPL 1.2 license](https://opensource.org/licenses/EUPL-1.1)
5. I have squashed any insignificant commits. ([`git rebase`](http://gitready.com/advanced/2009/02/10/squashing-commits-with-rebase.html))
## Checklist:
- [x] The code change is tested and works locally.
- [x] I based my code and PRs against the repositories `developmental` branch.
- [x] I [signed off](https://docs.pi-hole.net/guides/github/how-to-signoff/) all commits. Pi-hole enforces the [DCO](https://docs.pi-hole.net/guides/github/dco/) for all contributions
- [x] I [signed](https://docs.github.com/en/authentication/managing-commit-signature-verification/signing-commits) all my commits. Pi-hole requires signatures to verify authorship
- [x] I have read the above and my PR is ready for review.