From: Adolf Belka <adolf.belka@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: IPFire 2.27 - Core Update 165 is available for testing
Date: Thu, 17 Mar 2022 10:29:14 +0100 [thread overview]
Message-ID: <d9e62ea3-2dc1-5278-c2b8-1b0f533d9249@ipfire.org> (raw)
In-Reply-To: <164734440708.2330719.8637606495269936408.ipfire@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 2091 bytes --]
Hi All,
Running 165 Testing for a day now. Most things working well.
One thing I found is that this morning the daily update of the IPS rulesets had not taken place although the updates were set to occur in 163 and also showed on the WUI page as being set for daily.
After some searching I found that the suricata rules update link was not set in the /etc/fcron.daily directory. Pressing save on the IPS page made no difference.
I then changed the setting to weekly and pressed save and the link was then created in the fcron.weekly directory. Then I changed it to daily and pressed save and now I have the link in my fcron.daily directory but it was not present after the upgrade process.
It is no running with updated rulesets and I will check tomorrow how the update went.
In terms of test results, everything was running after the upgrade (On my testbed I have everything set up and running although I don't yet have a working IPSec client but that should be available for the next testing.
OpenVPN Roadwarrior connections successfully running.
Web Proxy is up and running and working.
Openssh is up and working.
OpenVPN Roadwarrior connections log working.
Domain Name System fully working with five DNS TLS servers.
DHCP server up and fully working.
Backup system working.
All graphs working as before.
All Firewall Log Charts working.
Regards,
Adolf.
On 15/03/2022 12:40, IPFire Project wrote:
> IPFire Logo
>
> there is a new post from Michael Tremer on the IPFire Blog:
>
> *IPFire 2.27 - Core Update 165 is available for testing*
>
> Another update is ready for testing: IPFire 2.27 - Core Update 165. It comes with various updates for the firewall engine that improve its performance and increase its flexibility, as well as with an updated toolchain, Python 3.10 and various more bug and security fixes.
>
> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-165-is-available-for-testing>
>
> The IPFire Project
> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>
next parent reply other threads:[~2022-03-17 9:29 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <164734440708.2330719.8637606495269936408.ipfire@ipfire.org>
2022-03-17 9:29 ` Adolf Belka [this message]
2022-03-17 9:50 ` Adolf Belka
2022-03-18 11:37 ` Adolf Belka
2022-03-18 12:58 ` Adolf Belka
2022-03-20 10:35 ` Core Update 165 (testing) report Peter Müller
2022-03-21 16:05 ` Michael Tremer
2022-03-23 17:08 ` [PATCH] rules.pl: Fix creating rules for location based groups Stefan Schantl
2022-03-23 17:12 ` 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=d9e62ea3-2dc1-5278-c2b8-1b0f533d9249@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