@admon would you be able to point me to the correct resource?
It worked (Somewhat).
After unchecking dns for vpn and dns for vpn guest, AdGuard Home shows the client IP address instead of localhost
I then go to VPN Dashboard of GL-iNet (/#/vpndashboard), updated the Proxy Mode from Global Proxy to Based on Client Device. Checked the VPN on the device that is on the exclude list, it can successfully do DNS look ups and bypasses VPN no problem. However, ALL dns requests to AdGuard Home now show as localhost. Even after I revert the Proxy Mode to Global Proxy doesn't help.
I then navigate to /cgi-bin/luci/admin/network/firewall/forwards, changed nothing but clicked Save & Apply and Voilà! Client IP now show up in AdGuard Home again...
I could solve my problem that only localhost / 127.0.0.1 was shown as client by cleaning up the firewall settings as suggested by @slesar , but now I have only IP adresses without hostname in the AdGuard Home log and also the top client list:
Any idea how I can display the hostnames next to the IP address again?
Somehow turning AdGuard Home off and on again solved my issue at first.
Without VPN I had it already running perfectly: AdGH showed IP with hostname and local LAN hosts connected via DHCP were visible in DNS (provided by AdGH without manual entering the name).
Sadly that all broke now after I tried to setup a WireGuard Server to connect from my smartphone and I cannot bring it back to life even after disabling VPN. I try to figure out the reason.
@slesar I wanted to avoid manual setup of all local hostnames, since (with a few exceptions of static IP services) they should already be known by Flint2 when they get their network via DHCP by the Flint2 router.
Yes correct. Adguard home listen in luci DHCP. You could turn off DHCP in luci/LAN network range in GL gui and turn on Adguard home DHCP server. Should be auto name each devices🤔
you're at the same point that I'm. So question: if from Lucy -> /luci/admin/system/startup we set a restart for Adguard service, it should work right ? ( in case you have scheduled a reboot at midnight) but from my side it didn't work, the command I set is: "/etc/init.d/adguardhome stop" then ....start but nothing happened. Tonight I will set it twice just for testing then I'll let you know, if someone have any workaround I'll be pleased, thx.
