Not able to make AGH running on Raspberry Pi 4B with Raspian Bullseye 11 64 bits on it

[diegofrances]

Hello All,

I have installed Raspbian OS Desktop 64 bit (Debian 11 Bullseye) on a Raspberry Pi 4B. I have followed the guide explained at "https://github.com/AdguardTeam/AdGuardHome?tab=readme-ov-file#automated-install-linux-and-mac" but unfortunately I am not able to make it working.

When I send a request from the browser on the Raspbian, the AGH works as expected but when I point other machines to use the Raspberry Pi as the DNS server it does not work. I have taken a trace using Wireshark at client side and I can see the DNS queries reaching the Raspberry Pi but no action from the AGH is seen.

I have also noticed that when I run "netstat -atunp | grep 53", only tcp6 and udp6 are listening on port 53. Even I have disabled IPv6, I am not able to make it working on IPv4 so that's why I believe it is not working.

Can somebody please help me here?

Willing to share any log if need. I've ran out of ideas.

Thank you in advance.

Regards

[ghost]

G'day!

In the .yaml, could you please tell me which interface AdGuard Home is listening on by pasting the parameter for bind_host?

[diegofrances]

Hello,

I have reinstalled and instead of selecting all interfaces to listen on port 53, I have selected only the IPv4 one and now I can see the service listening on port 53 but unfortunately I am facing the same issue as I have described before, it only works on the local machine.

Please find the first lines of the yaml file:

http:
pprof:
port: 6060
enabled: false
address: 0.0.0.0:3000
session_ttl: 720h
users:

• name: username
  password: encrypted_password
  auth_attempts: 5
  block_auth_min: 15
  http_proxy: ""
  language: es
  theme: dark
  dns:
  bind_hosts:
  • 192.168.3.20
    port: 53

The above seen IP is the IP of the Raspberry Pi.

netstat -atunp | grep ":53 "
tcp 0 0 192.168.3.20:53 0.0.0.0:* LISTEN 164237/AdGuardHome
udp 0 0 192.168.3.20:53 0.0.0.0:* 164237/AdGuardHome

As you can see, the DNS config is as expected:

When I try to test it, it fails:

In opposition, when I ran the request from the Raspberry Pi, it works:

[ghost]

Are the queries coming through to the query log from that client?

[diegofrances]

Hello,

Unfortunately that's the issue that I am facing. Even if the IP of the device where the AdGuard is running is answering the DNS queries as per below image, the added block or any other rules are not being honoured.

No entries at the AdGuard for the SandBox IP:

SandBox's Config pointing to the IP where the AdGuard is running on:

But as I said, any request coming from the Raspberry Pi itself is being analysed and filtered if need:

Content of "dhcpcd.conf":
interface eth0
static ip_address=192.168.3.20
static routers=192.168.3.1
static domain_name_servers=192.168.3.20
noipv6
static domain_search=

Do I have to set the IP of the Raspberry out of the DHCP range of my Ubiquiti's Dream Router in order to work? Could that be the issue?

Thank you all for your collaboration.

[diegofrances]

Hi All,

I have been able to make it working but only for the devices sitting on the same VLAN/Subnet as the AdGuard. I have a Unifi Dream Router and even if I can exchange ICMP and DNS traffic between clients on different VLANs, the DNS requests coming from a different subnet/VLAN different from where the AdGuard is, is not being honoured.

I need to investigate further with UniFi Team.