Bonded Internet 3.1 release notes¶

September 21, 2010

Additions¶

Bonders can now use PPPoE. PPPoE legs can be assigned public addresses or private addresses with the correct network configuration.
Bonders now monitor legs as they start and run. If a leg fails to start, perhaps because PPPoE authentication fails, it is restarted. If a PPPoE daemon quits unexpectedly, it is restarted.
The configuration server supports PPPoE by assiging Radius usernames, passwords, IP addresses, and groups to each leg.

Bonders no longer use the Debian volatile repository.
Leg netmask and gateway are no longer required fields in the config server, as these are not needed when using PPPoE.

To reduce load on the configuration server, bonders now update their cached configuration files each hour within a one-minute block, rather than all at the exact same time.
The time Bonding waits for OpenVPN daemons to exit has been reduced. This reduces the time required for Bonding on aggregators to stop by about 50%.

The Debian preseed file has been updated with correct APT repository sources.
The /etc/hosts file is now updated to match the entry in /etc/hostname.
“UseDNS no” is no longer appended to the SSH configuration file multiple times.
The Flowlet monitoring thread no longer delays Bonding shutdown if it is waiting to restart the Flowlet balancing script.
If a leg ping check is in progress when Bonding shuts down, it no longer gives a logging-related error.
When errors are encountered while applying updates from the config server, Bonding logs the error but without any unnecessary detail.

Leg netmask and gateway fields are not required, even for static-IP legs. Failing to supply these fields for a static-IP leg will make a bonder unable to start that leg.