thomas
-
Posts
76 -
Joined
-
Last visited
Content Type
Profiles
Forums
Downloads
Store
Gallery
Bug Reports
Documentation
Landing
Report Comments posted by thomas
-
-
1 hour ago, Nephilgrim said:
Same here with PiHole when VM is on too. Webpage is unaccesible until I shutdown any VM that is running.
Not even able to ping the IP of pihole docker.
Edit: Just noticed that after 30 seconds i disabled Wireguard plugin everything started to work. Can someone confirm same behaviour?
Indeed, if you stop the wireguard you can access the webpage of the Adguard docker.
-
I have the same issue. The docker works fine until I start the VM. After that the web page is not accessible and I can't even ping it. I have to stop the VM and then the docker start working again and responding to pings. Docker is configured to use Custom : br0 with a unique IP and the VM is using a different fixed IP.
Before updating to 6.8.0 -rcX was working fine.
-
Changed Status to Closed
-
Thanks. I'll check it.
-
When will be the new RC ready to test it?
Also I have seen that even if I can ping 8.8.8.8, there is no "next" release available...
Thanks
-
Pinging 8.8.8.8 for internet alive, I don't think is the best practice. Maybe you should ping the first DNS server, that is defined, if it's external, or resolve an internet domain using 2 different DNS servers, from different providers...
- 1
-
See below the results
root@unRAID:~# traceroute 9.9.9.9
traceroute to 9.9.9.9 (9.9.9.9), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 16.803 ms 16.798 ms 16.794 ms
2 * * *
3 * * *
4 149.248.92.141 (149.248.92.141) 34.132 ms 34.142 ms 41.240 ms
5 woodynet.torontointernetxchange.net (206.108.34.115) 41.204 ms 41.201 ms 41.197 ms
6 dns.quad9.net (9.9.9.9) 39.981 ms !X 15.685 ms !X 20.601 ms !X
root@unRAID:~# traceroute 1.0.0.1
traceroute to 1.0.0.1 (1.0.0.1), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 16.792 ms 16.785 ms 16.779 ms
2 * * *
3 * * *
4 149.248.92.141 (149.248.92.141) 25.321 ms 25.323 ms 25.318 ms
5 he.ip4.torontointernetxchange.net (206.108.34.112) 26.868 ms 26.869 ms 30.658 ms
6 198.32.181.56 (198.32.181.56) 33.326 ms cloudflare.ip4.torontointernetxchange.net (206.108.34.208) 17.442 ms as13335.toronto.megaport.com (206.53.203.8) 18.906 ms
7 1dot1dot1dot1.cloudflare-dns.com (1.0.0.1) 17.367 ms 17.353 ms 17.349 ms
root@unRAID:~# traceroute 8.8.8.8
traceroute to 8.8.8.8 (8.8.8.8), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 12.698 ms 12.693 ms 12.688 ms
2 192.168.1.254 (192.168.1.254) 3003.381 ms !H 3003.391 ms !H 3003.389 ms !H
root@unRAID:~# traceroute 8.8.4.4
traceroute to 8.8.4.4 (8.8.4.4), 30 hops max, 60 byte packets
1 192.168.1.254 (192.168.1.254) 12.723 ms 12.722 ms 12.718 ms
2 192.168.1.254 (192.168.1.254) 3005.614 ms !H 3005.617 ms !H 3005.620 ms !H -
Unfortunately DD-WRT is not that smart. What I wanted to accomplish is all the devices that have google DNSs as default, to revert to the one that is running in the network. Those rules accomplish that. If I'm checking the DNS requests using the google DNSs they timeout.
-
Destination LAN NET Subnet Mask Gateway Flags Metric Interface default 0.0.0.0 1xx.xx.x.x UG 0 WAN 8.8.4.4 255.255.255.255 192.168.1.254 UGH 2 LAN & WLAN 8.8.8.8 255.255.255.255 192.168.1.254 UGH 2 LAN & WLAN 1xx.xx.x.x 255.255.255.224 * U 0 WAN 169.254.0.0 255.255.0.0 * U 0 LAN & WLAN 192.168.1.0 255.255.255.0 * U 0 LAN & WLAN Those IPs are redirected to the router's IP, but this shouldn't matter as I'm using different DNSs.
-
This is the result from the command and it looks ok.
root@unRAID:~# cat /etc/resolv.conf
# Generated DNSv4 entries:
nameserver 9.9.9.9
nameserver 1.0.0.1
# Generated DNSv6 entries:I have a dd-wrt router with a static route for 8.8.8.8 and 8.8.4.4. As soon I remove those the update starts working...
[6.8.0-rc3] Can't enter the Adguardhome docker webpage if vm is on
-
-
-
-
-
in Prereleases
Posted
After more testing it seems the option "Local gateway uses NAT: Yes" is the problem. If you choose "No" the docker works properly and it seems that I can still connect through Wireguard to my server