From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Core Update 186 (testing) report
Date: Sat, 18 May 2024 16:11:00 +0000 [thread overview]
Message-ID: <a3073c5d-ad78-470a-acbe-88c77f58d7df@ipfire.org> (raw)
In-Reply-To: <fc9abe5a-8e31-d857-e5bd-191eb63e158b@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1121 bytes --]
Hello development folks,
Core Update 186 (testing; see: https://www.ipfire.org/blog/ipfire-2-29-core-update-186-is-available-for-testing)
is running here for a couple of days by now without any major issues known so far.
During the update, I merely noticed dracut complaining:
> dracut: Skipping program /bin/loginctl using in udev rule 71-seat.rules as it cannot be found
However, this does not appear to have any noticeable impact whatsoever.
The updated Lynis version now outputs significantly fewer warnings about deprecated
grep parameters, which previously made output hard to read sometimes.
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 186.
Thanks, and best regards,
Peter Müller
next prev parent reply other threads:[~2024-05-18 16:11 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164537850759.17885.12515633604045912133.ipfire@ipfire.org>
2022-02-21 15:01 ` IPFire 2.27 - Core Update 164 is available for testing Adolf Belka
2022-02-21 15:08 ` Adolf Belka
2022-02-21 15:28 ` Adolf Belka
2022-02-21 17:44 ` Jon Murphy
2022-02-21 18:03 ` Adolf Belka
2022-02-23 20:43 ` Core Update 164 (testing) report Peter Müller
2024-05-18 16:11 ` Peter Müller [this message]
[not found] <ebc93bea-279d-4336-99de-8d4f1cd307f4@ipfire.org>
2024-05-28 10:05 ` Core Update 186 " Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=a3073c5d-ad78-470a-acbe-88c77f58d7df@ipfire.org \
--to=peter.mueller@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox