For me, AdGuard is working fine on RT-AC68U, but I want to change the adguard homepage port number, mine is assigned http://192.168.0.1:14711/#, I used AMTM for installation.
Edit /opt/etc/AdGuardHome/AdGuardHome.yaml change that number to the port you want.For me, AdGuard is working fine on RT-AC68U, but I want to change the adguard homepage port number, mine is assigned http://192.168.0.1:14711/#, I used AMTM for installation.
I speak to soon. Youtube ads is back. It only takes day for youtube realize ads fail to play and switch iver to some other ip or domainNope. This was tested on my iPad and android tablet and Samsung smart TV and nvidia shield.
They are so your browser don't auto DoH and skip using adguardhome. What is not to understand? We are telling dnsmasq to honor blocking auto doh. If it pleases everyone I will remove them.On my RT-AX86U, Asuswrt-Merlin 386.4, everything seems to be working fine with AdGuardHome installed, although I haven't yet tested all combinations. However, I cannot figure out one of the pre-configured settings. Under "DNS Settings/Upstream DNS Servers", I don't understand the following entries:
[/use-application-dns.net/]192.168.1.1:553
[/dns.resolver.arpa/]192.168.1.1:553
I'm using the router's DHCP service, and my LAN uses 192.168.50.xxx. Should the entries above reference 192.168.50.1:553? If not, how do these lines work?
The values configured in "Private reverse DNS servers" are using 192.168.50.1 as expected.
I wouldn't use it for dhcp, it would not suitable as dhcp for asuswrt merlin router functions.How can I let agh take over DHCP on ipv4 and IPv6? I think that would be best way to control IPv6 on device base.
Yeah but IPv6 is letting ads pass. Because the IPv6 adress change.I wouldn't use it for dhcp, it would not suitable as dhcp for asuswrt merlin router functions.
Ipv6 is blocked with universal ::, I haven't seen any ads pass. If you want to use dhcp, you have to disable your router's dhcp, once that is done you must turn on adguardhomes. It is a very sticky process that could really muck things up. (Probably break aimesh too.)Yeah but IPv6 is letting ads pass. Because the IPv6 adress change.
You can define client rules by their address then. Ipv6 addresses can be controlled by changing your router configuration from stateless dhcp6 to stateful.Thing is, I need some devices that need the ads.. so it should be device specific.
Hmm do you have more info on that.You can define client rules by their address then. Ipv6 addresses can be controlled by changing your router configuration from stateless dhcp6 to stateful.
That is all you need.Hmm do you have more info on that.
I only see a start and end op pool
And how will the IPv6 get assigned then. Cause I don't see any way to give a client a IPv6 adresThat is all you need.
I'm just not understanding why the entries are for 192.168.1.1:553, instead of for 192.168.50.1:553. If this is the way it's supposed to work, it's fine. I wasn't asking for you to remove them.They are so your browser don't auto DoH and skip using adguardhome. What is not to understand? We are telling dnsmasq to honor blocking auto doh. If it pleases everyone I will remove them.
Okay I will fix it.I'm just not understanding why the entries are for 192.168.1.1:553, instead of for 192.168.50.1:553. If this is the way it's supposed to work, it's fine. I wasn't asking for you to remove them.
Okay I pushed a fix, change yours to match .50. But I fixed it in the installer.I'm just not understanding why the entries are for 192.168.1.1:553, instead of for 192.168.50.1:553. If this is the way it's supposed to work, it's fine. I wasn't asking for you to remove them.
Thank you!Okay I pushed a fix, change yours to match .50. But I fixed it in the installer.
Yea i just wasn't understanding you had a different local ip. I failed to take that into account on one of my late night hotfixes.Thank you!
No problem. 192.168.50.1 is the default for the RT-AX86U, and I think for the earlier RT-AC86U as well, so I imagine others have this situation, too. I'm not aware that it caused any issues in my LAN.Yea i just wasn't understanding you had a different local ip. I failed to take that into account on one of my late night hotfixes.
Welcome To SNBForums
SNBForums is a community for anyone who wants to learn about or discuss the latest in wireless routers, network storage and the ins and outs of building and maintaining a small network.
If you'd like to post a question, simply register and have at it!
While you're at it, please check out SmallNetBuilder for product reviews and our famous Router Charts, Ranker and plenty more!