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 156 (testing) report (was: Re: IPFire 2.25 - Core Update 156 available for testing)
Date: Tue, 20 Apr 2021 23:14:18 +0200	[thread overview]
Message-ID: <1f98ab02-a074-3416-3683-0042ca10c111@ipfire.org> (raw)
In-Reply-To: <564fb301-b04c-d3f2-3c15-2dd794706890@ipfire.org>

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

Hello development folks,

Core Update 156 (testing, see: https://blog.ipfire.org/post/ipfire-2-25-core-update-156-available-for-testing)
is running here for about 24 hours by now, with no issues known 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 community ruleset enabled)
- Guardian
- Quality of Service
- DNS (using DNS over TLS)
- Dynamic DNS
- Tor (relay mode)

Looking forward to this Core Update.

Thanks, and best regards,
Peter Müller



  parent reply	other threads:[~2021-04-20 21:14 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <161882580503.27807.11098110518344373131.ipfire@ipfire.org>
2021-04-19 16:48 ` IPFire 2.25 - Core Update 156 available for testing Adolf Belka
2021-04-20  7:54   ` Adolf Belka
2021-04-20 21:14   ` Peter Müller [this message]
2021-04-21 12:25     ` Core Update 156 (testing) report (was: Re: IPFire 2.25 - Core Update 156 available for testing) Adolf Belka
2021-04-21 14:26       ` 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=1f98ab02-a074-3416-3683-0042ca10c111@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