Related
Recommended
talex

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.

Parents

  • Buen día a todos

    Comento que ayer a eso de las 13 horas local argentina instale las actualizaciones en dos equipos, XG310, XG210 ambos en HA, y tal como lo señala Ryan Partington he tenido algunos inconvenientes con el tema DHCP que se solucionan tras un reinicio del pc de escritorio o refrescando la configuración ip

    cito : Ryan Partington

    is anyone else having the DHCP issue too, whereas clients sometimes don't get their default gateway? As soon as you do ipconfig/renew it's back in action?

    estoy evaluando en el dia de hoy ver si la ocurrencia se repite y/o en caso volver a la versión anterior de firmware

    First of all, I'm using the Google translator

    Good morning to all

    I commented that yesterday at about 13 local hours in Argentina, the updates on two firewalls, XG310, XG210 both in HA, and as what Ryan Partington says has had some problems with the DHCP issue that is solved in a PC restart desktop or refreshing ip configuration

    Cito: Ryan Partington

    Does anyone else have the DHCP problem too, while clients sometimes do not get their default gateway? As soon as you do ipconfig / renew is it back in action?

    I am evaluating today to see if the occurrence is repeated and / or in case of returning to the previous firmware version

Comment

  • Buen día a todos

    Comento que ayer a eso de las 13 horas local argentina instale las actualizaciones en dos equipos, XG310, XG210 ambos en HA, y tal como lo señala Ryan Partington he tenido algunos inconvenientes con el tema DHCP que se solucionan tras un reinicio del pc de escritorio o refrescando la configuración ip

    cito : Ryan Partington

    is anyone else having the DHCP issue too, whereas clients sometimes don't get their default gateway? As soon as you do ipconfig/renew it's back in action?

    estoy evaluando en el dia de hoy ver si la ocurrencia se repite y/o en caso volver a la versión anterior de firmware

    First of all, I'm using the Google translator

    Good morning to all

    I commented that yesterday at about 13 local hours in Argentina, the updates on two firewalls, XG310, XG210 both in HA, and as what Ryan Partington says has had some problems with the DHCP issue that is solved in a PC restart desktop or refreshing ip configuration

    Cito: Ryan Partington

    Does anyone else have the DHCP problem too, while clients sometimes do not get their default gateway? As soon as you do ipconfig / renew is it back in action?

    I am evaluating today to see if the occurrence is repeated and / or in case of returning to the previous firmware version

Children
No Data
Unfiltered HTML