From mboxrd@z Thu Jan 1 00:00:00 1970 From: Adolf Belka To: development@lists.ipfire.org Subject: Re: IPFire 2.27 - Core Update 165 is available for testing Date: Thu, 17 Mar 2022 10:50:47 +0100 Message-ID: In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/mixed; boundary="===============1584660949653239869==" List-Id: --===============1584660949653239869== Content-Type: text/plain; charset="utf-8" Content-Transfer-Encoding: quoted-printable Hi All, Further update. I registered for the Talos VRT Registered rulesets. I then=C2=A0 added the set to my IPS and after a while the IPS page came back= now with Talos VRT added to the providers. I then pressed customise ruleset = and got the rules. I selected some rulesets from Talos and then pressed apply= . I got the spinning symbol and the browser status bar showed activity ongoin= g. After some time the browser pointer spinning disk disappeared and the stat= us bar was empty but the IPFire IPS spinning symbol continued. I checked in /= tmp and there was no lock file but there was an ids_tmp directory. I then selected another wui menu and then went back to the IPS menu and got t= he screen with three providers. Selected customise ruleset again and got the = table headed ruleset with the buttons Back and Apply but absolutely no rulese= ts. I then deleted the Talos VRT ruleset and after some time got back the main pa= ge with only two providers now. I then pressed customise ruleset again and got all the rulesets for the two r= emaining providers back again. So the Talos VRT Registered ruleset=C2=A0 still has some issues. Regards, Adolf. On 17/03/2022 10:29, Adolf Belka wrote: > 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 s= howed on the WUI page as being set for daily. > > After some searching I found that the suricata rules update link was not se= t in the /etc/fcron.daily directory. Pressing save on the IPS page made no di= fference. > 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 presse= d save and now I have the link in my fcron.daily directory but it was not pre= sent after the upgrade process. > > It is no running with updated rulesets and I will check tomorrow how the up= date went. > > In terms of test results, everything was running after the upgrade (On my t= estbed I have everything set up and running although I don't yet have a worki= ng 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* >> >> =C2=A0=C2=A0=C2=A0 Another update is ready for testing: IPFire 2.27 - Core= Update 165. It comes with various updates for the firewall engine that impro= ve its performance and increase its flexibility, as well as with an updated t= oolchain, Python 3.10 and various more bug and security fixes. >> >> Click Here To Read More >> >> The IPFire Project >> Don't like these emails? Unsubscribe . >> --===============1584660949653239869==--