Route10 Firmware 1.5c Released

  • Add support for PBR over WireGuard VPN connections
  • Add support for LACP connections over LAN and WAN
  • Add support for Tailscale
  • Add support for Custom Update Windows

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.

LACP is here!! I want to connect both 10G ports to an existing 10G core router (not Alta, sorry). I assume - except for the necessary wiring - I just add a port to the configured port and choose LACP mode. Is there anything else required to setup a working Route10?

Yep - that is how you do it. I set it up and things are working well.

Is Tailscale hardware accelerated?

Tailscale uses WireGuard protocol, which is not hardware accelerated. You can still get 800 Mbps+ with WireGuard on Route10, though.

@Alta-Jeff is it possible to bond 2 route10 2.5g ports with 2 S8 POE ports? I don’t normally do this but with the uniqueness of Alta products, just thought I would ask.

What I REALLY need is a 2.5g switch with S8 form factor. :thinking:

Yes, you can bond two Route10 ports to 2 S8 ports using LACP. Of course, it has all of the caveats of LACP, wherein you would only get 2 Gbps aggregated speed, and based on hashing, half of the clients would use one line, whereas the other half would use the other line.

Well I bonded the route 10 to a couple of switches and ran into issues. After about 2 hours of troubleshooting, I got everything working (so far). I thought I would post my experience in case it could help someone else

The first bond was the 2 10G ports on the Route 10 to a core switch. I have a VLAN 99 which is an NNI (default-route) for all the networks behind the Route 10. I have the native vlan as 99 since I don’t have Alta’s management vlan exposing my equipment behind the router. I could not get the bond to pass traffic until I set the allowed vlans to none.

The 2nd bond was between the route 10 and an S8 (which has a AP6 hanging off of it). The wireless network is isolated from the enterprise for now. I set the route 10 L2,L3 to LACP combine 7,8 on S8 with both connections setup. After multiple tries which resulted in no traffic passing - I set the Aggregation mode on Route 10 to active-passive and everything started working. Not sure what is going on there but I assume the S8 is using LACP mode.

Is there a way to roll back to 1.5c? Today I got the update to 1.5d, and my 2 Gig connection is now speedtesting at 400 U/D, from the Alta device. Normally it tests at 970 U/D.

It’s most likely to be due to some other issue, based on the negligible changes between 1.5c and 1.5d. I’d recommend reaching out to support and they can help you downgrade for an A/B test, but I’d be very surprised if 1.5c makes any difference. 1.5b->1.5c did have quite a bit more changes, and would be more likely to have introduced a regression, if there is any.

@Hanz thanks for the report. What you’re describing isn’t the intended effect. I think you’re hitting a race condition that we didn’t encounter until after release, which can leave the bond interface(s) in a bad state. It’s not something I can reproduce locally, but I was able to find a system that could reliably reproduce it, and fixed all the issues. When hitting that problem, another config change can fix it by reapplying the configuration. So those subsequent config changes didn’t directly impact the bond, they just indirectly happened to make it work by reapplying the config. I suspect you’ll get consistent, expected results on the next release.

The expectation is the mode must be LACP when linked up to an Alta switch with aggregation enabled on the ports. Active-passive is for scenarios where your switch doesn’t support LACP, or you want to connect to two different switches for switch redundancy.

@Alta-cmb Thanks for your follow up on this. I had to disconnect the bond between the R10 and S8 since it was very unstable. You are correct that when I reapplied the config, it would connect. I’m glad you were able to track down the issues and get them fixed

The 2 10G ports on the Route 10 connected to a core switch is still active. The bond will not negotiate when I restart the R10 but if I change the speed settings between default and 10G, it activates the R10 10G ports.

Looking forward to the next update!