No Internet when enabling DHCP

[diepnt90]

Have a question or an idea? Please search it on our forum to make sure it was not yet asked. If you cannot find what you had in mind, please submit it here.

Prerequisites

Please answer the following questions for yourself before submitting an issue. YOU MAY DELETE THE PREREQUISITES SECTION.

• [ v] I am running the latest version
• [v ] I checked the documentation and found no answer
• [ v] I checked to make sure that this issue has not already been filed

Issue Details

• Version of AdGuard Home server:
  • AdGuard Home v0.107.0-b.13
• How did you install AdGuard Home:
  • downloaded from this github and installed by ./AdGuardHome -s install
• How did you setup DNS configuration:
  • Turned off DNS and DHCP on router (openwrt) then installed AGH and enabled DHCP
• If it's a router or IoT, please write device model:
  • Raspberry Pi 3 Model B
• CPU architecture:
  • armv6
• Operating system and version:
  • Pi lite os

Expected Behavior

DHCP works and can access the internet

Actual Behavior

DHCP works but no internet access

Screenshots

Hi,

I installed AGH on my PI. It can give PC, mobile IPs but these devices do not have internet access.

I tried to install an old version like https://static.adguard.com/adguardhome/release/AdGuardHome_linux_arm.tar.gz and it worked well but the newest version does not work.
You can see my screenshot

Please help. Thank you.

Screenshot:

Additional Information

[diepnt90]

[bntsp]

Can you please check if the DNS Server is answering correctly and which IP is resolved for www.google.com.

[diepnt90]

@bntsp
Yes, it resolves to incorrect IP

Below is the static configuration for Pi OS

Example static IP configuration:

interface wlan0
static ip_address=172.16.10.214/24
#static ip6_address=fd51:42f8:caae:d92e::ff/64
static routers=172.16.10.1
static domain_name_servers=8.8.8.8

Also below are images for errors I could see when checking the DNS upstream server. Please help to check. Thank you so much!

[EugeneOne1]

@diepnt90, the gateway IP doesn't seem to be within the same subnet. Is that the intention?

We've introduced some changes to the DHCP server's behavior during the v0.107.0 cycle (See #3443, #3538). Briefly, the list of DHCP options returned within the lease is now expanded to satisfy the RFC-2131. It says that all the requested options should be returned with either explicitly configured value or the default one. So the problem may be caused by unexpected values in the lease.

Could you please try to specify the subnet mask to cover both 172.10.10.1 and the range for leases. The minimal one would be like 255.224.0.0

[diepnt90]

@EugeneOne1

I changed the local LAN IP to 192.168.10.1 255.255.255.0 and AGH works fine now.

But I think 172.16.10.1/24 255.255.255.0 is the correct setup and should work :D

[EugeneOne1]

@diepnt90, what do you mean by "local LAN IP", what exactly did you changed?

But I think 172.16.10.1/24 255.255.255.0 is the correct setup and should work :D

This is the correct setup itself, the problems begin when you're trying to work outside of a single subnet.

[diepnt90]

@EugeneOne1

Internet -> my modem -> PI

So my change the LAN of the modem from 172.16.10.10/24 to 192.168.10.10/24

[EugeneOne1]

@diepnt90, are other settings remained the same? If it works with the address of AGH's host being 192.168.10.10, gateway IP being 172.10.10.1, and leases range being 172.16.10.100-172.16.10.200?

[diepnt90]

Hi @EugeneOne1

Change IP range 192.168.10.1/24 with gateway192.168.10.1

before it was 172.16.10.1/24 and gateway 172.168.10.1

all are the same just change the LAN IP range on openwrt of my modem

[EugeneOne1]

@diepnt90, we'll close the issue for now since it seems to be resolved.

Please note that all the addresses (gateway IP, interface's IP, and leases range) are intended to be in the same subnetwork (covered by the network mask). We've introduced some validations about it in #3529.