Route10 Firmware 1.3z Released!

We’ve just launched an updated firmware for Route10 that brings new capabilities and a key fix:

  • Add LAN subnet selection to initial setup process.
  • Improve firewall rule handling when protocol is not specified.

Note: Multi-WAN and load-balancing were not included in this release due to an internal communication issue. We have taken corrective steps to prevent similar oversights, and we appreciate your patience and understanding.

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.

12 Likes

Thank you team.

What happens now if a firewall wall rule protocol is not specified? Does it add one or more automatically?

1 Like

It sets it to all. Before it was leaving it blank - which openwrt for some reason was treating as two iptables rules; one for UDP and one for TCP. I can confirm that this is fixed for me.

5 Likes

Thank you for adding the initial subnet setting. I’ve been worrying about how I could ever recover from factory settings if I had to without installing another router to route between the default initial subnet and the one I use that includes my controller.

2 Likes

Have any of you been able to get the load balancing to work? I’ve set both WANS to the same metric (tried different options), with no luck… one of the ISP/WAN ports simply does not get loaded… all the traffic is going through the other WAN. In previous firmware versions the failover worked very well, but no such luck on the load balancing. I spoke with someone from the Support team and it looks like the current algorithm is for each devices to select a WAN and stay with it… so the load balancing is per client connected and not per session regardless of the client… Hopefully there is a later update to allow the same client to access both ISPs or WAN connections

  • Add LAN subnet selection to initial setup process.
    Thank You Team Alta - this will really help when adding a Route 10 into existing setup.

:+1:

4 Likes

Thank you!!

2 Likes

I have the same problem. Starting a ping on a client, forcing failover by disconnecting the cable to the primary WAN port. It won’t change to the secondary connection. I’ve tried both with equal metrics and non-equal.
Were you able to solve this issue?

unfortunately no, I reached out to the ALTA LABS team and waiting on their proposed solution… I hope that they are able to make changes to the software and allow the users to do more customization on the load balancing feature…I only need the router for that feature as a multi-gig load balancing wired router. The failover works great and very fast when each WAN port has a different metric. However, as load balancing the current algorithm only has it to match or assign each WAN to a client or MAC address and not per sessions or true round robin. Will update once I hear back

Pretty sure I have completed what you’re looking for, I just haven’t been able to test it yet. I made a rather large discovery while building the script, and this explains what you’re seeing even more, as well as @Seb.

The mwan3 package actually wasn’t included in 1.3z, so multi-WAN/load-balancing is not currently working at all. I am not sure the status of failover either, as I haven’t tested it—it may not work, which touches on what @Seb is seeing.

We’re already building a fixed firmware, which includes another big update. More to come soon. I’ll also follow up via your ticket shortly.

5 Likes

This is a pretty big miss, that just re-enforces another post where I commented on lack of rigor and process around pushing updates to the managed portal.

When you have a firmware release for your primary router, where the 1st feature listed in the very terse release notes is multi-WAN and WAN failover, but somehow “forget” to include the OpenWRT module that is handles MWAN, there is a problem. Whether it is a QA problem, a release control problem, or just a simple human mistake, it is a problem.

Alta Labs is wanting people to spend hundreds, if not thousands, of dollars on their hardware. This is not an open source project run by volunteers or a hobby project of someones, this is a company that claims they are not a startup, that is competing in a very competitive market. I have serious concerns over the lack of quantity and quality of documentation, but more serious and more concerning is the lack of quality and control on the software side. If Alta cannot properly manage firmware/software development and releases for their current hardware lineup, what is to be expected as you grow it with your upcoming products?

I know the fan boy club here will probably be upset at the “tone” of this post, I’ll state it again, this is not a run by volunteer project, this is a business trying to compete in a competitive market and I see no indication from Alta Labs that they are truly serious about bringing better products to market (this includes all aspects; hardware, software, performance and reliability). I’m sure it will be met with much criticism from this community as disrespectful to the Alta Labs team or whatever, but I’m calling it as I see it.

The point of this post is to provide feedback that the current state of quality will and has turned people away from their products. I honestly hope that Alta Labs will step back and take a hard look at the mistakes and mis-steps and start to build better processes, procedures and quality checks into the development processes. This includes making sure documentation is part of the release process and new features are documented at the time of release, proper controls on the management portal, etc. There is some first class hardware coming out of Alta Labs, but it is worthless without some first class firmware, software and documentation to go with it.

4 Likes

I certainly hope not, because there is nothing wrong with your tone here. I appreciate your feedback and am sharing this internally.

6 Likes

@techrider I appreciate your feedback. I find it interesting that in another thread that you have opted to pass on our products, but you remain active in our community. Which I do appreciate, for a number of reasons. First, we obviously have you interested enough to spend time with us. Second, feedback such as yours, either positive or negative, is vital to the way we build our products.

I agree that proper documentation is an area of improvement for us. Why this latest release happened the way that it did, with our documentation being misaligned, is something I am reviewing. We will learn from this and put appropriate steps in place to make sure it doesn’t happen again. I would also love to hear some examples of release documentation strategy and release windows, that you like and dislike from other manufacturers.

Regarding your opinions on our firmware and hardware, I would be curious how much you have used our gear if you have “passed” on it? For example, on the same post, you share both negative and positive reviews (“world class” - again, thank you) of the hardware. We have a large and expanding base of customers that deploy our products in all types of projects across the world. Varying from one AP, switch or router to multiple hundreds. Backed with rave reviews on our products, firmware, performance and support team.

If you’re willing to take the time with me, I would be love to hear what experiences you have had with our gear and where you feel we are falling short so we can use your feedback for improvement. Concurrently, as stated above, I would also greatly appreciate examples of documentation and release strategies you like and dislike. Either here in the open forum, via private message or on a call. Whatever works best for you.

5 Likes

Happy to share my experience and appreciate the engagement. For now, I am not comfortable using the AL stack in a customer environment, as I’ve mentioned in other threads. For evaluation, we have multiple APs (AP6s, AP6 Pros and 1 AP6 Outdoor), multiple switches (S8s and S16), Route10 and a local controller. Tested the cloud management, local HW controller and local hosted controller.

I have continued to keep track of progress as I’m hopeful to see another strong player in the market. You guys are new and may be having some growing pains, I’m optimistic to see something that makes me want to re-evaluate again.

The APs function very well, had good results with them in various setups. A note, I absolutely hate the mounting system, never could really master it. HW wise, worked well, but did have 2 failures out of 6 APs, so that was a bit concerning. Switches work, nothing really special to note about them, except the S8s did have an overheating problem as they were in a cabinet that wasn’t well ventilated - so I consider that a self induced issue on my end. The Route10 didn’t get much of a workout, it was so feature in-complete at the time that I really didn’t spend a whole lot of time on it. The HW local controller was a huge mess, struggled getting it setup on a test VLAN, the DDNS stuff was odd at best. A self hosted controller was much easier to setup, but it wasn’t clear on how to do the updates, once I realized I needed to manually do the apt update it seemed to function fine. I was a bit surprised at just how chatty all the devices were to outside IPs. The test environment was ultimately blocked from Internet access and the number of blocked attempts was huge.

The hardware appears solid, has a lot of capability using modern chips, good selection of ports on the Route10. As I mentioned, without solid firmware / management system, it makes the good hardware much less attractive.

Honestly, I never really liked the interface to the controller - most configurations take place in small pop-up windows. When you on-site and working off a 13" Macbook Air, seems like a poor design choice to leave so much un-used real estate on the screen. The change to allow those pop-ups to be enlarged was great and appreciated, why hasn’t it made it to the devices window?

If I pull up a AP from the Network tab - I can manage various settings as I would expect. But, there is a global AP setting for the Backup Network, which is under System → Advanced, where you have switch settings, user settings, control (if local) settings - all this random stuff bunched together under Advanced. Most of which, there is zero documentation on other than the tool tip. The Backup Network setting (which is ON by default) is a great example, you can find it referenced several times on the forums where it has caused an issue, but I do not believe there is anything in the Knowledge Article area about this one. As for this setting being enabled by default - it really is not clear that putting an IP address in the field is what enables it - why not make this a on / off switch? Some places use a toggle, others don’t - there is no consistency.

Under Settings - there is a Firewall and Networks area - if I only have APs deployed, these have zero use, but yet they are there with no indication how they relate (or don’t) to the hardware installed.

On the Devices tab - I can select a device connected to my network (for example, my Macbook). There is a setting under Advanced for UPNP - the pop-up states “Only required if UPnP Strict Mode is enabled” - I have no clue where that setting is located - after opening every single setting, I found it under Networks → WANs → WAN1 hidden under Advanced, where I had to actually enable UPnP before the UPnP Strict mode was exposed. Turns out, since I don’t have a Route10, this setting has no use for just an AP deployment.

These are just some quick examples of how the web interface to manage the environment needs some serious work or at least some documentation to make it clear what is what.

My take on the interface is that it wasn’t really planned out how it would grow as the hardware roadmap developed. Realtime stats are cool - but actually not very useful, what is useful is the ability to see the history, spot trends, do analysis.

A lot of this could be addressed with simple documentation. Most of this applies to the Route10 as it is the most dynamic area right now. IDS/IPS are the perfect example, there isn’t any actual documentation - or at least that is what I thought - nothing in the release notes (other that IDS/IPS released), nothing in the Knowledge area on the Alta.inc site. Turns out, there is a blog post that does provide some insight into the use and configuration of IDS/IPS, I just happen to stumble on it - why is this not in the knowledge article area?

Release notes should describe what is new, changed or removed and they should include enough details for everyone to understand the impact of the change. Take the most recent firmware for Route 10 - it states:

  • Improve firewall rule handling when protocol is not specified.

What does that mean? It was improved, but how? Did it fix a bug, did it modify how firewall rules are managed, what did it do? Was it not blocking before and now it is? It is very difficult to know just what changed and how it impacts me as an admin.

Another example:

  • Resolve issues with manually setting port speed.

An alternative way to write this (making some assumptions on what was actually resolved…)

  • Fixed an issue where you were unable to set the port speed on the Route10 manually. The port speed is now selectable and the setting will take effect immediately.

As for release schedules, maintenance windows, etc. You asked about other companies that do it well - Firewalla comes to mind. They have an MSP portal, iOS/Android apps and local firmware. I assume they maintain additional infrastructure to support a Early Adopter MSP portal. Before the MSP is updated, very detailed release notes are provided and you can select to opt in to the EA version. Use TestFlight (iOS) and whatever is the Android equivalent for their app testing (which I think you guys do already) and similar on their firmware, they have an opt-in EA capability to load EA firmware. What is most important, NOTHING changes on their MSP portal without announcements, release notes, before the actual release. Version numbers are clearly visible for everything so you know what version you are on, whether you are on an EA release, etc. I’ve personally had a Firewalla deployed in some form or fashion for years and have never been surprised about a feature or release.

Ubiquiti is another one that does a good job on release notes, maintains an EA channel (along with release candidates). I do have a full suite of Unifi equipment in my test lab that runs all the EA releases, allows me to know what is coming, what works (and what doesn’t ) before I ever have to put it into a production environment. Also allows me to provide feedback before something is final.

The distribution model that Alta Labs uses is also a bit concerning. I just did a quick check and found bundled deals on Amazon that are cheaper than what I would get through the 2 distributors I generally use. I could not find any bundle deals through the distributors. When you sell direct on Amazon and potentially undercut distributor pricing, that is not a model I want anything to do with.

There is a lot here - bottom line, everything Alta Labs has put out there works, no debating this. For home installs, it is a valid choice. For some small business I think it could be a good fit. For someone who sells, installs and manages (or supports the business person who is tasked with managing), it is just a little too risky for me because it isn’t well documented and things change without notice. I will take another look at the Route10 in the near future, as I mentioned, when we purchased and tested, it simply was not ready for prime time so we didn’t bother.

I am optimistic that things will continue to improve and innovate over time. I think having new options in the market place is a good thing. It is tough environment right now, seeing what Ubiquiti has brought to the market in the last month it is a bit overwhelming and I’m sure painful for those that want to compete with them. This is why I think it is so important to be the best across the board, strong hardware, solid software / firmware and great documentation. It is like a 3 legged stool, if just one leg is not up to speed, the entire stool is useless.

Appreciate the opportunity to provide feedback.

3 Likes

@techrider Thank you for taking the time to provide such comprehensive feedback. I look forward to the date were you are ready to re-evaluate our gear for your projects. I understand the need to feel comfortable putting your name and reputation behind a brand and we will earn that from you. In the mean time, I have the following for you:

Happy to hear you like what you saw with our APs and their performance.

As for the mount, were you using rounded screw heads to mount the APs to a surface or junction box by chance? More often than not, that is a primary cause for frustration with the mount as the tolerances are tight. Also, if you tighten the mount to a junction box to the point where it deforms a bit, it also introduces some headache. I also admit our mount needs some refinement. We are working on that now as it is, and we will have the mount out a little later this year.

On the failures, we have addressed this previously on the forum. Happy to reiterate here again that this was identified and isolated. It is no longer an issue going forward and should anyone have an issue stemming from this, even outside of our published 2 year warranty, we will stand behind them.

Are there specific features you are waiting to be released before you work with our Route10 again? If so, would you mind sharing what those are?

Is your preference an Alta Labs hardware controller, or a self hosted controller?

Regarding how “chatty” our devices are, was this just a surprise? Or is this a concern for you? Happy to have some follow up discussions here as well as to why this has been architected as it has.

Thank you!

We did not see a need to add this as the fields and data in there at present generally do not require a larger window. That being said, its an easy modification. We will get that queued up in a future release.

Do you feel the tool tip was not clear enough for the back up network then? We do have a knowledge base article on this and have for some time.

https://help.alta.inc/hc/en-us/articles/26752608198555-Alta-Guest-Backup-Network-Feature

Perhaps this was too hard to find, or not clear enough? Would you like to see a link in the tool tip to the KB article, or is just knowing the article exists is enough?

I am curious what you think about the back up network feature as well.

Interesting you bring this up now. We have been discussing this very thing internally as well. We are seeing an increased number of support calls regarding what these settings do, when a certain product is in use, without the other applicable products. We are trying to decide how to best update our UI to indicate when certain features are available or not, without cluttering things up, or making it overly complicated. We are taking this as an action item, as this does need to be addressed.

I see your point here. We need to improve tool tips and documentation here. We will take this as an action item.

We believe a combination of real-time and historical stats are important for management and troubleshooting. What do you think of our 2 day, 2 week and 2 month filter settings in the UI? Are these useful to you?

I am in agreement with you on our documentation. We can do a better job here, and we will. The IDS/IPS is a good example. This is an action item for us as well.

I also see your point here. We could do a better job explaining the bug or feature that is being deployed or fixed here. We will take this as an action item for future releases.

I appreciate you providing the examples I requested. We will certainly take these into consideration as we look how we can improve our own processes. Generally speaking, we do provide version numbers clearly on all the hardware and release notes, and if you are running a self hosted version, this is provided in settings. We also have recently deployed beta program for mobile app testers, for those that are interested. We also provide the ability for you to unenroll a site in automatic backups. Down the road a bit, we will have a complete EA program interested parties can enroll in.

Understanding that, is it fair to say that your frustrations with our release processes are the lack of advanced warning of an update, and the level of description provided in the release notes?

Is your concern our entire distribution model, or just the fact we have our products listed on Amazon? We take pride in the margin we are able to maintain for our registered installers, so I want to make sure we resolve any concerns here. We are selling on Amazon yes, but to use the authority granted us by Amazon to remove unauthorized sellers who have historically gotten in and eroded margins for us and our peers in the industry. The same applies for NewEgg. We have our sites set on ebay next. We want MSRP parity globally (where allowed by law) and we have no intention of undercutting our distributors.

I appreciate your optimism regarding Alta Labs. It’s well placed. You are correct in that we will continue to innovate and improve, as we strive to “elevate” the world of networking. The documentation and release improvements we have discussed here will happen sooner than you think.

As for competition in the marketplace, its healthy. We welcome it. If another manufacturer decided to introduce a number of products all at once that does not discourage or distract us. Rather, we remain focused on developing and delivering products that out perform our competition and that just work. Backed by our zero licensing strategy and support strategy, of course.

I did list some follow up questions above that I would love to hear back from you on. Should you have any additional feedback for me, now or at any time, I would love to have it.

Thanks @techrider

3 Likes

Good morning, appreciate the response. Below is the follow-up to your questions.

As far as I can tell, it looks like the Route10 is about to the point where it has most features needed. What I was trying to communicate was that at launch, it was not near a point of features to be of real use in a production environment. I know many were stated as “Coming Soon”, I guess the concern is what does that actually mean from a timeline perspective. The hype around the product generated some excitement, as I mentioned, it seems to be a good mix of hardware, but the let down at release and soon after was that it really couldn’t do what was needed for a production environment. I don’t recall exactly when it was actually released, but here we are in March of 2025 and it still cannot support failover WAN. I really can’t comment on how the IDS/IPS works or reporting capabilities as I no longer have the device to test.

For me, must have features would be: Multi-WAN with failover, IDS/IPS with comprehensive reporting. Region and application blocking (I know you can do app blocking at the AP level, not sure it is there yet in the Route10 or with wired connections), with comprehensive reporting on what is being blocked and why. The reporting is huge in my opinion. If you have ever had to diagnose something not working properly, without knowing exactly what is being blocked and why, it can become a huge time drain tracking things down. Almost every install we do has a guest component to it, having the ability to keep the guest WiFi family friendly or prevent things like torrenting is also very important. From a support and management standpoint, having Wireguard VPN capabilities are also important to us. And of course, speed, how fast can it do all these things and how much traffic can it route…

My personal preference is self hosted, but for customer installs, a local hardware controller makes more sense. This really aligns with my initial theme, I’m hesitant to use a cloud based controller that I cannot control or have visibility into it’s changes. Having screens change, icons show up, new menu items appear without any notice or documentation creates risk for me. Here is a good real-world example.

We did an install and setup for a small local oil change business. The owner’s son “knows computers” (yes these words always cause me to shutter…). They want to manage their install with minimal support from us. This means we need to be able to educate him on what the interface is, what it does, where to make changes if needed and where to NOT make changes. We tell them when it is time to do an upgrade and explain what should or should not be done after each upgrade. A local controller would be the only option I would have in this instance, as the cloud one is too dynamic.

It was actually a bit of a surprise. I honestly do not know what exactly is being pushed up to the cloud or why. We put a local HW controller in the lab when we did the evaluation, so my expectation was to see very little Internet based traffic, there seemed to be a lot and honestly we didn’t dig in deep enough to see what or why.

Honestly, I don’t recall if this article existed at the time we were evaluating. What we did find were some forum posts that related to it that seem to go into much more detail on when this kicks in. Here is a good example (I just wanted a link to the post, the forum seems to be adding a synopsis which is a bit confusing in this context - so please ignore the following synopsis and focus on the link to the post).

This post documents exactly when the fallback feature kicks in:

  1. ICMP (ping) replies from the APs gateway
  2. ICMP (ping) replies from ping.alta.inc

This information is not included in the knowledge article, but I really think this is the level of detail that should be in any knowledge article.

Sadly, not a fan at all! We actually triggered it by accident (blocking Internet access) and spent way too much time trying to figure out what happened. Honestly, I want my APs to be APs, I want them to do a great job of being an AP. DHCP is not their job. I feel the same way about DPI and blocking.

When you read the Knowledge Article, it makes it sound like it is there to protect the absent minded admin. If I screw up DHCP leases or VLAN assignments, this is going to present itself as a problem somewhere and generally it is pretty straight forward to diagnose and resolve. The fallback features actually makes the diagnostics more complicated because there are several other environmental issues that can trigger it beyond my own incompetence (which to be honest, I’m not a fan of the implication in the article).

Possibly, having both is a good thing. I don’t recall how much historical data we had or how well we could use it for analysis. We typically watch trends and look for anomalies. Recently we saw a spike of Internet usage at a site that ran for several hours late at night into the morning, which was not characteristic for this particular site. Our concern was that maybe someone had made their way in and was up to no good. What really happened was an employee left their ipad on their desk streaming Amazon Video all night. It took just a few minutes to diagnose and track this down. I don’t know if the current interface for Alta would have allowed something like that.

I understand why you would want to have a presence on Amazon, eBay, etc. I suspect it is as much for protecting the brand as it is opening up a direct channel to consumers. I probably didn’t do a good job of explaining my issue with the approach.

I generally quote MSRP pricing on everything. This is where I make some money is the margin on the hardware. When direct to consumer sites (like Amazon) have better pricing than MSRP (such as bundle deals, etc.) it is more of a reputation issue for me. I don’t want to quote a price and have a customer come back and say “hey I found it cheaper on Amazon”. Not worried about being under sold as installer pricing is good. Let me caveat this - I took a quick look yesterday to see our distributors had similar bundles like I see on Amazon, I didn’t see anything but I didn’t look all that hard. What this means for me, before I could do a quote to a customer, I have to research the direct to consumer sites to see if there are any “deals” out there and then account for that in my quote. To put it simply, I’m not willing to add that overhead to my quoting process. It isn’t about me not being able to get good pricing, it is about my reputation.

Again - I do appreciate the dialog. I realize I’m calling the baby ugly at times and I am only a single, small voice is a sea of users.

Thank you.

1 Like

Try the new firmware. I did and the load balancing works. I assume that it was released with 1:1 distribution load rules. I don’t know for sure…I will do more thorough testing next week. Hopefully on a future update it will include load routing rules.

2 Likes

Correct, current weighting is 1 for any wan interface.

Is the goal to add more parameters to be modified by the user in a future release? Such as routing rules and loading ratios? Thanks for the clarification.