From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core Update 181 (testing) report
Date: Tue, 07 Nov 2023 21:58:47 +0100 [thread overview]
Message-ID: <6d15b618-2157-4c9b-a2b8-d199609c934e@ipfire.org> (raw)
In-Reply-To: <b9289ea1-03f9-4745-8571-8fc4554496b9@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1612 bytes --]
Hi All,
Have also been testing since it was issued.
Have confirmed that OpenVPN RW and N2N are both working as expected.
Also fix for bug 11048 in OpenVPN has been confirmed to work, also when restoring old backups.
No problems found with any graphs.
Backup and restore worked with no problems.
IPS running with ET community and Abuse.ch rulesets with no issues.
Web Proxy with Conventional mode and using both DNS and DHCP for providing info to FireFox browser. No issues found.
SSH connection working with no issues.
OpenVPN RW connection logs and graphs working as expected.
vm system used for testing has a raid setup for the main IPFire system.
ExtraHD with LVM volumes (one on a partition and the other on the whole drive) mounted and accessible as expected.
Regards,
Adolf.
On 07/11/2023 19:16, Peter Müller wrote:
> Hello *,
>
> Core Update 181 (testing; https://blog.ipfire.org/post/ipfire-2-27-core-update-181-is-available-for-testing)
> is running here for about 24 hours by now without any issues observed so far.
>
> 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 this Core Update.
>
> Thanks, and best regards,
> Peter Müller
prev parent reply other threads:[~2023-11-07 20:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-11-07 18:16 Peter Müller
2023-11-07 20:58 ` Adolf Belka [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=6d15b618-2157-4c9b-a2b8-d199609c934e@ipfire.org \
--to=adolf.belka@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