SD-WAN Internet 4.4 release notes

November 30, 2011

Additions

  • Automated speed testing of bonds and legs has been added. This allows legs to be tuned for IDMQP much more easily than before.

  • Legs can now be configured by DHCP.

  • DHCP and static legs can use NAT addresses.

  • Leg MTUs can be set from the configuration server.

  • There is a new page that shows a short message describing the status of a bond. This can be used in a Nagios plugin.

Removals

  • The pppauth command has been removed because PPP authentication details can be changed from the configuration server.

Changes

  • Policy routing on bonders now uses routing table IDs instead of named tables. The /etc/iproute2/rt_tables file can now be modified to customize routing on bonders and aggregators.

  • Configuration updates are now sent through WAN IP addresses first, then through leg IP addresses if updates through the WAN IP fail.

  • Leg icons have been replaced with larger images.

  • HMAC checking is performed on all control packets between tunnels, regardless of the bond’s HMAC setting. Data traffic still obeys the setting.

  • The tunnel now starts even if a link cannot be created.

  • Celery, the asynchronous task queue manager, now uses Redis as the task broker instead of RabbitMQ. Redis uses much less memory than RabbitMQ as a message server and has additional uses as a key-value store.

Fixes

  • PPP sessions are now restarted even if the PPP daemon quits because it failed to receive PADS packets.

  • Bonding now warns if the IP address assigned by the PPP server doesn’t match the IP address given in the config server.

  • Routes are now validated to avoid duplicate network addresses.

  • The config server will no longer report data rates above zero for legs that are down, idle, or offline.

  • Legs that have not started properly are now removed correctly.

  • A minor ordering bug in the link monitoring config Munin chart has been fixed.

  • The Celery Munin chart now shows all available tasks.

  • A minor naming issue in Django leg models was corrected.

Defects

  • PPPoE legs don’t support NAT.

  • Config updates cannot be submitted to a bonder through a leg with a NAT IP address. Every bonder must have at least one IP address routable from the configuration server.