Route10 Firmware 1.4h Released!

Routers
,
1

Focused enhancements and key fixes are now available in the latest Route10 firmware release.

  • Add option to disable DoH.
  • Improve adherence of manually configured IP addresses.
  • Multi-WAN: Resolve remaining issues with sticky connections after failover/restoration.
  • Resolve issues with alternate acceleration.
  • Improve system stability with DPI enabled.
  • Resolve issue with incorrect daylight savings calculation on IPS/IDS event timestamps.
  • Remote syslog: Use UTC for all timestamps (previously, local and UTC time zones could be mixed).

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:

As always, if you have questions or encounter any issues, feel free to reply here or start a new topic. Please include details about the issue so we can assist you effectively.

2 Likes
2

Thanks for all the hard work team. Installed. No issues to report thus far.

4 Likes
3

Thanks @Alta-MikeD and everyone! Figured I’d just get this question out of the way real quick since it’ll probably be asked otherwise: where exactly is the option to disable DoH? I don’t need it myself at this moment but I’m just curious where it’s at (I also might be blind :grin:)!

Otherwise so far so good on my end!

2 Likes
4

It’s found under Advanced on the Ports section. If it’s not showing up, try a refresh without cache. Cloud only until the next Control tag is released.

image
image355×670 27.1 KB

1 Like
5

Roger! That was going to be my next step and I just hadn’t had a moment to do it yet. Can confirm it’s sitting right there under advanced. Thanks again!

1 Like
6

Installed, and over the moon - DoH toggle works lovely!

1 Like
7

Everything’s fine, but where can I modify the available DoH servers?

1 Like
8

When is DDNS for Cloudflare going to be fixed?

When setting the hostname in the GUI, it automatically sets the following in the config:
option domain ‘randomHex@example.com’
option lookup_host ‘randomHex@example.com’

The cloudflare script works perfectly as it parses the option domain ‘randomHex@example.com’ correctly. It gets the domain, sub domain, zone ID and sets the IP. The issue is the lookup_host as its not a FQDN and the ddns script errors getting an IP during its checks. I have to manually go into the config, change the lookup_host to randomHex.example.com & restart ddns service. Then evrything works fine.

Now setting the hostname to randomHex.example.com causes a different issue where the cloudflare script fails because zone ID is missing. If done this way, I have to add the zone ID option to the config.

I migrated from an openwrt router and the hostname/domain was separate from lookup_host when configuring ddns. Either add this to the interface or the ability to add custom option lines. I’m not sure why this hasn’t been corrected yet.

9

@Alta-Jeff

Thank you for taking the feedback and providing a suitable solution! Great to see Alta takes feedback seriously!

Can confirm the events tab is now reporting the time correctly!

1 Like
10

Thanks for the update regarding DoH! - @Alta-Jeff, @Alta-MikeD :man_bowing:

Since we’re on the topic of this, do you think this feature would be considered: Feature Request: DoT and/or DoH for Route10? Since we’re using our own custom DNS, I wonder if we could just set the DoH server directly?

Thanks again!

3 Likes
11

Has anyone else had issues with adding new wireguard remote-user peers after this update?

I can create a new peer but when I download the config the endpoint is undefined in the .conf. “Endpoint = undefined:51820”
I know I could just edit the .conf and add the public IP but having to manually do so defeats the purpose of being able to email a config or simply scan the QR code.

Also I cant seem to find the system hostname anymore “*.ddns.manage.alta.inc” when opening the card for the Route 10.