SD-WAN Internet 4.1 release notes¶

July 29, 2011

Additions¶

The balancing algorithm Intelligent Delay Managed Packet Queuing (IDMPQ) has been added. This algorithm constantly analyzes link delay, speed, queue size, and traffic characteristics to make balancing decisions that minimize packet reordering and delay variation. It requires accurate tuning of leg upload and download speeds.
Tunnel data compression has been added as an option.
The config server now separates legs into multiple types: static IP legs, PPP legs, and PPP legs with Radius integration (not shown in environments where Radius is not supported). When editing a leg, it is now clear which fields must be supplied for each type of leg. This also greatly simplifies the internal design of the software, making it easier to maintain and enhance.
PPP credentials can now be managed from the configuration interface.
A free-form Note field for each bond has been added.
A nightly task now removes configuration update records more than a week old.This greatly speeds up loading of bond detail pages. The latest 15 update records are kept for each bond, regardless of their age.
The bond and aggregator lists now show more information, including WAN IPs, device CPU name and speed, and option settings.

Support for version 3.x bonders was removed.
The bond enabled/disabled option was removed.
The bondingctl command was removed because it was no longer necessary after recent reliability improvements and after combining the leg Enabled and Force Down options (see below).
The leg Pseudo Number field has been removed and replaced with a Note field.

The leg Enabled and Force Down options were combined into the Link Mode option.
The tunnel MTU was increased by 40 bytes.
PPP daemons are restarted at intervals of at most every 30 seconds instead of up to every five minutes as before.
Tunnels are restarted at intervals of at most every 30 seconds. Previously there was no maximum time between start attempts.
The bonder bonding.log file is now rotated daily. Old files are renamed by date and retained for seven days.
In leg hooks, the following environment variable names were changed: OUTSIDE_IP to IP, OUTSIDE_NETMASK to NETMASK, and OUTSIDE_GATEWAY to GATEWAY. NETMASK and GATEWAY are only present for static legs.
The name of the Munin graph link_invalid_packets was changed to to packet_exceptions.

Multiple PPP daemons can no longer be started for a single leg.
The firewall script now only flushes the wan_in chain. It doesn’t remove other chains.
Legs now stop properly in all circumstances.
The network value of each WAN IP must now be unique. WAN IPs are no longer allowed to conflict in a single bond or even among different bonds.
Leg updates from aggregators other than the aggregator assigned to a bond are now ignored. This situation can occurs when a bond is switched from one aggregator to another. Previously this triggered an exception and caused all further updates from the old aggregator to fail.
The bond editing page now always shows correct information even if the browser Back button is used to navigate to the page.
Updating of leg states has been improved. There should be fewer occurrences of stale leg state records in the database.
Logging of errors when starting Bonding with a route object but no OSPF daemon is now logged properly.
Legs now start properly when they are specified as failover.
The name of the user is now logged when bonds, WAN IPs, and routes are added.
Config server correctly validates that a netmask value is provided when adding a new WAN IP address.

It is time consuming to tune links for use under IDMPQ. This needs to be automated.
The config server includes references to bond and aggregator Munin graphs even if those graphs don’t exist. This results in unnecessary requests that always return 404 File Not Found.
Bonds can sometimes fail to be deleted when the bonder is offline.
Each Munin plugin from every bonder and aggregator is graphed, even though most graphs are never seen. This places an unnecessary load on the config server.