Hi XG Community!

We've released SFOS v17.5.5 MR5 for the Sophos XG Firewall. Initially, the firmware will be available by manual download from your MySophos account. We then make the firmware available via auto-update to a number of customers, which will increase over time.

Please visit the following link for more information regarding the upgrade process: Sophos XG Firewall: How to upgrade the firmware.

What's New in XG Firewall v17.5 MR5

APX 120 support for XG Firewall

The APX 120 is a new entry-level, 2x2 MIMO access point. It comes with dual-radio technology and supports 802.11ac Wave 2 for much improved performance over the equivalent AP Series models. With 17.5 MR5, you would be able to manage APX 120 from XG Firewall.

Issues Resolved in SF 17.5 MR5

  • NC-42458 [Authentication] CAA error "Username already logged in too many times. Client will try again shortly"
  • NC-43413 [Authentication] access_server does not always react to service heartbeats
  • NC-43108 [Email] Unable to use a Russian search string in SMTP quarantine search
  • NC-40223 [Licensing] Unable to send license sync request after not receiving CSR response
  • NC-44226 [Wireless] MAC filtering cannot be configured for a SSID using API

Download

To manually install the upgrade, you can download the firmware from the MySophos portal. Please refer to Sophos XG Firewall: How to upgrade the firmware.

  • 44 comments
  • 0 members are here
  • Installed and running on a very simple implementation.   Will still not send backup by email.  Will still show error on "Sophos Connect Client" update.

    • Just now updated no issues so far .... Email  Backup with external  Email Server is working fine

      • since 17.5.3 (including this release) my firewall rules intermittently display with formatting errors. seems to not show images and whatnot (for example the folder icon for grouped rules). I've seen it on software and hardware appliances - is anyone else other than me getting this?

        • , I have the same problem on every appliance, when using Google Chrome latest version. Sophos supports claims that this is not their problem, and I should contact Google :=). In Firefox, everything is OK, so I'm using Firefox for now.

          • Thanks MiroslavCacija - that makes sense, I do use Chrome too! However I'm a little disappointed Sophos are stepping back away from the issue and pointing the finger at Google. As I say, 17.5.1 - not an issue with Chrome (then there was a strange 17.5.2 version that kinda of did and didn't get released) and then in 17.5.3 I had the issue. So if this helps anyone at Sophos resolve...