Sophos Firewall: v19.5 MR1: Feedback and experiences

Hello James,

Following up on what Luca mentioned, can you share the Case ID you have with Support?

Take a look at this KB

Regards,

Literally just this second Sophos Support have said that because 19.5.1 is not in "Available to All", that means that no 19.5.x version will be available. That sounds like a bug, but is the best explanation i have heard just now.

Are you okay for me to past the Case ID here?

Hello James,

Thank you for the follow-up.

Feel free to share here or via PM.

Regards,

Hi Emmanuel. Case ID is 06300943, and Sophos Support have just now confirmed that 19.5.1 is now fully GA and I can see that one client shows 19.0.2 and 19.5.1 as available from Sophos Central (LuCar Toni  FYI - they must have fixed the bug you previously indicated).

Our own Sophos is already on 19.5.0 and does not show an option for 19.5.1 from Sophos Central, but I assume I just need to wait another day or two.

It's frustrating though that we have many firewalls across many clients and they all email every few hours to say we should upgrade to the latest version, but we can't upgrade from Sophos Central and so can't use our automation tools to schedule the upgrade.

Hello James,

Thank you for the Case ID and the feedback.

Is your Sophos Firewall now showing 19.5 MR1 in central as an option to download?

Regards,

Yes, like 10 minutes after I posted the above it started showing up

Essentially Sophos controls the Release, which Central shows and when. This will usually not be done on a Device level - Instead for the entire installations base. Therefore the Central component will come up later. 

Can you share the Support ID please? 

I didn't realise how slow my XG115w is until I had to use my mobile hotspot this morning. Site connections are fast, even this forum is quick when compared to accessing it through the XG.

Ian

This has been a very bad experience for us. 

Running 2 XGS21000 in HA mode. 

Since upgrading connectivity to websites is slow, sometimes hangs completely. Some apps will get disconnected after a few minutes of use. This is consistent so has made those apps useless, for example my General Manager has stopped using Sirius XM radio on his desktop because it will not stay connected. When these problems are happening we see many "invalid packet" in the log file for that client and service. This indicates a problem with nf_conntrack but the only thing support has been able to do for the past few weeks is try adjusting the tcp-est-idle-timeout but the timeouts are already happening much sooner than the timeout value. We will probably roll back soon but if we do that how will we know when it's safe to upgrade again? It is a problem.