Mine was like that at first. You have to ssh in and type "runner_disabled=0" then reboot. From then on, as long as no incompatible features are enabled, runner will stay on.It's weird, I have an AC86u too, with just a basic config, no qos, and i've never seen the "runner" enable
Just an FYI....I'm liking the cache change so far. Seems to have improved the dnsmasq failure stats for me.The cache fix however might possibly resolve some random resolution failures in his opinion. He's been testing it for a while, and will merge to my repo in the coming days, so I can also test it on my end.
I discovered what looks like a bug in 384.7_beta3 on my 86u (also existed in previous versions I think, but didn't pin it down until after installing beta3). I normally keep hw acceleration 'runner' enabled, and the webui tools menu shows it as enabled. However if just click on the webui 'adaptive qos' tab on the left (not actually changing any settings there), runner becomes disabled. I am aware that enabling adaptive qos is incompatible with runner, however I think simply reading the qos page(s) and not changing any settings should not trigger a runner disable. Runner should not be disabled until an incompatible setting is actually applied. When this happens to me, rebooting the router re-enables runner.
Is anyone else having this problem? Not sure if it's something that can be fixed, or if it's locked inside a closed source blob.
In case it matters, I'm also running the latest diversion+skynet+pixelserv_beta, some other scripts to add a local ntpd and block webcam wan access via iptables, and an openvpn server... and aiprotection, qos, traffic stats, and ipv6 stuff is all disabled.
Not for me .just opening adaptive QOS tab and runner is disabled, rebooting router fix it.
It is working with openvpn, but I can't use openvpn because someone is trying to hack my router through this port an kills my router memory (I don't know how to protect my 1194 port so I disabled it).
This is not the answer you're looking for... but if openvpn server is working for you, changing the default port on the server might be your best solution at the moment.
There are 65000 ports to choose from just make sure you up above 2000 to be safe.What are
Does anyone know of good alternative ports to use instead of 443 or 1194? Ports that get scanned less.
Does anyone know of good alternative ports to use instead of 443 or 1194? Ports that get scanned less.
Changelog of dnsmasq 2.8test7 as per Merlin update.Loaded and testing 384.7_beta3-gc44f112e3 and all seems to work well. All my pages load without delay and no problems with vpn or add blocking, what would you like specifically tested?
EDIT: DNSSEC is working as expected as well.
dig 202.59.245.173.in-addr.arpa +trace
I'm unable to run this command from my router. Do I need to install Dig?dig 202.59.245.173.in-addr.arpa +trace
Do I need to install Dig?
opkg update
opkg install bind-dig
Need install from entwareI'm unable to run this command from my router. Do I need to install Dig?
-sh: dig: not found
Yes.
Code:opkg update opkg install bind-dig
Yup that worked. Does this verify that dnssec is working or am I looking for a different command?Need install from entware
opkg update ; opkg install bind-dig
Does this verify that dnssec is working
+[no]trace
Toggle tracing of the delegation path from the root name servers for the name
being looked up. Tracing is disabled by default. When tracing is enabled, dig
makes iterative queries to resolve the name being looked up. It will follow
referrals from the root servers, showing the answer from each server that was
used to resolve the lookup.
I believe this test just observes if your DNS server of choice can handle DNSSEC. It doesn't check the function. As an example: disable DNSSEC on LAN page and then go back to the above mentioned site. You will see that when the test is run it still gives you thumbs up. Further if you leave DNSSEC disabled and enter your ISP DNS (if it is like mine it doesn't support DNSSEC yet) and run the test again...now it fails as the DNS server of choice no longer supports DNSSEC. That the way it seems to me IMHO.If you want to verify DNSSEC is working, just visit https://dnssec.vs.uni-due.de/ for example, and press 'Start test'.
Loaded and testing 384.7_beta3-gc44f112e3 and all seems to work well. All my pages load without delay and no problems with vpn or add blocking, what would you like specifically tested?
Interesting is the “dig +trace” command working.
Example of command
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!