A couple of days ago we snuck out a minor update to Veeam Powered Network (Veeam PN) bringing the version up to 2.1 (Build 2.1.0.461). We released 2.0 back in May which was a significant release as we ripped out OpenVPN and replaced it with WireGuard for the site to site networking functionality. Version 2.1 bring with it some minor under the hood enhancements but it mainly focused on supporting Veeam PN being deployed from the AWS Marketplace.
For those that need a little refresher on what Veeam PN does… it presents a simple and intuitive Web Based User Interface for the setup and configuration of site-to-site and point-to-site VPNs. Veeam PN has become popular in the IT enthusiast and home lab worlds as a simple and reliable way to remain connected while on the road, or to mesh together with ease networks that where spread across disparate platforms.
I use Veeam PN almost all the time from home and more importantly, when I am away on work trips to connect back to my home office as well as remote into various platforms where I run lab workloads.
Upgrading to 2.1:
For those still running 1.0 there is no direct upgrade to 2.x due to the replacement of OpenVPN with WireGuard. For those on 2.0, the upgrade is simple and can be completed in under a minute.
When you login, you should see a message above the main dashboard
Clicking on that will take you to the Settings -> Updates Tab
Click on the Update Now button and the upgrade will begin. Note that there is a services restart so all existing connections will be disconnected
After about a minute or so, you can log back in, and all end points should automatically reconnect. There is no need to re-download the site-to-site or point-to-site configurations.
Note that you can also upgrade via the command line using apt-get.
New DNS Configuration:
In the Veeam PN hub portal, you can see the list of configured sites, DNS suffixes and DNS servers. If you want to disable DNS on a network hub you can toggle the DNS setting to off. DNS forwarding and configuring was introduced in 2.0 to resolve FQDNs in connected sites.
Links:
