Viprinet Multichannel VPN Router 510 RuggedVPN Firmware 2016080240/2016080800 Download

Posted at December 22, 2024 by PCI-DB Team

Install Driver Automatically

Device Name	Viprinet Multichannel VPN Router 510 RuggedVPN Firmware 2016080240/2016080800
Category	Router Switch Access Point
Manufacturer	Viprinet
File Size	24.9 MB
Supported OS	OS Independent

Viprinet Multichannel VPN Router 510 RuggedVPN Firmware 2016080240/2016080800 Description

This is the third official stable release of the RuggedVPN firmware. This release brings very important improvements in regards of product performance, quality and stability. All existing customers should update to this release in a timely manner. We also recommend all customers still using Classic firmware to upgrade to this release now, as end of support for Classic firmware is nearing.

New features:

- You can now create custom LTE WWAN profiles, which might be needed for some carriers or users of private APNs. Please note: The default APN profile settings have changed. Please verify that your LTE provider works fine with these new profiles before mass-deploying this release.
- Hubs in Hotspare mode now have working ACLs (and internally run our full routing stack, which they did not before). Finally this enables using the Service ACLs. This is important because without them, the DNS service on Hubs running in Hotspare mode could be used as amplifiers in DNS DDoS attacks. Please verify you have ACLs in place after upgrading to this release.
- The CPU usage of tunnel channels on Nodes has been decreased. This may result in slightly higher total bonding capacity especially when using a lot of channels (stacking).
- The CPU load when a Hub or Node receives a very high number of new connections at the same time (for example during a port scan or DoS attack) has been reduced significantly.
- The routing core latency now is as low as never before. You can ping the router with a response time of <3ms now.
- LAN throughput has been increased, CPU load for LAN traffic decreased.
- LTE-TDD Bands B38 and B40 are now validated to work. The 4G Europe/Australia/Africa module now has a working AT command tool, and is now ready for production use.

Bug fixes:

- Multiple bug fixed for the WLAN Client module which improves compatibility and now also allows connecting to unencrypted APs.
- QoS bonding priorities did not get copied when using QoS restore from/to templates.
- On stacking slaves a 24h disconnect or the ISP re-assigning the IP while connected could cause the router to eat 99% CPU permanently.
- Hubs in Replacement mode would complain about not having VLM installed. They no longer do that.
- Heartbeat diagnostics ("A single router is gone from the network") is now only shown once instead of every second.
- Log messages have leaked memory if the web interface was used without web sockets being enabled. This could grow to a significant amount of memory if the web interface was opened for a very long time with the router producing a lot of log lines (very busy Hubs).
- Fixed a memory leak when the router was dropping IPv6 broadcast traffic it was seeing on the LAN.
- Fixed a small memory leak in the configuration system. On stacked nodes doing lots of configuration syncs (for example because very unstable channels are used), this could grow to a significant amount.
- The memory usage of Hubs that see a very high number of concurrent flows (50000+) has been reduced.
- The internal packet slicer (which is used to cut IP packets into slices that are then sent over the channels) under circumstances (especially with a high number of channels, unstable channels and/or FEC enabled) could leak significant amount of memory.
- The LAN NIC no longer can get stuck, and in worst-case a LAN reset will always actually bring the NIC back to life now.
- A WLAN Client module could cause the router to eat 100% CPU. This is fixed.
- The default Autotuning mode for newly created channels is now Hybrid instead of Heuristic.

Offline update

As an alternative to an online update, an offline update is available. From time to time in additional to stable Firmware releases "Cutting edge" firmware releases are made available only as an offline update. To do an offline update, please download the correct firmware image for your product and then use the manual update function inside the router's web interface to upload that image.

About Router Firmware:

Before you consider downloading this firmware, go to the system information page of the router and make sure that the currently installed version isn’t either newer or matching this release.

Due to the large variety of router models and different methods for upgrading the device, it is highly recommended that you read and, above all, understand the installation steps before you apply the new firmware, even if you are a power user.

In theory, these steps shouldn’t be much of a hassle for anyone, because manufacturers try to make them as easy as possible, even if they don’t always succeed. Basically, you must upload the new firmware to the router through its administration page and allow it to upgrade.

If you install a new version, you can expect increased security levels, different vulnerability issues to be resolved, improved overall performance and transfer speeds, enhanced compatibility with other devices, added support for newly developed technologies, as well as several other changes.

If you’re looking for certain safety measures, remember that it would be best if you perform the upload using an Ethernet cable rather than a wireless connection, which can be interrupted easily. Also, make sure you don’t power off the router or use its buttons during the installation, if you wish avoid any malfunctions.

If this firmware meets your current needs, get the desired version and apply it to your router unit; if not, check with our website as often as possible so that you don’t miss the update that will improve your device. 

  It is highly recommended to always use the most recent driver version available.

Try to set a system restore point before installing a device driver. This will help if you installed an incorrect or mismatched driver. Problems can arise when your hardware device is too old or not supported any longer.

Related Viprinet Drivers