Route10 Firmware 1.3l Released!

The latest Route10 firmware is here, bringing a range of enhancements and new features, including:

  • IKEv2 VPN Server support
  • Alta DDNS support (hover over device IP to see).
  • Add support for RADIUS-assigned VPN IP address.
  • Add support for domain-name search option.
  • Add support for routing jumbo frames.
  • Add support for L2TP and IKEv2 VPN from multiple WAN interfaces.
  • Add support for historical switch port stats.

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.

1 Like

Nice! When can we expect having a wireguard implementation? I’m looking forward to be able to actually use my route10 :slight_smile:

I have everything updated. I have logged out of the controller and logged back in. I have cleared browser cache. I still do not see the DDNS entry for route10.

Same here!

IVEv2 works from my laptop. It does NOT work from my iPhone. it connects for one second, then disconnects.

Can you please double check the Remote ID? If that is incorrect for me, then it will behave exactly as this. I left the IPSec ID field blank, so for me Remote ID is just the full DDNS hostname.

Open Route10 card, go to VPN, IPSec Server Open, and it should be listed as Certificate, like here:

1 Like

I left my remote ID blank as well… and it just shows “vpn”.

When I hover over the address for Route10, I also do not see a DDNS address anywhere

Safe to assume your Route10 is running 1.3l? Probably a stupid question, but just in case. :slight_smile:

Can you please cat /var/log/messages | grep uacme and share /var/log/uacme.log via DM? It should contain relevant info to debug.

To my knowledge the only place to view the cert name is within the IPSec Settings card, at least at this present time.

Thanks for the logs! I just marked them as deleted so that your hostname wasn’t permanently on display. This issue should actually be fixed. You’ll need to restart your Route10. Once you do that it should properly retrieve the cert and show the DDNS hostname in Control. Please let me know either way.

Sounds good, and thank you. Once I am done with the web meeting I am in, I will reboot and try again.

1 Like

No problem!

I see the DDNS address in the VPN setup now… but this is contrasting to the firmware release notes as shown below:

  • Alta DDNS support (hover over device IP to see).
1 Like

Glad to hear it’s working now!

Oh, good point. Apparently I need more coffee. I can confirm this isn’t working here at this time. Checking on that, I’ll follow up. Thanks!