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 163 (testing) report
Date: Sat, 29 Jan 2022 12:55:22 +0000
Message-ID: <4e901b5f-a807-6437-fdc7-27051db7a407@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============1982647308768351149=="
List-Id: <development.lists.ipfire.org>

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

Hello development folks,

Core Update 163 (testing; no release announcement or changelog has been publi=
shed, yet)
is running here for about 24 hours by now without any major issues known so f=
ar.

On my relatively fast, relatively low-latency DSL connection, CAKE did not in=
troduce any
noticeable change so far, but this was kind of expected. It's a bit sad to ha=
ve this
reported, knowing how much effort went into this feature. Let's hope it makes=
 IPFire more
usable behind slow/high-latency internet connections.

Tested IPFire functionalities in detail:
- PPPoE dial-up via a DSL connection
- 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 am looking forward to the release of Core Update 163.

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


--===============1982647308768351149==--