Sophos Firewall: v19.5 EAP1: Feedback and experiences

Thank you for the update. I am aware that you are a home user and contribute with testing. I am interested in memory because my 4gb XG115w has a very high memory use and wondering if the EAP will break it. The memory use cycles between 73% and 83%.

Ian

Just for some insights: Memory consumption is not as bad as it looks like. So a (linux based) system can run with something like 95% used memory without any problem. If there is a "mem leak" (means the memory increases overtime until all memory is consumed), you need to take action. But looking at a "stable amount of memory", is looking fine to me. The system performs not better or worse if you have 75 or 85% memory consumption. 

Will this EAP have multiple builds? Or It will have other features that will be added later on?

Thank you, I am aware of that memory function, I am more concerned if the requirement goes over 100% and swapping starts.

As it is now I get services stopping then starting two or three days later for no reason that I can see or is logged.

Ian

Potentially no. It could be a fix build as EAP2 and then GA. Features could be added in MR Versions after GA. 

Also, we are now able to change log rotation behaviour by modifying /static/logrotate/logrotate.conf. E.g. you can change amount of rotations and each log file's maximum file size. This was not possible previously.

Kind regards,

cougz

Installed the sig file.

memory sitting around 83% and failing.

CPU 13-37% and climbing. Now the IPS has updated the CPU load has dropped significantly.

IPS updates failed, but that appears to have happened before the v19.5 EAP was installed.Forced update has not fixed the issue. v18.19.68. After the re-login and check the IPS has updated, same version but now updated to 1207 in lieu of 0505 this morning.

Automatic logout time is very short.

Ian

observation, GUI is way slower than v19.0.x

Ian

I have been observing this behaviour over the last 48hrs.
Memory climbed to around 87% right after upgrading the FW. GUI was slower.

After about 24 hours memory usage started dropping to around 71% and has been sitting there. Feels like GUI reaction time has increased.

Makes me wonder why the first 24hrs memory was this high....

The memory issue is something I have noticed and commented on in most releases, something to do with various processes settling and optimising in would be my guess.

Ian