Adguard Home DHCP Issue

[Saku241]

Issue Details

• Version of AdGuard Home server:
  • v0.106.3
• How did you install AdGuard Home:
  • curl -sSL https://raw.githubusercontent.com/AdguardTeam/AdGuardHome/master/scripts/install.sh | sh
• How did you setup DNS configuration:
  • Load-balancing
• If it's a router or IoT, please write device model:
  • Raspberry Pi 3 Model B
• CPU architecture:
  • ARM64
• Operating system and version:
  • Raspbian 10

Actual Behavior

I got a problem with the DHCP of Adguard Home. I disabled my router's DHCP and Adguard DHCP seems to work fine with WIFI devices because they are granted an IP BUT for Wired devices (RJ45) they never get an IP.
I actually have to add every MAC addresses of wired devices to manually assign IP to each. It kinda works but sometimes when I turn on my computer, it takes a while to get an IP (approx. 30s-2m).

My IP Range is 192.168.1.2 to 192.168.1.126, subnet 255.255.255.0 and lease 86400sec

Additional Information

I added the MAC addresses of my devices in client section but I cant determine the device if it's an other IP, I thought it would be able to identify with only the MAC Address

[ainar-g]

Hello. Are you sure that your router processes both wired and wireless connections using a single DHCP server? Also, can you configure verbose logging, and try connecting and disconnecting the wire? Thanks!

[Saku241]

Hello. Are you sure that your router processes both wired and wireless connections using a single DHCP server?

Not sure but my router got basic dhcp options

I’ll try the verbose and update ticket

[Saku241]

Adguard acting weird after verbose set to true

log_compress: false
log_localtime: false
log_max_backups: 0
log_max_size: 100
log_max_age: 3
log_file: "/home/pi/logs"
verbose: true
schema_version: 10

No logs are written + all devices are getting weird ip (169.254.95.36)

[ainar-g]

Please make sure that AdGuardHome is actually up. For example that the web interface is shown and that you can see DNS queries on the Query Log page.

[Saku241]

Adguard is on but there's no query as devices didnt get a correct local ip. If I put back verbose false and log_file "", Adguard start working as normal.. Anything wrong with the log_file directory ?

[ainar-g]

Are you sure that /home/pi/logs is a file and that AGH can access it?

[Saku241]

Are you sure that /home/pi/logs is a file and that AGH can access it?

Oof I thought it was only a directory not a file...

So here's verbosse logs :

• https://paste.ee/r/9oUYh/0 Here, I got my local ip (192.168.1.22) with static lease in approx 30-45sec
• https://paste.ee/r/1A2v0/0 Here, I removed the static lease only for 2c:f0:5d:60:34:79. It seems to loop and I never received the supposed 192.168.1.10, I never got internet on my pc at this state.

After that I manually put 192.168.1.10 as my ip and 192.168.1.2 as dns and Adguard could identify my pc in clients BUT in statistics, there is 2 instances : Bryan-PC (192.168.1.22) and Bryan-PC (192.168.1.10), they should be merge as it is the same client just on different ip, isnt it ?

[Saku241]

Any update since ?

[ainar-g]

Hi, sorry for the delay. It seems like the machine just doesn't accept the IP for some reason and resends DISCOVER immediately after receiving an IP from AGH. Were you able to make sure that there are no other DHCP servers in the network?

Also, could you try to either increase the icmp_timeout_msec parameter in the configuration file to 3000 or decreasing it to 250? Perhaps that IP is already taken, but AGH cannot see that.

[Saku241]

Hi, sorry for the delay. It seems like the machine just doesn't accept the IP for some reason and resends DISCOVER immediately after receiving an IP from AGH. Were you able to make sure that there are no other DHCP servers in the network?

Also, could you try to either increase the icmp_timeout_msec parameter in the configuration file to 3000 or decreasing it to 250? Perhaps that IP is already taken, but AGH cannot see that.

Yep i'll try that but as I said, its not the only machine, every machine with a ethernet connection does this.
I'll try that and give you updates

[Saku241]

So I tried 3000 and 250 and it changes absolutely nothing.
On Adguard/#dhcp it clearly show me that I was supposed to have 192.168.1.10 with a lease but my machine never get that ip assigned.
I had to add a static lease to get it work again

It's a real mess to understand why static lease works but not auto... and even worse to understand that it applies only on ethernet connections

[hoshsadiq]

I think I have the same issue. None of my devices were able to connect earlier. I had to switch off AGH's DHCP, re-enable DHCP on my router, connect my devices, then re-enable DHCP on AGH.