Hello, I bought this router almost a month ago and I'm still amazed at everything it can do.
Yesterday I decided to reset it and start my configuration from scratch.
I noticed that when connecting via the guest network on the wireless, it is not possible to resolve DNS via IPv6 if AdGuard is enabled.
Enable AdGuard Home: ON
AdGuard Home Handle Client Requests: ON
IPv6 Mode: Native (I don't know if this has any influence, since the guest will always use NAT6)
So, if you try something like:
nslookup google.com 192.168.9.1
It works perfectly.
However, if you try something like:
nslookup google.com fd8b:1234::1
It will time out.
I'm not sure if this was really the expected behavior.
PS: Remember to adjust the network addresses to their respective values.
PS2: It would be great if it were possible to adjust the ULA IPv6 network prefix. I saw that it is possible to adjust it through the LUCI interface, but changing it there, there are places that are not changed together, such as the glipv6 file.
bruce
2
According to your information, I try to reproduce local.
WWAN: IPv4 + IPv6 connected
Router ADG enable, IPv6 enable with Native
Router local (192.168.8.1) IPv4 + v6 both ok.
In the client (pc), connect to the guest wifi, ping domain name and v6 address:
In the client (pc), connect to the main wifi:
Seems to not reproduce the issue, please check
- how about if the IPv6 can address?
- did you also enable other features or modify other configurations?
Right now I have a lot of changes, but when I found the bug, I reset the router and reproduced with the minimum possible.
You can ping it, but you can't use to do a nslookup.
Also I didn't make my self very clear. My router is dialing a pppoe connection, I'm not using it as a repeater, not sure if that matters.
I attached a few pictures.
Let me know if you can reproduce it, if not, I can reset the router again do the changes and export a config. Is that ok for you?
But the problem is not the ping, it is the DNS resolution that fails on IPv6 using the guest network.
`s
n this photo:
In the first test, I was connected to the wireless guest network.
In the second test, I switched to the main wireless network (cable also works).
In other words, the DNS server is working, but there must be some firewall rule that is preventing it. I didn't get to look into it much, because it was already late and I needed to restore the router so that people wouldn't kill me in the morning when there was no internet 
bruce
6
That is ok, both WWAN or PPPoE is just the way for the WAN.
My router has not any changes, same as the previous post, enable ADG (default configuration) + IPv6 Native + Guest WiFi
The CMD nslookup works well.
Seems some problem is in the DNS service of your router?
Reset to firmware, only enable ADG (default configuration) + IPv6 Native + Guest WiFi, see if the nslookup works? or what ADG configure?
Update: I reproduced it.
DAMMITTTTTTTTT
When I received the email this part is not there, so I did a full reset and video of 10 minutes. Ops!
(Hint: always check if the post has been updated first)
Anyway, I will send you a PM with the link for the video and the router config exported. It may help.
PS: Please ACK that you have received my PM.
bruce
8
Yep, thanks for your conformation. 
I have reproduced this issue, will submit to the R&D.
system
Closed
10
This topic was automatically closed 180 days after the last reply. New replies are no longer allowed.
