For PIA, you basically have this today since PIA works with FQDNs for the server address and not IPs.For example, I have mine VPN setup to disconnect everyone on the network upon vpn going down on the current server.
Would have a secondary server or the option to list more if your current one goes down that can just automatically connect to the next server listed.
Going to remove pertist-tun totally forgot about that setting, so many keep track of. Thanks JohnFor PIA, you basically have this today since PIA works with FQDNs for the server address and not IPs.
First, check your custom config section and make sure it doesn't contain 'persist-tun' (I removed this from the autogen'd config a while back). Technically, this shouldn't be necessary, but I don't think PIA has configured their servers to fully support it correctly.
Then, since it's resolving via FQDN, it should automatically try a different server IP if the original server has gone down. I've actually seen it do this on my system.
So if I am on AC68U I need to use this option or no option if I choose 1.1.1.1 DNS?So, right now I'm thinking of removing the old DNSCrypt v1 and replacing it with DNS over TLS support. ARM users who want DNSCrypt can use @bigeyes0x0 DNSCrypt installer (it should work on my fork, but needs to be tested). MIPS routers, sorry, no more DNSCrypt, but you should get DNS over TLS.
It works either on or off, so why not turn it on? Personally, I haved turned it on.So if I am on AC68U I need to use this option or no option if I choose 1.1.1.1 DNS?
Whom may concern: https://www.asus.com/us/support/Article/925/
For example I opened my n66u to put a sdcard into it (not that it matters now, since the warranty expired a long time ago).
I wonder if this extends to the software as well, since I have this FW on the router for a very long time now.
First time I ever saw the warranty requirements made less strict...So in short: they can no longer refuse to provide warranty service just because you have opened your router. At least in the US - laws might differ in other countries.
If the DNS server supports DNSSEC, you should select it. This will use DNSSEC if available, but not fail the DNS requests if it gets a bad DNSSEC response. You should also use the strict option, which will fail the DNS request on a bad DNSSEC response (this will become the default in the next dnssmasq release).So if I am on AC68U I need to use this option or no option if I choose 1.1.1.1 DNS?
It’s not, really. The law was already this way (stickers/opening a device don’t really invalidate the warranty), they’re just actually enforcing it for a change.First time I ever saw the warranty requirements made less strict...
First time I ever saw the warranty requirements made less strict...
How is this relevant to this thread?Official RT-AC66U firmware revamped to: 3.0.0.4.382.50470
ARM users who want DNSCrypt can use @bigeyes0x0 DNSCrypt installer (it should work on my fork, but needs to be tested). MIPS routers, sorry, no more DNSCrypt, but you should get DNS over TLS.
@john9527 Any indication when the next release will be? Considering there hasn't been a commit in the last couple of months on Github.
I'm considering switching to your firmware for my AC66U, but I'm debating if I should go for stock or this build.
John has a different workflow from me, he only commits to Github after he issues a new release. So, nothing unusual with lack of recent Git commits.
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!