5.6 Release Notes
The release notes of all 5.6 rWeb and RIOS versions are stored here.
5.6.2 System Release Notes (RIOS v5.6.2)
RIOS v5.6.2 (RE2000, RE4000, RE2200, RE4200, RE5200, RX10, RS10, RS30, RG)
A RioRey license is required to upgrade a filter device to RIOS 5.3.0 or later. If you don't have one, please contact RioRey.
Bug Fixes
- Fixed an issue in AT17 where invalid analysis values were being used. AT17 filtering should now be improved and more predictable.
- Whitelisted destinations will no longer report victims for null or private address space IPs.
- Implemented an advanced recovery method for RS30s that will prevent bypass mode from being triggered under non-critical conditions.
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 5.6.0.release (No rWeb upgrade required)
5.6.1 System Release Notes (RIOS v5.6.1)
RIOS v5.6.1 (RE2000, RE4000, RE2200, RE4200, RE5200, RX10, RS10, RS30, RG)
A RioRey license is required to upgrade a filter device to RIOS 5.3.0 or later. If you don't have one, please contact RioRey.
Bug Fixes
- Fixed a control flow issue caused during TCP option processing.
- AT3 will no longer count Selective ACK (SACK) packets as excessive duplicates.
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 5.6.0.release (No rWeb upgrade required)
5.6.0 System Release Notes (RIOS v5.6.0, rWeb 5.6.0.release)
RIOS v5.6.0 (RE2000, RE4000, RE2200, RE4200, RE5200, RX10, RS10, RS30, RG)
A RioRey license is required to upgrade a filter device to RIOS 5.3.0 or later. If you don't have one, please contact RioRey.
New Features
- AT8 has a new set of algorithms for defending against session attacks.
Enhancements
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 5.6.0.release
New Features
- IP Search implements a global platform search for configuration/filtering information by IP and prefix.
- rWeb disk usage can be managed to automatically delete unused historical data.
- Filter List with RIOS 5.6.0 allows historical and more powerful searches.
- Reports can now be customized with a new logo.
Enhancements
- Net Stats can now be viewed by Customer, Zone, Device, and Interface perspectives.
- rWeb can be rebooted or shut down from the web interface.
- Device status queries are faster.
- rWeb now accepts HTTP browser connections, which will be forwarded to HTTPS.
- Blacklist and Whitelist entries can now be made in the Default Zone.
Bug Fixes
- Patch for SSL CRIME vulnerability.
- Patch for Logjam attack.
- Fixed display bugs on the device zone usage page.
- Support uploads no longer render on other device pages.
- Various attack subtype displays fixed.
- Multiple local users can be added at one time.
- Fixed display issues when creating multiple zone charts.
- Excessively high rates of email notifications will be throttled.
- Templates on new systems will now save correctly on the first attempt.
- Fixed various typos.
- Fixed subtype display on the victims detail page.
- Multiple support uploads can be safely generated at the same time.
- Email notifications will now be properly generated for short lived victims.
- Device configuration is now fully properly pushed following a loss of connectivity.
- Top Attacker percentages now calculated correctly.
- Failed support uploads will not impact other processes.
- Expired blacklist entries will no longer count against filter device limits.
- Rapid whitelist or blacklist updates will no longer cause excessive disk usage.
- 'Infinity' timestamps are now represented as the string 'Infinity' in JSON.
This change may break previously existing API scripts which handle victim data.
Known Issues
- For users who have restricted port 80 access to rWeb, there is a redirect issue. If your rWeb is available at 'rweb.address', and you try to visit https://rweb.address/, this will do a redirect to http://rweb.address/ before redirecting you to https://rweb.address/rWeb_GWT/. With port 80 restricted, this intermediate redirect will fail and it will look like rWeb is inaccessible. As a temporary workaround, please navigate directly to https://rweb.address/rWeb_GWT/.