Sophos Firewall: v19.0 MR1: Feedback and experiences

It looks like there was a sudden jump in memory usage. top is showing snort processes consuming the most currently.

Does any of those time values match with the sudden increase of the RAM? 

You see the run time and the increase seems to be some hours ago. Which process matches? 

Looking at the memory usage graph, it appears the increase in memory was at 3:34 AM local time. It was around 9:00 AM local time when I looked at top, so about 5 hours and 30 minutes from the increase in memory usage. It looks like it was an increase of 1,437 MB and I none of the times in top seem to correspond to an increase around that time (just looking at what appears to be the uptime for each process in top). 

I’ll keep letting it run for now to see what happens but I’ll reboot at some point if nothing changes and try to get some before and after screenshots.

Hello shred,

I have exactly the same experience on my virtual app. For a long time, the RAM memory is at about 50%, but now it is at 89%. But according to the RAM load graph, the spike didn't come until midday today. Probably a bad snort engine update?

Regards

alda

Ah that’s a good point on updates. Looking at mine, it looks like my IPS signatures haven’t been updated since 28 Jul but my AV and ATP was updated at 03:29:01, Aug 01 2022 which corresponds closely to the big jump in memory usage.

You can give me a Support Access ID and i will forward this for further inspection. 

Sent you a message with the Access ID. Also, I can see my memory use has increased to 91% and checking top, it’s definitely the snort processes increasing in memory usage.

Avira and ATP came through at the same time and memory use has grown.

Ian

Just to wrap up: 

NC-100681

Increase in snort memory with ATP pattern updates

Temporary workaround provided by Support Engineer which I believe I can share here.

You need to modify the timer value in /sys/class/net/<affected_interface_name>/bridge/ageing_time from 0 to 30000. In my case:

# echo 30000 > /sys/class/net/wlnet3/bridge/ageing_time

After above modification traffic started to hit the firewall rule as before the upgrade to v19.0.1 MR-1.