Re: IPFire 2.29 - Core Update 191 is available for testing

Re: IPFire 2.29 - Core Update 191 is available for testing

[Adolf Belka]

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

Hi All,

I have found that some things didn't get shipped in CU191.

I have looked through all the changes and I believe that the following 5 are the only things (but don't hold me to it). The list of updates was quite large so that a few got missed is not so surprising.

ipblocklists/sources	- confirmed in the updated system by checking the sources file
wlanap.cgi		- confirmed in the updated system with one of the changes
squid
dhcpcd			- confirmed in the updated system by checking version
initscripts/functions	- confirmed in the updated system by checking the functions file


Regards,
Adolf.

On 03/01/2025 17:37, IPFire Project wrote:
> Happy New Year! I hope everyone had a great start. The IPFire development team has been very busy over the holidays and is bringing you the latest update for IPFire ready for testing. It comes yet again with a huge amount of package updates to keep your firewall up to date and IPFire the modern Linux OS that it is. The update also includes a number of smaller bug fixes and groundwork for some bigger changes that will be released over the next couple of updates.
> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
> 
> 
>   IPFire_
> 
> 
>   IPFire 2.29 - Core Update 191 is available for testing
> 
> Happy New Year! I hope everyone had a great start. The IPFire development team has been very busy over the holidays and is bringing you the latest update for IPFire ready for testing. It comes yet again with a huge amount of package updates to keep your firewall up to date and IPFire the modern Linux OS that it is. The update also includes a number of smaller bug fixes and groundwork for some bigger changes that will be released over the next couple of updates.
> 
> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-191-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>
> 

Re: IPFire 2.29 - Core Update 191 is available for testing

[Arne Fitzenreiter]

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

Hi Adolf,

I can confirm:
ipblocklists/sources and initscripts/functions

but wlanap.cgi (it is also not in core system), squid and dhcpcd are not 
touched since core190.

should we reship this anyways and bump hostapd version?

Arne



Am 2025-01-03 21:42, schrieb Adolf Belka:
> Hi All,
> 
> I have found that some things didn't get shipped in CU191.
> 
> I have looked through all the changes and I believe that the following 
> 5 are the only things (but don't hold me to it). The list of updates 
> was quite large so that a few got missed is not so surprising.
> 
> ipblocklists/sources	- confirmed in the updated system by checking the 
> sources file
> wlanap.cgi		- confirmed in the updated system with one of the changes
> squid
> dhcpcd			- confirmed in the updated system by checking version
> initscripts/functions	- confirmed in the updated system by checking the 
> functions file
> 
> 
> Regards,
> Adolf.
> 
> On 03/01/2025 17:37, IPFire Project wrote:
>> Happy New Year! I hope everyone had a great start. The IPFire 
>> development team has been very busy over the holidays and is bringing 
>> you the latest update for IPFire ready for testing. It comes yet again 
>> with a huge amount of package updates to keep your firewall up to date 
>> and IPFire the modern Linux OS that it is. The update also includes a 
>> number of smaller bug fixes and groundwork for some bigger changes 
>> that will be released over the next couple of updates.
>> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>> 
>> 
>>   IPFire_
>> 
>> 
>>   IPFire 2.29 - Core Update 191 is available for testing
>> 
>> Happy New Year! I hope everyone had a great start. The IPFire 
>> development team has been very busy over the holidays and is bringing 
>> you the latest update for IPFire ready for testing. It comes yet again 
>> with a huge amount of package updates to keep your firewall up to date 
>> and IPFire the modern Linux OS that it is. The update also includes a 
>> number of smaller bug fixes and groundwork for some bigger changes 
>> that will be released over the next couple of updates.
>> 
>> Read The Full Post On Our Blog 
>> <https://www.ipfire.org/blog/ipfire-2-29-core-update-191-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>
>> 

Re: IPFire 2.29 - Core Update 191 is available for testing

[Adolf Belka]

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

Hi Arne,

On 07/01/2025 09:46, Arne Fitzenreiter wrote:
> Hi Adolf,
> 
> I can confirm:
> ipblocklists/sources and initscripts/functions
> 
> but wlanap.cgi (it is also not in core system), squid and dhcpcd are not touched since core190.

When I was looking through the git repo list of commits I went past the one called "core191: start updater"

So I was also checking the commits from CU190.
> 
> should we reship this anyways and bump hostapd version?

squid I didn't test when I checked it. Using squid -v I can confirm it was correctly updated in CU190 and so no problem for CU191.

dhcpcd had a version update in CU190 but it turns out it wasn't shipped in CU190 and so that is why dhcpcd --version shows the old version in CU190 and in CU191. So dhcpcd could definitely do with shipping again.

wlanap.cgi is a very interesting situation.
It turns out that it is installed when you do a fresh install but if you don't have hostapd installed then it never gets updated.
If you install hostapd it then gets updated to the latest version and if you then uninstall hostapd then wlanap.cgi is also removed.

It turns out that wlanap.cgi is not commented out in the web-user-interface rootfile.

So when I was checking I was doing it with an old version of wlanap.cgi in my vm testbed, because I don't have hostapd installed on it.

So all the wlanap.cgi updates were correctly installed and I confirmed this by installing hostapd and then checking some of the commit changes in the freshly installed wlanap.cgi

I will provide a patch to correct the web-user-interface rootfile. Not critical for this to go into CU191 Testing as wlanap.cgi has been uncommented since at least CU90 and probably from when it was first created.

So sorry for my error although it did allow me to find some interesting things.

Regards,
Adolf.

> 
> Arne
> 
> 
> 
> Am 2025-01-03 21:42, schrieb Adolf Belka:
>> Hi All,
>>
>> I have found that some things didn't get shipped in CU191.
>>
>> I have looked through all the changes and I believe that the following 5 are the only things (but don't hold me to it). The list of updates was quite large so that a few got missed is not so surprising.
>>
>> ipblocklists/sources    - confirmed in the updated system by checking the sources file
>> wlanap.cgi        - confirmed in the updated system with one of the changes
>> squid
>> dhcpcd            - confirmed in the updated system by checking version
>> initscripts/functions    - confirmed in the updated system by checking the functions file
>>
>>
>> Regards,
>> Adolf.
>>
>> On 03/01/2025 17:37, IPFire Project wrote:
>>> Happy New Year! I hope everyone had a great start. The IPFire development team has been very busy over the holidays and is bringing you the latest update for IPFire ready for testing. It comes yet again with a huge amount of package updates to keep your firewall up to date and IPFire the modern Linux OS that it is. The update also includes a number of smaller bug fixes and groundwork for some bigger changes that will be released over the next couple of updates.
>>> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>>>
>>>
>>>   IPFire_
>>>
>>>
>>>   IPFire 2.29 - Core Update 191 is available for testing
>>>
>>> Happy New Year! I hope everyone had a great start. The IPFire development team has been very busy over the holidays and is bringing you the latest update for IPFire ready for testing. It comes yet again with a huge amount of package updates to keep your firewall up to date and IPFire the modern Linux OS that it is. The update also includes a number of smaller bug fixes and groundwork for some bigger changes that will be released over the next couple of updates.
>>>
>>> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-191-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>
>>>

Re: IPFire 2.29 - Core Update 191 is available for testing

[Adolf Belka]

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

Hi Arne,

I have confirmed that the ipblocklists/sources, initscripts/functions and dhcpcd are all now updated as expected in Core Update 191 Testing.

So that covers everything that I have identified up to this point.

Regards,

Adolf.

On 07/01/2025 12:15, Adolf Belka wrote:
> Hi Arne,
>
> On 07/01/2025 09:46, Arne Fitzenreiter wrote:
>> Hi Adolf,
>>
>> I can confirm:
>> ipblocklists/sources and initscripts/functions
>>
>> but wlanap.cgi (it is also not in core system), squid and dhcpcd are not touched since core190.
>
> When I was looking through the git repo list of commits I went past the one called "core191: start updater"
>
> So I was also checking the commits from CU190.
>>
>> should we reship this anyways and bump hostapd version?
>
> squid I didn't test when I checked it. Using squid -v I can confirm it was correctly updated in CU190 and so no problem for CU191.
>
> dhcpcd had a version update in CU190 but it turns out it wasn't shipped in CU190 and so that is why dhcpcd --version shows the old version in CU190 and in CU191. So dhcpcd could definitely do with shipping again.
>
> wlanap.cgi is a very interesting situation.
> It turns out that it is installed when you do a fresh install but if you don't have hostapd installed then it never gets updated.
> If you install hostapd it then gets updated to the latest version and if you then uninstall hostapd then wlanap.cgi is also removed.
>
> It turns out that wlanap.cgi is not commented out in the web-user-interface rootfile.
>
> So when I was checking I was doing it with an old version of wlanap.cgi in my vm testbed, because I don't have hostapd installed on it.
>
> So all the wlanap.cgi updates were correctly installed and I confirmed this by installing hostapd and then checking some of the commit changes in the freshly installed wlanap.cgi
>
> I will provide a patch to correct the web-user-interface rootfile. Not critical for this to go into CU191 Testing as wlanap.cgi has been uncommented since at least CU90 and probably from when it was first created.
>
> So sorry for my error although it did allow me to find some interesting things.
>
> Regards,
> Adolf.
>
>>
>> Arne
>>
>>
>>
>> Am 2025-01-03 21:42, schrieb Adolf Belka:
>>> Hi All,
>>>
>>> I have found that some things didn't get shipped in CU191.
>>>
>>> I have looked through all the changes and I believe that the following 5 are the only things (but don't hold me to it). The list of updates was quite large so that a few got missed is not so surprising.
>>>
>>> ipblocklists/sources    - confirmed in the updated system by checking the sources file
>>> wlanap.cgi        - confirmed in the updated system with one of the changes
>>> squid
>>> dhcpcd            - confirmed in the updated system by checking version
>>> initscripts/functions    - confirmed in the updated system by checking the functions file
>>>
>>>
>>> Regards,
>>> Adolf.
>>>
>>> On 03/01/2025 17:37, IPFire Project wrote:
>>>> Happy New Year! I hope everyone had a great start. The IPFire development team has been very busy over the holidays and is bringing you the latest update for IPFire ready for testing. It comes yet again with a huge amount of package updates to keep your firewall up to date and IPFire the modern Linux OS that it is. The update also includes a number of smaller bug fixes and groundwork for some bigger changes that will be released over the next couple of updates.
>>>> ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌ ‌
>>>>
>>>>
>>>>   IPFire_
>>>>
>>>>
>>>>   IPFire 2.29 - Core Update 191 is available for testing
>>>>
>>>> Happy New Year! I hope everyone had a great start. The IPFire development team has been very busy over the holidays and is bringing you the latest update for IPFire ready for testing. It comes yet again with a huge amount of package updates to keep your firewall up to date and IPFire the modern Linux OS that it is. The update also includes a number of smaller bug fixes and groundwork for some bigger changes that will be released over the next couple of updates.
>>>>
>>>> Read The Full Post On Our Blog <https://www.ipfire.org/blog/ipfire-2-29-core-update-191-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>
>>>>
>