Bonded Internet 2013.1 release notes

January 15, 2013 Additions ^^^^^^^^^^

  • Multiple bonds can be edited or restarted at once from the dashboard and bond index pages.
  • User documentation is available on configuration server from the Help->Documentation menu. Documentation will no longer be released as a PDF file.
  • Config updates for aggregators are shown on the aggregator details pages.
  • Bonds can now be sorted by their current traffic rates.
  • Bond IDs in the bond list table can now be clicked to go to the bond details page. The same change has been made to the aggregator, speed test, and QoS profile list pages.
  • Internal testing procedures have been improved.
  • The API now logs the user that makes a change.
  • API documentation has been expanded.

Changes

  • Configuration updates are now run per node, not per bond. For example, previously if a bonder was not available, config updates would not even go to the bond’s aggregator. Now configuration updates will go to an aggregator even if the bonder is offline.
  • Admin app Javascript and CSS resources have been reorganized.
  • Some core libraries have been upgraded: Django has been updated to version 1.5 and the Django REST Framework to 2.0.
  • The username and password fields for bonders and aggregators are no longer required.
  • The default number of rows shown on tables has been increased from 10 to 25.

Fixes

  • The Save button at the top of the bond edit page now works in Internet Explorer.
  • Widgets on the speed test details page are collapsed properly when returning to the page.
  • The speed test details page now always renders as regular HTML. Previously it would render as JSON content when navigating to it using the back or forward buttons.
  • The bond configuration section on the speed test details page is populated correctly.
  • The TCP proxy field on the bond list page is populated correctly.
  • The leg details hover text on the bond list page no longer says that PPPoE legs are DHCP legs.
  • The user name in the navigation bar is no longer blank when a user’s full name is not provided. It now just shows the user name.
  • Multiple legs can no longer be set to failover using the API.
  • Font files are not longer loaded over HTTP on the HTTPS site.
  • The bond add form now saves properly when the TCP proxy option is enabled. Previously the TCP proxy could only be enabled for existing bonds.

Defects

  • When editing multiple bonds, it is impossible to clear the QoS profile. It can only be changed to a specific profile.