AdguardTeam
Adguard Home on UDM Pro no ARP Clients in List
Prerequisites
-
[X] I have checked the Wiki and Discussions and found no answer
-
[X] I have searched other issues and found no duplicates
-
[X] I want to report a bug and not ask a question
Operating system type
Other (please mention in the description)
CPU architecture
Other (please mention in the description)
Installation
Docker
Setup
Other (please mention in the description)
AdGuard Home version
v0.107.9
Description
Hello everyone, installed Adguard Home on my UDM Pro with these instructions:
https://github.com/AdguardTeam/AdGuardHome/issues/2809 e.G. This one: https://github.com/unifi-utilities/unifios-utilities/tree/main/AdguardHome
Here I had problems at first, because a DNS error occurred all the time. The remedy was that I also copied the 20-dns.conflist file to /etc/cni/net.d/.
Adguard Home can now be called up as normal via http://... and also works perfectly, except that only rDNS entries are visible under Client Settings but no ARP`s... On the start page, however, you can under Top Clients see these ARP entries...
This isn't a big bug in my opinion, but it just bothers me a lot that you can't see these entries. I have also tested Adguard Home running on a Raspberry and there were no problems here... Can anyone help?
Sorry for my English but it's easier for me with Google Translator.
PS: Please step by step if possible, because to be honest I only know the basic commands with Linux and I usually get on by trying things out.
Unfortunately, all beginnings are difficult ;)
Good day, and apologies for the long silence. Please enable verbose logs and look for error messages related to ARP.
Also, you can write messages in any language. For most languages, we'll be able to understand it.
Hallo ! Danke für die Rückmeldung. Kämpfe nur gerade damit, in dem Podman Container den Verbose Log Datei Pfad zu setzen ... Habe die AdGuardHome.yaml geöffnet (Vorher natürlich per podman stop adguardhome) den Container gestoppt und den Pfad wie im Beispiel /tmp/aghlog.txt gesetzt... und container wieder mit podman start adguardhome gestartet.
unter /tmp/ finde ich leider dann keine log datei...
Gruss
Unfortunately, I don't have any experience with Podman, but if it's like all other containerization software, you should also make sure that both the configuration file and the new log file are in a directory that is mounted somewhere. With Docker, this is usually done using the -v flag, like docker run … -v /tmp/:/tmp/.
(Übersetzt mit DeepL.)
Ich habe bedauerlich keine Erfahrung mit Podman, aber wenn es wie jede andere Containerisierungssoftware ist, sollten Sie auch sicherstellen, dass sowohl die Konfigurationsdatei als auch die neue Protokolldatei in einem Verzeichnis liegen, das irgendwo eingehängt ist. Bei Docker wird dies normalerweise mit dem -v-Flag gemacht, wie docker run ... -v /tmp/:/tmp/.
Sorry für die späte Rückmeldung. Werde heute Abend folgende Konfiguration versuchen:
podman run -d --network dns --restart always
--name adguardhome
-v "/mnt/data/AdGuardHome-Conf/:/opt/adguardhome/conf/"
-v "/mnt/data/AdGuardHome-Work/:/opt/adguardhome/work/"
-v "/mnt/data/AdGuardHome-Cert/:/mnt/data/proxymanager/letsencrypt/":ro \ # Test for Cert to Nginx hope works in RO
-v "/mnt/data/AdGuardHome-Logs/:/tmp/" \ #Test for logfiles Path
--dns=127.0.0.1 --dns=1.1.1.1
--hostname adguardhome
adguard/adguardhome:latest
Hoffe mal jemand kann hier drüber schauen, ob dies so richtig ist, dann werde ich dies heute Abend mal testen.
Habe auch noch festgestellt, dass ein ARP Eintrag vorhanden ist, dieser aber nur auf den Gateway des Netzwerks verweist: 10.0.5.1 – ARP. Eventuell hilft das weiter.
Gruss
The volumes look mostly correct. Another thing that could shed light on the issue is running command arp -a -n both on the host machine as well as in the container. This is the command that AdGuard Home uses to fetch this information.
(DeepL)
Die Volumes sehen größtenteils korrekt aus. Eine weitere Möglichkeit zur Klärung des Problems ist die Ausführung des Befehls arp -a -n sowohl auf dem Host-Rechner als auch im Container. Dies ist der Befehl, den AdGuard Home verwendet, um diese Informationen abzurufen.
Have you been able to resolve this issue ? I have the same problem, only the router IP is showing up. I had the same problem when running adguard in a container on server. I think the issue is with Adguard setting or UDM or UDMP setting. Just hasn't figure it out yet.
Hi ! No, unfortunately I haven't solved the problem myself, but since it's only an "optical" thing, I haven't looked further for it yet. But I'll probably start again one of these days, unless you find a better solution ;)
I don't know if it's the same issue you are facing than me. But I put the DNS into my Wan (internet) configuration instead of the LAN (network), so it was the router asking the request to Adguard instead of the clients. So that's why it was showing only 1 client. (The clients need to be restarted for this to take place on most router).
