Hello,

Thanks for the report. This sounds really positive.

Did anybody else find anything?

-Michael

On 29 Oct 2019, at 17:54, peter.mueller@ipfire.org wrote:

Hello list,

Core Update 137 (testing, see https://blog.ipfire.org/post/ipfire-2-23-core-update-137-is-available-for-te...) is running here for about 24 hours without any unexpected behaviour so far.

I can confirm new connections are now established immediately, without having a delay until the application or operating system decides do open up a new socket. Thereof, enabling Suricata does not have any noticeable negative side effect (except for some performance things), which I consider to be quite good.

While CPU IRQ usage deceased a bit after installing the Core Update, RAM consumption is now more adaptive (see WebUI graph attached) than before. It looks like some application has learned to free unused memory... :-)

The following parts of IPFire seem to work correctly:

• DDNS
• OpenVPN (RW connections only)
• IPsec (N2N connections only)
• Squid proxy (including authentication and upstream proxy)
• Guardian
• Tor (acting as a relay, no fresh installation, I am aware of bug #12220)
• Quality of Service

Output of "uname -a" for reference purposes:

...

[root@maverick ~]# uname -a Linux maverick 4.14.150-ipfire #1 SMP Tue Oct 22 17:07:54 GMT 2019 x86_64 Intel(R) Celeron(R) CPU N3150 @ 1.60GHz GenuineIntel GNU/Linux

I look forward to an official release of this Core Update.

Thanks, and best regards, Peter Müller <ipfire_core_update_137_testing_ram_consumption_per_week.png>