Hello,
I am trying to make a very simple setup, raspberry pi connected with ethernet to the internet running adguard on docker as dns only and a network manager hotspot. My problem is that every time you create a hotspot with network manager it spins up its own version of dnsmasq to run as dns and dhcp. The problem is that due to adguard binding on port 53 dnsmasq dns fails to start and the hotspot isn't working. I've seen that you can disable dnsmasq's dns by creating a file /etc/NetworkManager/dnsmasq-shared.d/disable-dns.conf and adding port=0 inside it. The problem is that if I do that dnsmasq's dns stops but then if you connect to the hotspot no internet even though adguard is running. Has anyone done something simillar? I cannot find any solutions.
I am trying to make a very simple setup, raspberry pi connected with ethernet to the internet running adguard on docker as dns only and a network manager hotspot. My problem is that every time you create a hotspot with network manager it spins up its own version of dnsmasq to run as dns and dhcp. The problem is that due to adguard binding on port 53 dnsmasq dns fails to start and the hotspot isn't working. I've seen that you can disable dnsmasq's dns by creating a file /etc/NetworkManager/dnsmasq-shared.d/disable-dns.conf and adding port=0 inside it. The problem is that if I do that dnsmasq's dns stops but then if you connect to the hotspot no internet even though adguard is running. Has anyone done something simillar? I cannot find any solutions.
Statistics: Posted by steveiliop56 — Sun Jun 09, 2024 8:59 am — Replies 0 — Views 9