==================================
SD-WAN 6.0 release notes
==================================

We're pleased to announce the release of SD-WAN 6.0. In
addition to a focus on stability improvements in private WAN, several
key features have been introduced:

-  /31 ranges are now permitted for connected IPs. For example, whereas
   before 203.0.113.21/30 would be used for a single connected IP, the
   two connected IPs of 203.0.113.20/31 and 203.0.113.22/31 could be
   used.

-  Upgraded to InfluxDB version 1.1.1, dramatically reducing CPU,
   memory, and disk throughput usage on management servers.
-  Upgraded to Salt 2016.3, featuring improved stability and a fix for
   high CPU on salt-minion.

Other important notices:

-  Last year, we announced that Debian 6 ("Squeeze") reached end-of-life
   and would no longer receive updates from Debian. In addition to this,
   2016.2 is the last version of bonding to run on Squeeze. Nodes
   currently running Squeeze will need to be upgraded to Wheezy or,
   preferably, Jessie, in order to run Bonding 6.0 or later. For more
   information, see `SB-4 2016-03-31 Debian Squeeze
   end-of-life <../service-bulletins/sb-4.html>`__.

Bonding Admin
--------------

Additions:

-  Added a Bond Defaults page to the administration section: this is the
   future home of all default settings to be applied to new bonds. You
   can read more about this page on the `Bond
   defaults <../administration/bond-defaults.html>`__ page.
-  Users in child spaces can now see aggregators, routing groups, and
   QoS profiles inherited from parent spaces on their corresponding list
   pages.
-  Leg notes are now included in the labels on the legend for charts.
-  Specific measurements can now have their visibility toggled for
   charts.
-  A button has been added to collapse or expand all sections on bond
   detail pages.
-  The ``upgrade-bonders`` script has been improved to more reliably
   upgrade bonders. You can read more about automating bonder upgrades
   on the `Upgrading a node <../nodes/upgrading-and-replacing-a-node/upgrading-a-node.html>`__ page.
-  Automatic bond tuning will test with concurrency and recommend TCP
   proxy on bonds in private WAN.

Fixes:

-  Services involving scheduled events more resilient to changes in
   daylight savings.
-  Improved reliability of generating historical charting data.
-  Improved reliability of updating leg states for large management
   servers with high database contention.
-  Corrected the management server URL being malformed in tuning test
   result emails.
-  Prevented a race condition concerning reserving a management VPN IP
   when adding bonds in bulk.

Bonding Node
-------------

Changes:

-  Version increased from 2016.2 to 6.0.
-  Provisioning ISO boot menu displays the date that the image was
   generated instead of the management server version.
-  Firewalls updated to disallow IPv6 traffic.
-  Proper support for provisioning under UEFI.

Fixes:

-  Inbound connections through the TCP proxy to a CPE NAT IP now behaves
   correctly.
-  GATEWAY and NETMASK environment variables are now set correctly in
   leg hooks for static legs.
-  Support for running on systems with a full BGP table and no default
   route.
-  When provisioning or updating a bonder, configuration files, keys,
   and certificates are written to disk in a more reliable way to avoid
   writing corrupt or empty files.
-  Improved speed test reliability in some exceptional circumstances and
   during leg and bond tuning.
-  Improved carrier detection on legs to prevent cases where bonding
   fails to detect carrier on a leg and does not bring it online or goes
   into an undesired state.
-  Routing correctly when a bond is configured with a route that
   overlaps with the management VPN range.
-  Improvements made to avoid routes missing on bonders when disabling
   or removing some CPE NAT IPs.
-  Properly handling metrics reported under virtual machines.

Known Issues:

-  Connections between bonds fail when going through the TCP proxy if
   the bonds are on the same aggregator.

Private WAN
------------

Additions:

-  TCP Proxy made compatible with Private WAN.
-  Added "High Availability" documentation for Private WAN Routers.

Fixes:

-  Improved synchronization between PWAN software and dynamic routing.
-  Correctly routing connected IPs with public addresses in PWAN.
-  Improved response in PWAN to configuration changes including, but not
   limited too: bonds changing aggregators, bonds changing spaces, new
   bonds being created, new spaces being created, space key changes,
   aggregator failover, service restarts.
-  Ensuring bird configuration is written to the disk before starting
   bird.
-  Private WAN Routers more responsible about tidying up resources
   during shutdown.
