In addition to the big number of improvements and stability fixes of our July 2017 release, this firmware brings two important additional fixes. All customers should immediately upgrade to this version.
If you haven't already upgraded to the July (2016111640/2017022000) release, please also read the release notes for that version.
If you wish to upgrade from a Classic firmware, please first update the router to the last stable Classic firmware release (Version 2015081830/2015102900 released on November 27, 2015). Please note that upgrading your firmware from Classic to RuggedVPN requires a Viprinet Lifetime Maintenance license to be in place. For more information, please check https://www.viprinet.com/vlm. It is possible to have Routers and Hubs running on Classic firmware connect to a device running RuggedVPN firmware. However, a compatibility mode will be used in this case, which limits performance and features. It is therefore not recommended to use such a setup in production permanently, but it is OK to have a Classic firmware device talk to a RuggedVPN firmware device while you are upgrading these devices. The Software VPN Client is available both based on Classic Firmware and alternatively based on the RuggedVPN firmware generation. Both versions are still supported, but we recommend migrating to the RuggedVPN one.
The list below lists all new features and bug fixes compared to the previous stable RuggedVPN firmware release (Version 2017021340/2017072200 released on July 31, 2017):
Bug fixes
- Under certain circumstances traffic in one or more QoS classes would suddenly stop flowing. This could for example result in the users suddenly no longer being able to resolve IPs via DNS. This issue existed for a long time, but became more frequent with newer firmware releases. The issue now is verified to be fixed.
- In some installations, with the July firmware release LTE 450 MHz modules as used in Northern Europe would no longer be detected. They now are detected on all products again.