You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've set up an ADH container on my Mikrotik router and it works fine for IPv4 addresses, but not for IPv6.
As a result, I can't reach any IPv6 upstream DNS servers.
Server "https://[2001:4860:4860::8888]:443/dns-query": could not be used, please check that you've written it correctly
The container has a valid IPv6 under the router.
# ip -6 add show dev eth0
2: eth0@if4: <BROADCAST,MULTICAST,UP,LOWER_UP,M-DOWN> mtu 1500 state UP qlen 1000
inet6 fd08:192:168:8:9cd3:83ff:fec8:599b/64 scope global dynamic flags 100
valid_lft 2591995sec preferred_lft 604795sec
inet6 fd08:192:168:8::5/128 scope global
valid_lft forever preferred_lft forever
inet6 fe80::9cd3:83ff:fec8:599b/64 scope link
valid_lft forever preferred_lft forever
I can ping LAN IPv6 addresses, but not remote ones.
Then I realized that the container does not have a default IPv6 gateway set up.
04-22 23:33:40 container,info,debug 2024/04/23 02:33:40.190436 [error] dnsproxy: upstream tls://[2620:fe::fe:10]:853 failed to exchange ;domain.name.tINt AAAA in 3.148431845s: getting conn to tls://[2620:fe::fe:10]:853: connecting to 2620:fe::fe:10: dial tcp [2620:fe::fe:10]:853: connect: no route to host
# ip -6 route show
fd08:192:168:8::5 dev eth0 metric 256
fd08:192:168:8::/64 dev eth0 metric 256 expires 0sec
fe80::/64 dev eth0 metric 256
ff00::/8 dev eth0 metric 256
Only if I manually add the default route, it can reach IPv6 addresses.
ip -6 route add default via fd08:192:168:8::1 dev eth0 metric 1
However, if the router is rebooted or the container is reset, the default route is lost.
My assumption is that it should have set the default route dynamically.
Any idea why it is unable to add the IPv6 default route?
The text was updated successfully, but these errors were encountered:
Prerequisites
I have checked the Wiki and Discussions and found no answer
I have searched other issues and found no duplicates
I want to report a bug and not ask a question or ask for help
I have set up AdGuard Home correctly and configured clients to use it. (Use the Discussions for help with installing and configuring clients.)
Platform (OS and CPU architecture)
Linux, ARM64
Installation
Docker
Setup
On a router, DHCP is handled by the router
AdGuard Home version
0.107.48
Action
Tested upstream servers and IPv6 was unreachable.
# ping 2800:3f0:4004:807::200e PING 2800:3f0:4004:807::200e (2800:3f0:4004:807::200e): 56 data bytes ping: sendto: Network unreachable
Expected result
Remote IPv6 addresses should be reachable.
Actual result
All remote IPv6 addresses are unreachable.
Additional information and/or screenshots
I've set up an ADH container on my Mikrotik router and it works fine for IPv4 addresses, but not for IPv6.
As a result, I can't reach any IPv6 upstream DNS servers.
The container has a valid IPv6 under the router.
I can ping LAN IPv6 addresses, but not remote ones.
Then I realized that the container does not have a default IPv6 gateway set up.
Only if I manually add the default route, it can reach IPv6 addresses.
However, if the router is rebooted or the container is reset, the default route is lost.
My assumption is that it should have set the default route dynamically.
Any idea why it is unable to add the IPv6 default route?
The text was updated successfully, but these errors were encountered: