From mboxrd@z Thu Jan  1 00:00:00 1970
From: Peter =?utf-8?q?M=C3=BCller?= <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Core Update 152 (testing) report
Date: Tue, 03 Nov 2020 10:38:29 +0100
Message-ID: <8e28d3e1-98ac-e30d-e083-de4f6c0badca@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6160272401401530058=="
List-Id: <development.lists.ipfire.org>

--===============6160272401401530058==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Hello *,

Core Update 152 (testing, see: https://blog.ipfire.org/post/ipfire-2-25-core-=
update-152-is-available-for-testing)
is running here for about 24 hours without any known issues so far. The updat=
ed Suricata version neither
seems to introduce problems nor solves any I observed in the past. On my test=
ing machine (Intel N3150),
throughput with IPS enabled is about the same compared to Core Update 151.

Tested IPFire functionalities in detail:
- IPsec (N2N connections only)
- Squid (authentication enabled, using an upstream proxy)
- OpenVPN (RW connections only)
- IPS/Suricata (with Emerging Threats ruleset enabled)
- Guardian
- Quality of Service
- DNS (with DNS over TLS and strict QNAME minimisation)
- Dynamic DNS
- Tor (relay mode)

Since I do not use Samba (and never would do so on a firewall for security re=
asons ;-) ), I am unfortunately
unable to test those changes. Besides that, I look forward to the release of =
Core Update 152.

Thanks, and best regards,
Peter M=C3=BCller

--===============6160272401401530058==--