Substantial Route 10 firmware imminent as Q2 approaches

Hi All,

Based on the post linked below I suspect a Route 10 upgrade is imminent that should tackle most if not all of the following promised features:

• IPsec Site to Site
• L2TP+IPsec Client
• Dynamic DNS Client
• Static Routes
• Advanced features: Match Source MAC, mark, DSCP
• DPI

I would like to take the opportunity to thank @Team for their continued work in progressing the Route 10’s software to align with its impressive Hardware features.

1 Like

While we continue to work hard every day on completing every post-launch feature that has been promised, there is no official ETA. We are targeting end of Q1, but it is not a hard deadline. Thanks for your continued patience and understanding as we finalize each feature release in turn.

1 Like

Q2 starts tomorrow.

1 Like

@Alta-Josh
As stated the team’s hard work is appreciated but considering Q2 starts tomorrow are we now to assume that the Q1 your are targeting is Q1 2026. This is where a published roadmap containing ETA’s for each of the post - launch features would prove invaluable to the team and the community. Everyone then has a clear understanding of what to expect.

Richard

I apologize for any confusion of our targeted release period. It is an estimation, not a deadline. When this estimate is missed, it does not follow that the remaining unfinished development would shift to the same quarter of the following year. Instead, the target period will be the very next quarter, hopefully early and not late.

Thanks for your understanding to expect that the feature development may require a longer timeline and that we do not have hard deadlines for release.

3 Likes

I guess, Static Route would be in the next release ?

Honestly I really wish they would work on fixing basic functions that are broken rather than working on new features. Disconnected devices STILL show in the connected device list.

I agree @DN3092 ,

There is alot of the current features broken as documented in the forum. I would assume though that this would be Two independent teams (one working on new features the other concentrating on fixing existing issues) but still enough callaboration between the two to forecast where issues could potentially arise in the work being produced by each group.

Richard

1 Like

I’d be very surprised if there’s a separate bug fixing team. It’s too small a company and too young a product. (Even then having separate teams is probably a bad idea.) They presumably have a separate release and dev code line, but this early on they may never actually make changes on the release line - unless they mess up and have to make an immediate patch.