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 147 (testing) report
Date: Wed, 08 Jul 2020 19:53:32 +0000	[thread overview]
Message-ID: <d08a2476-274b-a3d1-ff95-2014ad93f3d3@ipfire.org> (raw)

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

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üller


                 reply	other threads:[~2020-07-08 19:53 UTC|newest]

Thread overview: [no followups] expand[flat|nested]  mbox.gz  Atom feed

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=d08a2476-274b-a3d1-ff95-2014ad93f3d3@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