mirror of
https://github.com/AdguardTeam/AdGuardHome.git
synced 2026-03-04 00:01:12 -05:00
DHCP listing duplicate IP's for same device #5884
Labels
No labels
P1: Critical
P2: High
P3: Medium
P4: Low
UI
bug
cannot reproduce
compatibility
dependencies
docker
documentation
duplicate
enhancement
enhancement
external libs
feature request
good first issue
help wanted
infrastructure
invalid
localization
needs investigation
performance
potential-duplicate
question
recurrent
research
snap
waiting for data
wontfix
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/AdGuardHome#5884
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @nishikant on GitHub (Jan 17, 2026).
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Custom (please mention in the description)
Installation
Custom package (OpenWrt, HomeAssistant, etc; please mention in the description)
Setup
On a router, DHCP is handled by AdGuard Home
AdGuard Home version
Version: 0.107.71
Action
DHCP should assign a IP only once to a MAC.
Expected result
No IP conflict and single IP assignment
Actual result
Additional information and/or screenshots
My setup is ISP (192.168.1.1) -> Raspberry PI 5 (192.168.1.5 [wan] & 192.168.3.1 [lan]) -> eero mesh (bridge mode: 1 main and 2 extenders). Adguardhome runs on Openwrt installed on Raspberry pi 5. DHCP runs on 192.168.3.1 and is supposed to assign IP's to all devices.
@tjharman commented on GitHub (Jan 17, 2026):
I don't see any duplicates there? They're the same MAC address assigned to the same IP. Yes, the hostname has changed but there's no IP Address conflict or actual problem here, is there?
Or do I miss something?
@nishikant commented on GitHub (Jan 17, 2026):
This throws error on device trying to connect. It throws IP already assigned message. Don't have a screenshot of that.
I have switched to dnsmasq dhcp for now.
@tjharman commented on GitHub (Jan 17, 2026):
What is throwing the error? If AdGuardHome can you upload the log file please?
@nishikant commented on GitHub (Jan 19, 2026):
Will try to capture adguardhome logs and share.
@tjharman commented on GitHub (Jan 19, 2026):
This sounds like you have some other device handing out DHCP addresses. What does your routers arp table show?
Are you sure you didn't statically set an IP address somewhere?
I am almost certain this is a local network problem and not an AdGuardHome issue.
Did you just turn off one DHCP server and then turn on AdguardHomes? That would cause this.
@tjharman commented on GitHub (Jan 29, 2026):
Hi - any progress on this one?
@nishikant commented on GitHub (Jan 30, 2026):
I switched the dhcp to adguardhome and faced same issue. I could not figure out how to enable dhcp logging in adguardhome. So I found a work around for this problem.
I am running this on openwrt, where the data directory is in /tmp, and it gets wiped after every reboot.
option work_dir '/adguardhome'
And things seems to be stable.