Skip to main content

Director 1.0-1.3 Release Notes

The release notes of Director versions between 1.0.x and 1.3.x are available here.

Director 1.3.3​

Requires rWeb 9.0 or later

Bug Fixes

Director 1.3.2​

Requires rWeb 9.0 or later

Enhancements

  • Added firstboot logs to support uploads.
  • Director license commands will now show the serial number of your instance.

Bug Fixes

  • Improved resilience of certain operations that, when failing to execute, could cause a Director installation to partially fail.
  • The support upload now uses an explicit case number flag instead of a description flag. The feedback from running the script has been updated as well.

Director 1.3.1​

Requires rWeb 9.0 or later

Enhancements

  • Update base OS and several components, including several security patches.
  • Adjusted sampling ratios for interface tracking.

Director 1.3.0​

Requires rWeb 9.0 or later

New Features

  • Interface Workflows can now be set up to monitor and take actions based on traffic patterns observed on individual interfaces for which Director is receiving flow samples. Interface Sets are used to map these new workflows with the interfaces they should monitor.
  • Added a show traffic-interface command to the Director CLI to facilitate testing and setting up Interface Workflows.

Enhancements

  • Updated the OS (including security fixes) and several system components.
  • The Director CLI will now show Director's hostname in the interactive prompt.
  • Licensing commands will now attempt to show the external IP used by Director, which is occasionally needed for interaction with a 3rd party licensing component.
  • Enhanced the quality of error messages for a wide variety of configuration problems. It should be easier to understand where and why a configuration file has issues.
  • actions are now checked to make sure they are not impacting prefixes outside of the address space configured in rWeb, or they are suppressed.
  • Added more logs and diagnostics to the Director Support Upload.

Bug Fixes

  • The Director CLI will now show an error if the VM is missing required CPU capabilities as outlined in the installation requirements.
  • Configuration elements like workflows or actions that require unique names will no longer allow empty strings.
  • Director now explicitly records its upgrade path internally. This was already done indirectly, but it wouldn't capture the original starting version of a Director instance and needed interpretation.
  • Adjusted start timeouts of some internal services.
  • Secured an internal component that could inadvertently log sensitive information.
  • Fixed a case where Director Support Upload could fail if the temporary directory it was using got removed after being unused for too long.
  • Logrotate is now run more frequently to prevent some cases where log growth could consume too much disk on minimally sized deployments.

Director 1.2.1​

Requires rWeb 9.0 or later

Bug Fixes

  • This release only contains a packaging fix for the Director .ova file, to ensure the manifest and contents are in line with current standards. If you are a doing a fresh Director 1.2.0 install for VMWare, use this .ova instead.

Director 1.2.0​

Requires rWeb 9.0 or later

New Features

  • Users can now get better workflow and trigger status in the CLI.
  • Users can now manually start and stop actions or workflows regardless of traffic conditions.

Enhancements

  • Director utilizes the new include_prefix Zone API available in rWeb 9.1 to retrieve Zone configuration significantly faster. If this API is unavailable (i.e. it's connected to a 9.0 rWeb) it will use the previous (slower) API.
  • Added additional logs and information to the Director Support Upload.
  • Added a show system version command to the Director CLI.
  • Added some additional data to ClickHouse to make it easier to build a Grafana dashboard for Director visibility.
  • Added average-calculation-time as a supported configuration field to make traffic calculation more reliable for flow-based sampling.

Bug Fixes

  • Updated several 3rd party packages (such as ClickHouse).
  • Removed unnecessary processing for an internal notification that should have been immediately discarded.
  • Fixed a case where the CLI could hang for specific show traffic average queries.

Director 1.1.1​

Requires rWeb 9.0 or later

Bug Fixes

  • Applied latest OS updates and security patches.

Director 1.1.0​

Requires rWeb 9.0 or later

info

It's recommended you reboot if upgrading to this version of Director from a version below 1.1.0. Fresh installs do not need to be rebooted.

New Features

  • Director can now generate support uploads, similar to how RIOS and rWeb offer similar capabilities.
  • A new top level command branch can be used on the CLI to check on received flow samples.
  • Two other top level command branches are introduced to the CLI for analyzing network traffic based on your received flow samples: show traffic and show traffic-current.

Enhancements

  • Updated underlying OS to the next minor version, with accompanying component library updates.

Bug Fixes

  • Properly initialized per-install configuration items for the web UI that were using a static default value.
  • The web UI will now pop up a reminder to click the 'upgrade' button to actually start the upgrade, after it's finished uploading and processing an upgrade file.
  • Improved the resilience and error handling for the web UI of an internal message service.
  • Web UI configuration changes will be applied much faster (previously could be up to 30 seconds).
  • Hostname changes will now correctly update both the static and transient hostnames. It is still recommended that you reboot Director following any hostname changes to make sure all services are using the correct hostname.

Director 1.0.1​

Requires rWeb 9.0 or later

Bug Fixes

  • Increase default storage interval to prevent excessive disk usage.

Director 1.0.0​

Requires rWeb 9.0 or later

New Product RioRey Director is a new platform enabling offramp detection and deployment. With Director, you can now do out-of-band detection and redirection of DDoS attack traffic. Director processes incoming flow samples from your network's routers (mapping them to the Groups and Zones configured in rWeb) and uses a flexible workflow model to either perform traffic shaping via BGP or BGP Flowspec, or trigger arbitrary scripts.

A general discussion is available here and a more detailed walkthrough of an initial deployment is here. The basic installation guide is here.

New Features