stubby failing to start due to Bus error. AC3100 from a3.
Any other AC3100 owner with the same issue? I don't have one so I can't test it.
stubby failing to start due to Bus error. AC3100 from a3.
#i tested it on my AC3100, but i did a complete factory M&M before doing so because i came over from stock, i didnt experience this issue-- maybe that is the best recommendation.
what is the official names for the files that the system recognizes for customizing stubby?Any other AC3100 owner with the same issue? I don't have one so I can't test it.
only possible issues i have noticed in the past couple of weeks is issues with adaptive QOS failing to actually start even though it shows the logs for it, but this only was happening on beta 3 from what i noticed.A bus error usually indicates either a corrupted firmware image, or failing hardware. I wanted to be sure it wasn't the first one, since it seems to have happened a few times lately (first with Asus's own RT-AC68U release a few weeks ago, and also to an AC88U test build I did for myself a few days ago).
Why do you think DNSSEC in the webui is broken? Please if you would explain.but in this case the gui dnssec should be characterized as broken because of how it chooses to validate.
because of the general use is overkill, based on where it is placing options for dnssec. it is telling dnsmasq to do dnssec then also telling stubby to do it and then also telling it to be handled by the server as well.Why do you think DNSSEC in the webui is broken? Please if you would explain.
He doesn't understand validation is different from proxy...Why do you think DNSSEC in the webui is broken? Please if you would explain.
First I will confirm that the stubby.yml has the needed instruction to get dnssec extensions true. But no where do I see proxy-dnssec in any file associated with the process. Having Stubby take the extensions is no problem and never has been.because of the general use is overkill, based on where it is placing options for dnssec. it is telling dnsmasq to do dnssec then also telling stubby to do it and then also telling it to be handled by the server as well.
You are correct, I looked closer and it is in dnsmasq.conf.i confirm that having the command for stubby to do dnssec isn't a problem, but also having proxy-dnssec inside dnsmasq.conf at the same time is .
You are correct, I looked closer and it is in dnsmasq.conf. I removed it and bounced dnsmasq and still no issues. I'll reboot now and get back to you.
in reality they should setup the three option system -like john's forkReboot worked without issues. @RMerlin @themiron clearly the proxy-dnssec does not need to be there, if using the webui settings.
you can remove it using a helper script in dnsmasq.postconfThe instruction in dsnmasq.conf (proxy-dnssec) cannot be removed at this point of development, it keeps being restored.
Yes, They are being written to: appdata_dir: "/var/lib/misc"Curious to know if anyone has looked to see if the system is writing the trust anchor files to disk when using the
dnssec_return_status: GETDNS_EXTENSION_TRUE
setting. I saw the files early in my testing of the Stubby installer and saved a backup. But was never able to reproduce having Stubby create the trust anchor files in the appdata_dir folder again. DNSSEC appeared to work okay without the anchor files. If no appdata_dir is specified, the system defaults to the .getdns directory.
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!