This release enhances WAN visibility and routing capabilities, improves VPN interoperability, and expands advanced dynamic routing support.
WAN Status:
Add support for Speed Test.
Add support for Site Location.
Improve L2TP server compatibility with Windows clients.
Dynamic Routing: Add support for IS-IS.
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.
I updated my route 10 from 1.4t to 1.4u and the internet has been down since. I had to power on reset and reset the modem just to get connected with no internet. The cloud controller was then able to contact the route 10 but still no internet connectivity for my devices. I was able to run the new speed test from the controller. When I hit setup on the route 10 it was very glitchy. Seems like an issue routing the LAN/VLANs to the WAN.
click on each network and in the pop out deleted my local dns ip address from the dns servers box and saved. had to again do a power on reset before connectivity was restored.
I am also dead in the water, with everything disconnected. Using the Cloud Controller so unable to connect to any Alta devices.. Is there a formal statement on how we recover the network ? I dont want to make things worse by inadvertently erasing the configuration. Also wondering about the Alta Release process as this is not the first time an update has caused issues.
I have now performed the power on reset on Route10. devices have reconnected to the cloud controller BUT the route10 cant make up its mind if it wants a firmware update or not (it seams to have settled wanting to reload 1.t) . Also its reporting that requires setting up. So still allocated to my site.
Its taken two Power on resets on the Route10 to recover the network. Its running on 1.u and wanting to revert to 1.t. I hold off on that for the minute. Route 10 still wants to be “Set up” but appears to have the correct config.
As I have said above the Alta software Release procedure need really looking at from a Quality Standard point of view. This should just not happen in these enlightened days. For me it was no heating, no lights, car has not charged and more. I feel for those who have the route10 in production networks as it appears this require physical presence to effect a recovery, well it was in my case
IPv4 only in my case. DHCP via WAN SFP. Neither of power off and on, reset while on or Power-on-Reset seems to provide connectivity yet. All seems fine in the UI, LEDs blinking like I suppose they should, and Route10 responds to LED-settings etc., but no connectivity to WiFi or Ethernet yet. Next step may be to wipe out the entire network and PoR the hell out of it. Though, not entirely sure if it actually PoR entirely as the firmware should have been downgraded a few steps in that process…
Edit: So, not up and running yet, but I did note a few things. I could connect to the Route10 via Cloud UI ssh-terminal, the speedtest worked → WAN is functional. I got a bunch of APIPA warnings on fallback IPs. Some devices carried their proper IPs but were not accessible from their respective web based or app based UIs. Now, if I managed to cat the correct file, the very interesting issue was that the dnsmasq config showed no DHCP-ranges for anything else than the native VLAN, So, everything else than my network devices (native) VLAN is effectively locked out as I try to access them from SSIDs or via Ethernet via S8-switches set up for specific VLANs only?! Anything familiar here?
Though, not entirely sure if it actually PoR entirely as the firmware should have been downgraded a few steps in that process…