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 147 (testing) report
Date: Wed, 08 Jul 2020 19:53:32 +0000
Message-ID: <d08a2476-274b-a3d1-ff95-2014ad93f3d3@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============6960698978479860106=="
List-Id: <development.lists.ipfire.org>

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

Hello *,

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

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 my testing hardware was well supported before this testing Core Update,
there is little noticeable to say. I can confirm bug #11994 being fixed and
am looking forward to the release of this update.

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


--===============6960698978479860106==--