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 160 (testing) report
Date: Sat, 25 Sep 2021 10:32:53 +0200
Message-ID: <75b3dd8a-4d5e-47a1-175d-de36f6710506@ipfire.org>
In-Reply-To: <0fcd80aa-926b-86ca-2871-9682699269e6@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1358888836765724638=="
List-Id: <development.lists.ipfire.org>

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

Hello *,

Core Update 160 (testing, see: https://blog.ipfire.org/post/ipfire-2-27-core-=
update-160-available-for-testing)
is running here for about two days by now without any known issues so far.

Unfortunately, the cheap Realtek NIC of my testing machine does not benefit f=
rom ntuple offloading, so I am unable
to report back latency improvements in detail. The SVG rendered graphs do loo=
k smoother indeed, especially on
high-resolution screens.

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 community ruleset enabled)
- Guardian
- Quality of Service
- DNS (using DNS over TLS and strict QNAME minimisation)
- Dynamic DNS
- Tor (relay mode)

I look forward to the release of Core Update 160.

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


--===============1358888836765724638==--