public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: "Peter Müller" <peter.mueller@ipfire.org>
To: development@lists.ipfire.org
Subject: Core Update 182 (testing) report
Date: Sat, 23 Dec 2023 21:08:00 +0000	[thread overview]
Message-ID: <10318499-4809-4443-8901-dbb2be25a533@ipfire.org> (raw)
In-Reply-To: <87a92d05-0415-4692-8b07-5cd84a308736@ipfire.org>

[-- Attachment #1: Type: text/plain, Size: 1613 bytes --]

Hello *,

better late than never, some testing feedback on Core Update 182: Having
upgraded to "master/7270984c", all IPFire features tested (complete list
below) work fine. This particularly applied to Squid 6.6, which was
occasionally crashing with the following message before (version 6.5):

> 2023/12/20 13:41:36 kid1| FATAL: assertion failed: peer_digest.cc:399: "fetch->pd && receivedData.data"

This problem did not occur on any IPFire installations running Core Update
181, and the combination of Squid 6.6 and potentially having shipped changed
libgcc_s.so.1 appears to have resolved whatever the underlying root cause
was.

During the upgrade, I noticed the following warning emitted by dracut:

> dracut: Skipping program /bin/loginctl using in udev rule 71-seat.rules as it cannot be found

It does not appear to have a functional impact on Core Update 182 though.

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 minimization)
- Dynamic DNS
- Tor (relay mode)

I am looking forward to the release of this Core Update. My apologies for
the library deletion and ALSA firmware quirks initially introduced by me
in Core Update 182, and thanks to Arne for fixing both.

Merry Christmas, if you celebrate. Enjoy the holiday, if not.

Thanks, and best regards,
Peter Müller

      parent reply	other threads:[~2023-12-23 21:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <170179650558.1017810.9287558036661477115.ipfire@ipfire.org>
2023-12-06  9:45 ` Feedback on IPFire 2.27 - Core Update 182 is available for testing Adolf Belka
2023-12-06  9:59   ` Adolf Belka
2023-12-06 10:07     ` Michael Tremer
2023-12-06 10:13       ` Adolf Belka
2023-12-06 13:42         ` Adolf Belka
2023-12-06 14:51           ` Michael Tremer
2023-12-23 21:08   ` Peter Müller [this message]

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=10318499-4809-4443-8901-dbb2be25a533@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