Add support for forcing proxied DNS traffic over DoH
Improve Let’s Encrypt certificate renewal
Improve stability of VLAN acceleration under load
This update is being rolled out now. You can manually initiate the upgrade if you’d like, or it will automatically update overnight (if auto-updates are enabled). The complete, up-to-date changelog is available here:
If you have questions, feedback, or run into any issues, feel free to reply here or start a new topic. Including configuration details or relevant logs where possible helps us troubleshoot and respond more quickly.
Noticed that with 1.5i with no schedules configured, the firmware re-runs /cfg/post-cfg.shevery minute. The log shows the schedule check failing each cycle and then deleting /var/run/.schedules, so the next check fails the same way. Is this intended?
I just wanted to jump in and let you know that for me it is working as intended. Tested with couple of public DNS providers and I haven’t had any issues.
Edit: Seems like there might be compatibility issue with certain DoH providers. Quad9, Clean Browsing and Mullvad does not work for me. Cloudflare, ControlD, Adguard, OpenDNS seem to work. Removed the original post and previous edits as they seem to be wrong.
I’m unsure if this is the issue but after no issues with reboots last night the unit said their is an update. This morning it’s on and lights going but no internet.
Repowering it has not fixed it and unfortunately I’m off site so will investigate later.
I have no way of knowing if it attempted an update and had an issue or it’s something else.
I’m also experiencing a periodic post-cfg.sh trigger. As a quick fix, I have updated my init scripts in this file to execute only once even when post-cfg.sh is repeatedly triggered.
I think I found why Quad9 fails. Since 1.5h the firmware runs https-dns-proxy with -x, which forces HTTP/1.1 (the router’s curl has no HTTP/2 support), and Quad9 refuses HTTP/1.1 with an HTTP 505. Cloudflare and Control D answer over HTTP/1.1, which fits what you saw. I haven’t tested CleanBrowsing or Mullvad, but I’d guess they’re the same. With Force DoH off you’d never notice, because dnsmasq falls back to the ISP’s DNS.
@MapleBaconPoutine good call, thanks for posting. I changed this for the next Route10 release to enable HTTP/2 in curl and https-dns-proxy. It was using -x previously because we didn’t have HTTP/2 support at the time. It works with Quad9 with those changes.