I have attached terminals to both the wg-easy container on the one machine and the AdGuard container on the other, and I have determined that the wg-easy container is able to reach the AdGuard machine over the network, but the reverse is not true. I understand that I am pursuing a form of split tunnelling here, and so I have checked that the default wg-easy IP address range (10.8.0.x), which I am using, doesn't conflict with my local subnet (192.168.68.0/24) so far as I understand. I took the advice of an old Reddit post I came across and added 192.168.68.105/32 to my AllowedIPs list to ensure that DNS traffic was also being routed as advised here, but this did not fix the issue. In effect, this means that I can freely access the internet and I am also able to access devices on the same local network via their IP addresses, but I am not able to access these devices by their hostnames. Something else that may be of interest or perhaps unrelated is that while a forward DNS lookup will run without issue, the reverse is not true, and nslookup is unable to resolve the IP addresses it produces back to hostnames. ![]() The other sever, despite having its hostname specified in the same place in my AdGuard settings, is not. There is an exception to this experience that may point to a fault with AdGuard rather than with Wireguard: Only the device that hosts the AdGuard server is accessible via HTTP/HTTPS, SSH, and ICMP when using its hostname. If I use nslookup, however, the process reports that it is using the DNS IP I have specified (that of the AdGuard machine) and the hostnames are resolved without issue (which is why this SuperUser post doesn't answer this question, despite its similarity). Over SSH or ICMP, the processes inform me that they could not resolve hostname/find host. In a browser, I am given an ERR_NAME_NOT_RESOLVED. When I try to use the hostnames I have configured in the AdGuard DNS rewrite page over SSH, HTTP/HTTPS, or ICMP (when pinging), the DNS fails to resolve the hostname. I am having the following problematic experience when connected to the VPN from a remote network: ![]() On this local network, I am running another Ubuntu 22.04.1 LTS server on a separate machine as an AdGuard Home DNS provider, also via a docker container. When my Windows 11 client connects to the Wireguard server, I am able to access both the internet and my local network over the VPN. I use portainer to manage my docker containers. I am using an Ubuntu 22.04.1 LTS server to run wg-easy.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |