XG17 GA bug

I'm one of those affected as well.  I started a topic in the regular XG forum about /bin/networkd pegging the cpu.  I'm using the XG at home and upgraded my machine from 16MR8 to 17GA.

Hi TylerTodd,

Thank you for the Feedback.

For further communication sending you PM.

Regards,

Deepti

same issue here, already raised on forum, keep getting locked out every 2 days which requires reboot

Dear Sir

I also have same issue . My system was hanged after 4 days. I was not able to do ssh and web page was also not opening.Please help.

BR
Vishvas

Hi Vishvas,

              Thanks for the Feedback.         

For further communication sending you PM.

This happened to me after a week and a half of working fine.  Rolled back to 16.5 MR8. 

i,

Thank you all for your feedback and extended support.

We have already identified below issues whose end user symptoms are same but the issues are technically different.

The patch is available and  will be also fixed in SFOSv17 MR1 release which will be soon. I am already in touch with the reported one users in PM for the feedback.

The same issues are with the below thread as well.

https://community.sophos.com/products/xg-firewall/sophos-xg-beta-programs/sfos-v170-beta/f/sfos-v170-beta-feedback/96916/sophos-xg-17-rc1---can-t-login-as-admin-or-user/355596#355596

The issue has been identified in race conditions and listed as below.

NC-22472 - init/system process gets killed

NC-23608 - Kernel crash issue during IPS signature upgrade

NC-22950 - IPSec vpn up-down events causing system to be stuck

Regards,

Deepti

Hi ,

i m also using MY XG with 16MR8. after reading regarding version 17v its better to upgrade 17MR1. this blog is really helpful to people who using SOPHOS.

thanks.

After bricking 2 of our units with the latest firmware upgrade, and the resulting downtime (luckily on the staging network & not production), our forward strategy to get off the the unreliable, buggy, and non production ready XG firmware altogether and use the stable UTM v9 firmware.

Advantages:

• No bricking units when using IPSec connections.
• No bricking on automated, vendor initiated pushes of signature updates
• No more 'Rule 0' nonsense.
• Hopefully 1st level support who can actually assist the clients

Every engineer I've spoken with in the USA (after getting through the off-shored 1st level support) has stated the XG is buggy and the problems we are experiencing do not happen with the UTMv9.

The XG product has been nothing but a time-consuming bug inducing experiment in failure for us.

I did forget to mention other fun things we will miss with the UTMv9 in place

• no more tcpdumping on the console to help the engineers debug
• support for NAT that is not a backdoor kludge
• the ability to download firmware without having to enter additional credentials (the XG firmware download now wants additional credentials you'll be happy to locate when trying to un-brick and roll-back your units)