rWeb Release Notes
rWeb release notes are consolidated here, starting with rWeb 10.0. Releases prior to this version are posted in the archives.
General guidelines on upgrading rWeb can be found here.
rWeb 10.1.0.release.0
Pending Release
This release adds the new feature of visualizing Director data in charts on rWeb (maintatining historical Director data) and several enhancements targeted at improving backend performance, alongside many smaller bug fixes.
New Features
- Added Director Traffic visualizations to rWeb. rWeb will now ingest Director data for longer term data visualization, with data retention can also configurable for this data.
Enhancements
- Enhanced backend connectivity and process management to ensure adequate performance when managing over 100 RIOS devices.
- Backend process monitoring is also now exported to a new Prometheus endpoint.
- Added better feedback when rolling back configuration to a previous revision. A pop-up will confirm exactly which revision's settings were used once the rollback is complete.
- Added better feedback when using the rWeb Admin search sidebar. You'll see an in progress icon as you type to search, and you can now also click away from the search results list to close it.
- Added new mitigation controls that were either previously advanced controls or are new controls:
- AT1 and AT2 "Enable aggressive filtering" (requires RIOS >= 8.4.0).
- AT17 "Spoofed Attack Detection Threshold" (requires RIOS >= 9.0.0). This control already has preset values tied to filter sensitivity.
- AT23 "Maximum non-spoofed packet rate per second" (requires RIOS >= RIOS 9.0.0). This control already has preset values tied to filter sensitivity.
- Add support for new RE110 model on the Device Status page.
- Added new alerts for RIOS license changes. If a reboot is needed to process throughput changes on a license, this alert will be shown.
- The search bar will now also search currently applied template names while using "Apply to Zone" on the Group Templates screen.
Bug Fixes
- Unified reporting in Traffic Detail charts. Some data types are reported in longer cycles (90 seconds vs 30 seconds) which previously was being rendered as sawtoothed even if the 90 second data remained constant.
- Creating a template is now only selectable once you've finished saving all of your changes. Templates were only ever made off of saved state so this makes that relationship much more explicit.
- AT1 ECN controls were not showing up when searching for them. They're back now.
- The Device Links section will now show a message if this isn't configurable for the selected device.
- rWeb Hardware Status no longer shows up for VM rWebs.
- Fixed issues with adding a new Director: it could save empty strings for both user and password, and additionally the password field could show as plaintext input rather than a password input.
- Adjusted internal logging to better track down process delays.
- Updated the package used by Prometheus node exporter.
- Added more data to rWeb support uploads and restructured how they are packaged.
- The Device Interfaces section now has a proper refresh button on the panel.
- Fixed a bug on IP Search that would incorrectly represent Top Attacker samples as having a subtype of 0.
- Fixed an issue with the rWeb status API where it would not properly return full results when queried with an appropriately permissioned API Token.
- Fixed underlying query used to populate the disk usage table. Previously under certain conditions this could cause the table to render very slowly or not at all.
- Fixed a case where a spurious error message could appear when starting rWeb API.
- Fixed chart exports rendering empty charts.
- Fixed an issue preventing the RIOS console from connecting properly.
- Fixed an issue where RIOS support uploads that were generated without the "Upload to Riorey" button checked could not be properly manually uploaded later.
- Fixed an issue where template requests were being rejected with a 403 Forbidden error. This was happening for any templates that were not directly owned by the Default Group.
- Fixed a separate issue with requesting the full set of templates that could omit templates a user had the ability to read.
- Fixed an issue where backend process names were not showing up correctly in logs.
- Fixed an issue where victim reports could fail to generate if too many filter list entries were included. Reports are now capped to a limit of 1000 entries to ensure pdf generation succeeds. Users can still query the filter list API if they need to retrieve the full set of entries for the victim.
- Fixed a race condition that could periodically cause the sidebar on the group page to appear blank.
- Updated OS and various system packages.
rWeb 10.0.1.release.0
This point release includes a few minor bug fixes.
Bug Fixes
- Fixed an issue where the upload button for an rWeb support upload would attempt to upload before the log bundle was finished generating.
- Upgraded the internal library used for hardware status monitoring that was throwing spurious errors.
- Fixed an internal user management issue observed during in-place upgrades to rWeb 10.0.
rWeb 10.0.0.release.1
This major release updates many rWeb internals including the OS, along with a significant style rework of the entire web UI. Like the 9.0 upgrade, it is not a standard upgrade. However, unlike the 9.0 upgrade this one can be done in place from an existing rWeb. Please refer to the additional upgrade notes for more information.
New Features
- rWeb's style underwent a significant rework, with an eye torwards better responsiveness, more pleasing aesthetics, and visual clarity. Certain menu elements and UI interactions may be in new locations. The new style can also be customized by rWeb administrators.
Enhancements
- The base OS has been updated along with many system packages for security and performance improvements.
- EC SSL Certificates are now supported.
- rWeb now provides both application metrics and the standard Prometheus Node Exporter metrics. If you'd previously configured an application scrape job from rWeb, the metrics path is now at
/metrics/rweb(previously just at/metrics). More information is available on the Prometheus documentation page.
Bug Fixes
- Fixed an issue where canceling Zone Configuration edits wouldn't always leave the UI showing the original pre-edited state.
- Fixed an issue with OIDC logins where they were not being provided the correct timezone configured for rWeb.
- Updated the description on AT62's IP Protocol UDP controls to make it more obvious that it's dropping multiple UDP destination port packets.
- Fixed an issue where old backup SSL keys were not referenced in their correct location, in specific edge cases leading to a monitoring service to crash.
- Added an additional check to ensure the database is cleanly restarted on an rWeb cluster following an upgrade.
- Fixed a potential race condition that could occur if a cluster rWeb attempted to switchover during autorepair operations.
- Fixed an issue where the sidebar on Zone control pages could render twice.
- Updated our list terminology. Our previous usages of Whitelist, Blacklist, and Greylist are now Allow lists, Block lists, and Block list exceptions for technical clarity. If you were using the API for these functions you may need to update your scripts to use the new endpoints.
- Fixed an issue where regex testing in AT61 could crash if the uploaded packet capture included ICMPv6 packets.
- Fixed an issue where really long Group names would not wrap properly on several UI elements.
- Fixed an issue where inactive webhooks were still queuing events.
- Fixed an issue where rWeb support uploads could fail to generate or erroneously overwrite existing RIOS support upload history.
- Increased the size limit of the files allowed for Block list imports and subscriptions. The previous size limit was 10MB, which was too small for lists potentially containing both IPv4 and IPv6 addresses and/or lots of distinct description text. The new size limit is 100MB.
- Fixed an issue where resetting the chart on the Victims would render the chart in light mode, even if you were set to dark mode.