I decided to give the RPI a break for a little while. I wanted to see how well AGH is running on the router. Seems pretty stable other than occasional CPU thrashes (the GO garbage collector (GC) choosing more CPU usage in preference to router memory optimizations). The CPU thrashes seem to not hinder the normal function of the router. I am sure this would be a problem if too many filters or lists were utilized though, but using the default AGH filters seems to have no critical impact to router functionality. In other words, this is probably as good as it gets running it directly on the router.I have a few clients attached only, test setup. Wanted to see what's the complaint about.
Looks like that was it. Need to review what DNS Director does and would also like to get DNS encryption working. I cannot imagine it is as simple as a checkbox. Thanks again.For your userland case it is rather simple, LAN > DHCP > DNS should be blank. Otherwise you are forcing clients to use a different DNS other than the router VIA DHCP option, and they are being "redirected" by the firewall to use the router instead. That is why clients appear to be 127.0.0.1. Why you would put those DNS servers in your LAN-DHCP is beyond me, but that is why your client namespace resolution is broken. This is the consequences of making executive decisions.
and would also like to get DNS encryption working
Heres the stats from 4 days running straight.And the result:
View attachment 54613
DNS-over-HTTPS to OpenDNS.
If you ask some questions tomorrow I may not have the setup running anymore.
yes, me too, i ended to unistall all and reconfigure all from the beginnin, probably some incompatibility with the new yaml file.Newest update projectile shirt everywhere today and had to redo my config file - minor inconvenience I guess, no biggie.
Thankfully it backs itself up before overwiriting - I've quite an extensive list of ipset stuff in there.yes, me too, i ended to unistall all and reconfigure all from the beginnin, probably some incompatibility with the new yaml file.
Thankfully it backs itself up before overwiriting - I've quite an extensive list of ipset stuff in there.
yes, me too, i ended to unistall all and reconfigure all from the beginnin, probably some incompatibility with the new yaml file.
What is the output ofI have installed Unbound on AX6000 and latest Merlin with AdGuard, but I'm getting an error with IPV6 UPstream. I believe I did everything as I did in the original post, but something is off. Would really appreciate some suggestion how to resolve it.
Server "[::1]:5653": could not be used, please check that you've written it correctly
Server "tcp://[::1]:5653": could not be used, please check that you've written it correctly
netstat -nlp | grep unbound
Maybe answer my question first.nothing. I have this unbound installed https://github.com/dave14305/Unbound-Merlin-UI
netstat -nlp works just fine and provides output
And while I have your attention do I need to install Unbound from amtm if I had the one above already?
Sorry it is case sensitive, I meant.Apologies if I wasn't clear.
This command netstat -nlp | grep Unbound produces no results
View attachment 54753
netstat -nlp | grep unbound
Unbound only listens on 127.0.0.1 using my old add-on, not ::1. Shouldn’t matter for local queries within the router.nothing. I have this unbound installed https://github.com/dave14305/Unbound-Merlin-UI
netstat -nlp works just fine and provides output
And while I have your attention do I need to install Unbound from amtm if I had the one above already?
I don't know if you intended to,Unbound only listens on 127.0.0.1 using my old add-on, not ::1. Shouldn’t matter for local queries within the router.
prefer-ip6: yes
actually makes it try to avoid processing queries over ipv4. Not sure if this behavior is best when all instances of IPV6 are available. A simple " do-ip6: yes" would be most sufficient.Sorry it is case sensitive, I meant.
netstat -nlp | grep unbound
This is to make sure you are using the correct addresses in AGH upstream for AGH to communicate to unbound through.
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!