Important note about SSL VPN compatibility for 20.0 MR1 with EoL SFOS versions and UTM9 OS. Learn more in the release notes.

This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Sophos Firewall: v20.0 GA: Feedback and experiences

Release Post:  Sophos Firewall v20 is Now Available  

The EAP Post:  Sophos Firewall: v20.0 EAP1: Feedback and experiences  

The old V19.5 MR3 Post:  Sophos Firewall: v19.5 MR3: Feedback and experiences  

To make the tracking of issues / feedback easier: Please post a potential Sophos Support Case ID within your initial post, so we can track your feedback/issue. 

Release Notes:  https://docs.sophos.com/releasenotes/output/en-us/nsg/sf_200_rn.html 



This thread was automatically locked due to age.
Parents
  • In the release notes it was mentioned, that Heartbeat false positives have been reduced: "Synchronized Security has also been enhanced with added scalability and reduced false missing heartbeats for devices that are in a sleep or hibernate state."

    After upgrading to SFOS 20 we still see the same amount of false positives concerning "missing hearbeat" alerts as with v19.x before.

    Can anyone confirm that in v20 anything has changed here to the better and what one can do to improve the situation? Our workaround currently is to avoid S0 (modern standby) as much as possible, but this is not a very convenient solution and is not applicable to every device (MacOS for example).

    Thanks for any comments.

    Hans

Reply
  • In the release notes it was mentioned, that Heartbeat false positives have been reduced: "Synchronized Security has also been enhanced with added scalability and reduced false missing heartbeats for devices that are in a sleep or hibernate state."

    After upgrading to SFOS 20 we still see the same amount of false positives concerning "missing hearbeat" alerts as with v19.x before.

    Can anyone confirm that in v20 anything has changed here to the better and what one can do to improve the situation? Our workaround currently is to avoid S0 (modern standby) as much as possible, but this is not a very convenient solution and is not applicable to every device (MacOS for example).

    Thanks for any comments.

    Hans

Children