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 152 (testing) report
Date: Tue, 03 Nov 2020 10:38:29 +0100	[thread overview]
Message-ID: <8e28d3e1-98ac-e30d-e083-de4f6c0badca@ipfire.org> (raw)

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

Hello *,

Core Update 152 (testing, see: https://blog.ipfire.org/post/ipfire-2-25-core-update-152-is-available-for-testing)
is running here for about 24 hours without any known issues so far. The updated Suricata version neither
seems to introduce problems nor solves any I observed in the past. On my testing machine (Intel N3150),
throughput with IPS enabled is about the same compared to Core Update 151.

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 I do not use Samba (and never would do so on a firewall for security reasons ;-) ), I am unfortunately
unable to test those changes. Besides that, I look forward to the release of Core Update 152.

Thanks, and best regards,
Peter Müller

                 reply	other threads:[~2020-11-03  9:38 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=8e28d3e1-98ac-e30d-e083-de4f6c0badca@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