public inbox for development@lists.ipfire.org
 help / color / mirror / Atom feed
From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.27 - Core Update 164 is available for testing
Date: Mon, 21 Feb 2022 16:08:36 +0100	[thread overview]
Message-ID: <e44bbc74-a6cd-9f66-0bbe-92429058c143@ipfire.org> (raw)
In-Reply-To: <fc9abe5a-8e31-d857-e5bd-191eb63e158b@ipfire.org>

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

Hi All,

One thing I have noticed is that the help button on the Intrusion Prevention System page take you to the IPS Logs wiki page and not to the IPS setup wiki page. I will submit a patch to fix that but it's not an issue to do specifically with CU164.


Regards,

Adolf.

On 21/02/2022 16:01, Adolf Belka wrote:
> Hi All,
>
> Just tested out CU164 on my vm testbed system.
>
> The update went without any problems. You see the pakfire log status again on the wui page during the update.
>
> OpenVPN RW setup ran without any issues. Connection successfully made.
>
> IPS has the multiple providers option successfully in place. I eventually found the Force Update of rules button, which was very useful for my vm testbed as it is not running all the time and so the rules were a bit out of date.
>
> As far as I can tell everything is working fine on it. No issues detected.
>
> I will let it run over the next few days during the daytime and see how things go.
>
> Regards,
>
> Adolf.
>
>
> On 20/02/2022 18:35, IPFire Project wrote:
>> IPFire Logo
>>
>> there is a new post from Michael Tremer on the IPFire Blog:
>>
>> *IPFire 2.27 - Core Update 164 is available for testing*
>>
>>     It is time to test another release for IPFire: IPFire 2.27 - Core Update 164. It comes with a vastly improved firewall engine, a new kernel and various security and bug fixes. Please help us testing this release and if you would like to support us, please donate.
>>
>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-164-is-available-for-testing>
>>
>> The IPFire Project
>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>

  reply	other threads:[~2022-02-21 15:08 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <164537850759.17885.12515633604045912133.ipfire@ipfire.org>
2022-02-21 15:01 ` Adolf Belka
2022-02-21 15:08   ` Adolf Belka [this message]
2022-02-21 15:28     ` Adolf Belka
2022-02-21 17:44       ` Jon Murphy
2022-02-21 18:03         ` Adolf Belka
2022-02-23 20:43   ` Core Update 164 (testing) report Peter Müller
2024-05-18 16:11   ` Core Update 186 " Peter Müller

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=e44bbc74-a6cd-9f66-0bbe-92429058c143@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