A new firmware release is now available for Route10, adding expanded monitoring and telemetry capabilities, enhanced VPN visibility, more granular security and routing controls, and improved platform compatibility and reliability.
WAN Status: Add support for displaying Starlink telemetry.
Add support for PBR fallback and drop targets.
Add configurable IPS/IDS categories.
Add support for displaying VPN client statistics (in Devices Page).
Add support for displaying AltaConnect VPN Groups Status.
WAN Status: Improve Speed Test results.
Improve reliability with some SFP+ transceivers.
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.
Thanks! No problems to report here. Appreciate being able to see connected VPN clients, although as a small note I think it would be nice to be able to better identify them at a glance. The cloud icon works I think, but maybe something that specifically show’s “VPN” in some way? Just thinking out loud!
This may or may not be intended behavior: When rebooting for this update, FRRouting customized settings for OSPF were reset, causing all adjacent neighbors to fail detections. I had to manually reapply the settings prior to functionality being restored.
Custom settings applied:
frr defaults datacenter
ip ospf hello-interval 1
ip ospf dead-interval 4
@twitchytoes the config is provisioned so long as it gets uploaded to the controller. That happens when vtysh exits, if you tell it to do so. I’m guessing you probably opened the terminal, made the config, and then didn’t exit vtysh. Or exited vtysh and told it not to save.
I am guessing exiting vtysh is probably where I went wrong. I think when I did some of the edits in the dynamic routing tab, I just exited the terminal with the close button. I did, however, write the config. Not sure if I can replicate this with reboots or if it’s only with a firmware update.
Edit: Yep, I definitely didn’t exit at the end. I see the config uploaded when I just did, so that explains the trouble.