Skip to main content

6.1 Release Notes

The release notes of all 6.1 rWeb and RIOS versions are stored here.

info

In order to upgrade to 6.1 versions of RIOS, please upgrade to RIOS 6.0.5 first to ensure the 6.1 upgrade will complete successfully.

6.1.3 System Release Notes (RIOS 6.1.3)​

RIOS v6.1.3 (RE2000, RE4000, RE2200, RE4200, RE5200, RX10, RS10, RS30, RG)

info

RIOS 6.1.3 is compatible with both rWeb 6.0.0 and rWeb 6.1.0. For users not wishing to upgrade to rWeb 6.1.0, your rWeb must at a minimum be running rWeb 6.0.0.

Bug Fixes

  • Fixed issue where upgrading to RIOS 6.0.3 and later fails under some conditions.
  • Fix for condition where LLCF enabled ports were not coming back up properly.

Known Issues

  • If both AT17 and AT22 are set to "Off", AT21 must also be set to "Off" or traffic will be negatively impacted.

rWeb 6.1.0.release (rWeb Upgrade Optional, 6.0.0.release minimum)

6.1.2 System Release Notes (rWeb 6.1.2.release)​

rWeb 6.1.2.release

Bug Fixes

  • Fixed issue where rWeb backups would not finish downloading under certain circumstances.
  • Fixed issue where maintenance operations performed from rWeb would improperly pin device host keys.
  • Changed database command used by cleanup process to be compatible with the current version.

6.1.1 System Release Notes (rWeb 6.1.1.release)​

rWeb 6.1.1.release

info

This is a bug fix release for rWeb 6.1.0. Please see the 6.1.0 release notes for more details if you are upgrading from an older rWeb release.

Bug Fixes

  • Fix issue where it was not possible to upgrade from 6.0.1 to rWeb 6.1.0. Please upgrade directly from 6.0.1 to 6.1.1.
  • Fix issue where rWeb may not start properly after an unclean shutdown
  • Fix generation of SSL Certificate Signing Requests (CSRs)
  • Fix behavior of charts when maximized

6.1.0 System Release Notes (RIOS 6.1.0, rWeb 6.1.0.release)​

RIOS v6.1.0 (RE2000, RE4000, RE2200, RE4200, RE5200, RX10, RS10, RS30, RG)

info

RIOS 6.1.0 is compatible with both rWeb 6.0.0 and rWeb 6.1.0. For users not wishing to upgrade to rWeb 6.1.0, your rWeb must at a minimum be running rWeb 6.0.0.

Enhancements

  • AT9, AT17, and AT23 now include filtering support in IPv6. All algorithms now protect against both IPv4 and IPv6 versions of their attacks.
  • Kernel updated to latest version.

Bug Fixes

  • Fix for erroneous filter list entries (IPv4 attacks showing as IPv6).
  • Fix for AT9 sometimes labeling attacks as ST2 (Port Scan Attack) when they should be ST3 (High Connection Rate).
  • Some private IPv4 space addresses were not being blocked under AT62. The full list has been updated and is visible in the "Drop private IP address packets" section of the documentation page for AT62.

Known Issues

  • If both AT17 and AT22 are set to "Off", AT21 must also be set to "Off" or traffic will be negatively impacted.

rWeb 6.1.0.release (rWeb Upgrade Optional)

This version of rWeb makes significant changes to how users interact with the system. It is designed to allow very granular permissions to be assigned to each user and give stricter control over major administrative functions. For example, a user can be created that can only see and interact with a limited set of groups and zones.

RIOS 6.1.0 is backwards compatible with rWeb 6.0.0. You can upgrade your devices to 6.1.0 while you familiarize yourself with the new changes to rWeb, and perform the rWeb upgrade at a later time.

The "Customer" concept from prior versions of rWeb is now replaced by the concept of a "Group". Groups can now contain other Groups in addition to Zones.

The most significant impact is to users accustomed to using the API. Please read more in the API documentation.

New Features

  • Explicit permission sets for users. Users are now assigned to groups, and depending on their granted permissions they will be restricted to certain operations within rWeb. Users can see their assigned group and permissions in the new profile link.
  • Zone configuration history. Users can compare and revert to previous zone settings more easily.
  • rWeb SSL configuration. Users can change the SSL server certificate presented by rWeb, both self-signed and externally managed certificates are supported.
  • rWeb customization. Users can change the logo and header shown by rWeb in the GUI.

Enhancements

  • Updated several libraries and frameworks used by rWeb.
  • Added cancel buttons for actions that previously only had a save button when editing a configuration.

Bug Fixes

  • NTP servers now show their correct synchronization status.
  • Fix for slow uploads to rWeb erroneously showing a 504 error when the upload was still in progress.
  • Fix for charts not rendering properly when zoomed or set to fullscreen.