* Re: IPFire 2.29 - Core Update 189 is available for testing
2024-10-02 8:54 ` IPFire 2.29 - Core Update 189 is available for testing Adolf Belka
@ 2024-10-02 9:14 ` Adolf Belka
0 siblings, 0 replies; 2+ messages in thread
From: Adolf Belka @ 2024-10-02 9:14 UTC (permalink / raw)
To: development
[-- Attachment #1: Type: text/plain, Size: 3693 bytes --]
Hi All,
Besides the minor issue in the mail below, CU189 Testing has gone very well.
Confirmed that the suricata open all ports issue is no longer present if suricata crashes. Also if it does crash the watcher restarts it with no problems.
The issue with not being able to add new OpenVPN clients if the Static Pool addresses was enabled has been fixed.
The existing OpenVPN RW and N2N connections all continue to work and creating new ones also worked without any problems.
I have also tested completely removing the x509 certificate set from the OpenVPN page and re-creating everything from scratch and it all worked without problems.
Now that I have a Prime system also available for testing I have been able to do testing of the wlanap for blue connection.
This would not work properly with CU189 Testing. I think the label marked Broadcast SSID was actually for hiding the ssid and once it was checked it could not be unchecked again with the save button. So the wireless signal was not seen by my laptop or my phone.
Updating the Prime to CU190 Unstable allowed the wlanap to function correctly. The label was now Hide ssid and it could be unchecked. Unchecking it allowed the wifi connection to be seen by my phone and laptop and a connection could be successfully made with it.
I think the intention was to backport the wlanap.cgi changes from next to master but they are not in master. I think that would be something worthwhile to consider doing for CU189 Testing before releasing it.
Someone in the forum was having problems with CU188 if they had WPA2+WPA3 selected in the wlanap.cgi page. There WPA2 printer would not connect.
I wasn't able to test this out with CU188 at this point in time but I could confirm that with CU190 Unstable the wlanap.cgi changes allowed me to connect with WPA2 when WPA2+WPA3 was selected in the wlanap.cgi page as the protocol.
Regards,
Adolf.
On 02/10/2024 10:54, Adolf Belka wrote:
> Hi All,
>
> One thing I have noticed from the update (although, looking back I have realised it was already missing in CU188), is that the red and orange colouring on the dhcp Fixed Leases table for fixed IP's that are within the dynamic range (red) and for IP's that are outside the green and blue subnets (orange) has disappeared. This probably happened when the table colouring standardisation was done.
>
> A fix for it could also wait till CU190 as CU189 has been in Testing for a while now.
>
> Regards,
> Adolf.
>
>
> On 25/09/2024 13:15, IPFire Project wrote:
>> IPFire 2.29 - Core Update 189 is ready to be tested. It comes with a security fix and a new graph for the IPS as well as a large number of package updates. It is one of the largest update that we have ever shipped because it brings a large number of new and updated firmware files for a lot of hardware.
>>
>>
>>
>> IPFire_
>>
>>
>> IPFire 2.29 - Core Update 189 is available for testing
>>
>> IPFire 2.29 - Core Update 189 is ready to be tested. It comes with a security fix and a new graph for the IPS as well as a large number of package updates. It is one of the largest update that we have ever shipped because it brings a large number of new and updated firmware files for a lot of hardware.
>>
>> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-189-is-available-for-testing?utm_medium=email&utm_source=blog-announcement>
>>
>> The IPFire Project, c/o Lightning Wire Labs GmbH, Gerhardstraße 8, 45711 Datteln, Germany
>>
>> Unsubscribe <https://www.ipfire.org/unsubscribe>
>>
>
^ permalink raw reply [flat|nested] 2+ messages in thread