Some customers are reporting RED-W wireless issues and high CPU usage after updating to UTM v9.6 GA.
Applies to the following Sophos product(s) and version(s) Sophos UTM 9.6 GA
Development is currently investigating.
Verify the issue is occurring by navigating to the wireless log (or /var/log/wireless.log) and look for the following error:
utm awed: [MASTER] new connection from x.x.x.x:54756 utm awed: [AXXXXXXXXXXX] RED15w from x.x.x.x:54756 identified as AXXXXXXXXXXX utm awed: [AXXXXXXXXXXX] (Re-)loaded identity and/or configuration utm awed: [AXXXXXXXXXXX] Corrupt payload. Device may have wrong key. MD5 of the key is yyyyyyyyyyyyyyyyyy. Delete device to re-register it.
Rejoin the AP by:
Wireless should now be connected and CPU usage should return to normal levels.
This article will be updated when new information becomes available
If you've spotted an error or would like to provide feedback on this article, please use the section below to rate and comment on the article. This is invaluable to us to ensure that we continually strive to give our customers the best information possible.
Every comment submitted here is read (by a human) but we do not reply to specific technical questions. For technical support post a question to the community. Or click here for new feature/product improvements. Alternatively for paid/licensed products open a support ticket.