7.1 Release Notes

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

7.1.10 System Release Notes (RIOS 7.1.10)

RIOS v7.1.10 (RE2000, RE4000, RE10, RX10, RS10, RS30, RS40, RG, VM10)

Bug Fixes

• Fix for AT3 where duplicate ACK packets were not being counted correctly within a selective ACK (SACK) session.

7.1.9 System Release Notes (RIOS 7.1.9)

RIOS v7.1.9 (RE2000, RE4000, RE10, RX10, RS10, RS30, RS40, RG, VM10)

Bug Fixes

• Fix for where UDP, ICMP, and AT9 detector sensitivity reduces drastically after 198 days of uptime so most attacks were not picked up as expected.
• Fix for where AT1 and AT2 filter sensitivity reduces after 198 days so that some attack traffic leaks.

7.1.8 System Release Notes (RIOS 7.1.8)

RIOS v7.1.8 (RE2000, RE4000, RE10, RX10, RS10, RS30, RS40, RG, VM10)

Bug Fixes

• Fix for excessive heat caused by CPU not idling on ports without traffic on DPDK (RE10, RS40, VM) platforms.

7.1.7 System Release Notes (RIOS 7.1.7)

RIOS v7.1.7 (RE2000, RE4000, RE10, RX10, RS10, RS30, RS40, RG, VM10)

Bug Fixes

• Fix for an initialization timing bug that could cause RX10 and RS30 units to remain in bypass following boot.

7.1.6 System Release Notes (RIOS 7.1.6)

RIOS v7.1.6 (RE2000, RE4000, RE10, RX10, RS10, RS30, RS40, RG, VM10)

info

This release is a manufacturing related release only, for VM devices. The only change in this release allows starting a RIOS VM from 7.1.6 instead of needing to upgrade from an earlier image.

Bug Fixes

• Fix bug in VM manufacturing process to allow post beta 7.1 VM images to be built.

7.1.5 System Release Notes (RIOS 7.1.5)

RIOS v7.1.5 (RE2000, RE4000, RE10, RX10, RS10, RS30, RS40, RG, VM10)

Enhancements

• DPDK based systems (VM10, RE10, RS40) now support Jumbo Frames. This is enabled by default for these devices and does not require configuration in rWeb. If the network on either side of the filter device is configured to use Jumbo Frames it will support it correctly.
• Slight database performance boost for DPDK systems on a number of recurring queries.

Bug Fixes

• Fix for a device using only the first regex entry in a Zone and ignoring the rest of the list.
• Fix for Filter List entries made for attack types in Monitor Mode not being reported. This did not affect filtering, as devices only failed to report entries that violated the attack type but would not have dropped them as the type was in Monitor Mode.

7.1.4 System Release Notes (rWeb 7.1.4.release)

rWeb 7.1.4.release

Bug Fixes

• Critical fix to address a backend process crashing and being unable to restart.

7.1.3 System Release Notes (RIOS 7.1.3, rWeb 7.1.3.release)

RIOS v7.1.3 (RE2000, RE4000, RE10, RX10, RS10, RS30, RS40, RG)

Enhancements

• Improved internal logging of victims.

Bug Fixes

• Fixed an issue where the byte counts for ICMP attack victims were being reported incorrectly.
• Fixed an internal debug log error.
• Fixed an issue with detector cycle calculations causing incorrect cycle switches and cleanup, impacting UDP, ICMP, and AT9 detection.
• Fixed incorrect reporting of TCPOption length errors.
• Fixed issue where several internal buffers were too small, causing non-critical database queries to fail.

rWeb 7.1.3.release

Bug Fixes

• Filter list victim notification emails for IPv6 addresses are now sent correctly and no longer generate device errors.
• Fixed a few other issues with Filter List entry modifications, including another error when handling IPv6 entries.
• Fixed issue where a VM rWeb host could be pegged at 100% CPU usage while the guest reported much lower usage.
• Entering blacklist and whitelist entries using ASNs now works properly again.
• Added code to prevent the email notification process from deadlocking with the victim updating process. This previously had a small chance of occurring and sending duplicate notifications.
• AT4 controls can no longer be changed without hitting edit first.
• Added code to prevent a race condition that could cause the API to not come up properly following an upgrade from a pre-7.1 rWeb release.

7.1.2 System Release Notes (rWeb 7.1.2.release)

rWeb 7.1.2.release

warning

This release restricts the version of TLS used by rWeb to version 1.2. This may cause incompatibility issues with your browser. If you are unable to access rWeb with your browser, please check the versions of TLS that are supported.

Bug Fixes

• Fixed issue where upgrades previous to 7.0.1 could fail due to migration issue. It is safe to upgrade to this version from any prior release.
• Fixed issue where a license pull could mangle internal history of rWeb commands.
• Adding a RADIUS or TACAS server now works correctly and shows a proper result status.
• The primary rWeb in a cluster rWeb now shows the correct status for backend on the secondary.
• Fixed an issue where an alert could not be generated for an expired rWeb license.
• Fixed issue with sample packets not displaying properly.
• The down button on the authentication methods is now fixed.
• Fixed an issue where the API handler could be only partially running after certain cluster operations.
• Fix for zone configuration issued cause by AT1 being in Force On.
• TLS is now restricted to version 1.2.
• Fix for AT62 where IPv6 header control and victim display could be edited without clicking the edit button first.
• Fixed issue where port aliases could no longer be applied to a device.
• Fixed case where tcpdump expressions could be ignored (tcpdump would capture all traffic, instead).
• Fixed an issue that prevented new advanced configuration changes from being made.
• Fixed issue where SNMP for devices could not be configured properly.
• Fixed an issue where a database recovery mechanism would use a deprecated process and fail.
• Fixed an issue that could cause partial configuration loss during a backup restore.

7.1.1 System Release Notes (rWeb 7.1.1.release)

rWeb 7.1.1.release

warning

Before upgrading to this release, upgrade to 7.0.1 first. There is an issue where database migrations from pre-7.0.1 may not execute cleanly depending on the version, but upgrading to 7.0.1 first will prevent any issues.

There is a known issue where devices mapped to a zone with AT1 set to Force On prevents other zones mapped to that device from being able to change configuration. There is a manual workaround:

• Identify all zones with AT1 SYN Flood -> Filter Mode -> Force On
• For each of these zones, go to the zone Routing page. Record, then remove all devices in the 'connected' state
• For each of these zones, go to Mitigation Config -> AT1 SYN Flood, and change the Filter Mode to Auto
• Re-add devices removed from zones in the second step.

A single step alternate workaround is to simply delete all zones with AT1 SYN Flood turned on.

At this point, all zone configuration should be usable again, with the exception that no zones can be put into 'Force On' mode until this issue is patched.

Bug Fixes

• Group route inheritance is now fixed.
• License pulls will now display the correct error message when there is a problem.

Known Issues

• Adding a RADIUS or TACAS server can result in a confusing unexpected error message of "HTTP/1.1 200 OK" and not refresh properly. The server will be added correctly, however.
• The down button on the authentication methods order screen is broken, doing the same thing as the up button.
• The primary rWeb in a cluster rWeb may show the incorrect status for backend on the secondary, showing it as up and running when it in fact was stopped correctly.
• AT1 Force On can cause configuration issues. See note in top section.

7.1.0 System Release Notes (RIOS 7.1.0, rWeb 7.1.0.release)

RIOS v7.1.0 (RE2000, RE4000, RE10, RX10, RS10, RS30, RS40, RG)

Enhancements

• Improved internal configuration management.

Bug Fixes

• Fixed an issue with filter list tracking becoming inconsistent while handling expired entries.

rWeb 7.1.0.release

warning

Before upgrading to this release, upgrade to rWeb 7.0.1 first. There is an issue where database migrations from pre-7.0.1 may not execute cleanly depending on the version, but upgrading to rWeb 7.0.1 first will prevent any issues.

There is a known issue where devices mapped to a zone with AT1 set to Force On prevents other zones mapped to that device from being able to change configuration. There is a manual workaround:

• Identify all zones with AT1 SYN Flood -> Filter Mode -> Force On
• For each of these zones, go to the zone Routing page. Record, then remove all devices in the 'connected' state
• For each of these zones, go to Mitigation Config -> AT1 SYN Flood, and change the Filter Mode to Auto
• Re-add devices removed from zones in the second step.

A single step alternate workaround is to simply delete all zones with AT1 SYN Flood turned on.

At this point, all zone configuration should be usable again, with the exception that no zones can be put into 'Force On' mode until this issue is patched.

New Features

• Zone status and mitigation are now two separate tabs. By default going to a zone will bring you to the status tab. This allows more display room to be dedicated to showing charts when on the status tab, and the mitigation tab is now searchable to directly bring you to the controls you want to manipulate.
• Support for licensing (including subscriptions) of all rWeb and RIOS platforms.

Enhancements

• The maintenance user's password can now be temporarily overridden via the serial console.
• Internal OS platform updates and fixes were applied, including an upgrade of rWeb's underlying web framework. This also includes Tomcat, which is now a supported version.
• rWeb will now retain user's requested timestamps when navigating between zones and other pages in rWeb. Users will no longer have to re-enter start and end timestamps if they browse away from zone's traffic status page and then come back.

Bug Fixes

• The second NTP server can now be left blank (both entries are no longer required).
• Fixed inconsistencies in template comparison behavior on the group templates screen.
• Fixed case where a completed tcpdump could show "Done" temporarily rather than allowing you to download the completed capture.
• Fixed issue where rWeb would try to render non-existent devices for filter list queries.
• Fixed issue where repeatedly trying to remove a device from a zone's routing tab could generate a 500 error.
• Fixed inconsistencies in displaying licenses sorted by different criteria on the device license page.
• Changed dashboard bar chart widgets (like "Victims for the last 30 days") to include days with 0 values when rendering the chart for consistency purposes.
• Fixed issue where dashboard pie chart widgets would not update correctly when their data changed.
• Fixed issue where zone stats would not sort correctly.
• Fixed bug where blacklist or whitelist import controls could be hidden after a failed import. Imports will now also show better status messages.
• Changed internal package deployment for more consistent behavior following rWeb upgrades.
• Fixed issue where rWeb was not fully removing session information for deleted users.
• Query filter list will now show some immediate feedback to indicate progress on a query.
• Fixed a bug where victim reports would download without a .pdf extension on Firefox.
• Updated the status message shown after requesting a support upload for a device.
• Fixed alignment of several "upload" buttons throughout rWeb.
• Fixed rWeb upgrade status display when on any other page than the root path '/'.
• Fixed issue in report scheduling of weekly and monthly reports where the first run would always happen the following week/month (even if it could still be run in the current week/month).
• Fixed issue where report generation would fail in cases where a top attack was still ongoing and the selected local timezone was +UTC.

Known Issues

• Adding a RADIUS or TACACS server can result in a confusing unexpected error message of "HTTP/1.1 200 OK" and not refresh properly. The server will be added correctly, however.
• The down button on the authentication methods order screen is broken, doing the same thing as the up button.
• The primary rWeb in a cluster rWeb may show the incorrect status for backend on the secondary, showing it as up and running when it in fact was stopped correctly.
• Group route inheritance is currently not working properly (It cannot be changed from its current settings).
• License pulls may display a blank error message due to a status update race condition. The error is still correctly logged under rWeb logs.
• AT1 Force On can cause configuration issues. See note in top section.