SD-WAN 6.1 release notes

We are pleased to announce the release of SD-WAN 6.1. The focus of this release is on stability improvements in private WAN.

Important notes:

Warning

The deprecated v1 and v2 versions of the Bondingadmin REST API will be removed in a future release. Any applications utilizing these deprecated APIs should be migrated to the v3 API as soon as possible.

These API URLs will be removed in 6.2:

  • /api/ (this is an alias for /api/v1/)

  • /api/v1/

  • /api/v2

This URL will be the only supported one going forward:

  • /api/v3

Bonding Admin

Additions:

  • The TCP congestion control algorithm can now be chosen for use in the TCP proxy

  • InfluxDB was updated to 1.2.2, which has various performance improvements

  • Improved downsampling of InfluxDB data

  • “Let’s Encrypt”, which is a free SSL certificate authority, can be used to generate a signed certificate instead of using a self-signed certificate if desired

  • Proxy ARP can be enabled on aggregators and private WAN routers which allows for simpler routing in some server hosting provider environments

  • Packet loss is now shown in both directions in the packet loss charts

Fixes:

  • Space names and keys can now be reused after they are deleted

  • Aggregator failover maintenance mode no longer requires or supports an automated expiration time. Maintenance mode must be ended explicitly using the button at the top of bonding admin pages, once maintenance is completed

Bonding Node

Additions:

  • More reliable detection of interfaces that disappear and reappear at runtime; generally seen on USB mobile connections

  • the dhcp-client-update option was added to the DHCP server on bonders to improve compatibility in some Windows client setups

  • If a node suffers a Linux kernel-level crash, it will be automatically rebooted 90 seconds after the crash occurs, in order to get service back online quickly without manual intervention

  • Link MTU negotiation is automatically performed in some scenarios where the MTU was detected as incorrect

  • There is more information in logs about why legs have gone down

Fixes:

  • Bonders will flush the Linux conntrack table when a CPE NAT IP is started or stopped to avoid stale connection tracking information routing packets incorrectly

  • Fix multiple CPE NAT IPs for a single connected IP using the incorrect CPE NAT IP

  • The automatic reorder max hold feature now chooses a more sensible value, and can change at runtime to adapt to conditions. This should reduce the impact of a slow TCP ramp up

  • Devices that are upgraded from Debian 7 “Wheezy” to Debian 8 “Jessie” are handled better in bonding

  • Interface settings, such as Ethernet speed and duplex, now correctly apply to the base interface when using a VLAN.

Private WAN

The pwan-aggregator and pwan-router packages are no longer required to be installed on aggregators and private WAN routers in order to use private WAN. When upgrading to 6.1 apt-get will state that it is removing these packages if they were previously installed.

Since the private WAN packages have been migrated into the standard bonding package, private WAN router node types requires an additional step on installation:

/usr/sbin/pwan-configure-networking

Fixes:

  • Improve support for hairpin NAT in some scenarios

  • Private WAN is managed directly by bonding, greatly improving stability