Re: IPFire 2.27 - Core Update 170 is available for testing

Re: IPFire 2.27 - Core Update 170 is available for testing

[Adolf Belka]

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


Hi All,

I just tried out CU170 and tested out the fuse fix for borgbackup.

It failed.

When I tried to do the mount I got the message:-

        fuse: device not found, try 'modprobe fuse' first

I then tried running modprobe fuse and got the following message

        modprobe: FATAL: Module fuse not found in directory /lib/modules/5.15.49-ipfire

I checked and found the modules in directory /lib/modules/5.15.59-ipfire/kernel/fs/fuse/ just the same as in my running CU169.

In CU169 running modprobe fuse causes the module to be loaded successfully.


I am not sure what is different with CU170 and fuse.

Let me know if there is something I need to check out on my vm system.



Regarding the IP Address Blocklists new function. This has already been mentioned on the forum
https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/8400

I confirm the same effect as mentioned in the forum. Trying to enable any list and pressing save gives a clear white page. Reload does not do anything. Rerunning the IPFire web app gives a system with everything still disabled.

Looked in httpd/error_log but no errors from trying to run the ipblocklists page but the following error entries look to have been from the upgrade by pakfire.

Can't locate IO/Socket/INET.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/IO/Socket/INET.pm: Permission denied at /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/IO/Socket.pm line 21.
Compilation failed in require at /var/ipfire/general-functions.pl line 19.
BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line 19.
Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 30.
[Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 123588682180160] [client 192.168.200.10:54370] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
sh: error while loading shared libraries: libreadline.so.8: cannot open shared object file: Permission denied
Can't locate overload.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/overload.pm: Permission denied at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
[Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 123588782827072] [client 192.168.200.10:45148] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
Unable to write file /var/ipfire/ipblocklist/settings at /var/ipfire/general-functions.pl line 256.
Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.


Regards,
Adolf.


On 15/08/2022 18:00, IPFire Project wrote:
> IPFire Logo
> 
> there is a new post from Peter Müller on the IPFire Blog:
> 
> *IPFire 2.27 - Core Update 170 is available for testing*
> 
>     The next Core Update is available for testing. It features new IP blocklists for the firewall engine, significant improvements to Pakfire, modernizes the default cryptographic algorithm selection for IPsec connections, as well as a new kernel, and a plethora of bug fixes and security improvements under the hood.
> 
> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-170-is-available-for-testing>
> 
> The IPFire Project
> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
> 

Re: IPFire 2.27 - Core Update 170 is available for testing

[Adolf Belka]

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

Hi all,


Further follow up on CU170 Testing

Have tested out as many of the menu items that I am able to and have not found any problems with them.

Menu options I can't currently test are:-

IPSec

OpenVPN Site to Site

Quality of Service

URL Filter and Update Accelerator

Captive Portal

DNS Forwarding

Static Routes

Wake on Lan

Assign MAC Address


Everything else has been tested or the output checked and no problems found beyond the original issues with fuse for borgbackup and ipblocklists mentioned in the earlier communication.


Regards,

Adolf.


On 16/08/2022 15:58, Adolf Belka wrote:
>
> Hi All,
>
> I just tried out CU170 and tested out the fuse fix for borgbackup.
>
> It failed.
>
> When I tried to do the mount I got the message:-
>
>        fuse: device not found, try 'modprobe fuse' first
>
> I then tried running modprobe fuse and got the following message
>
>        modprobe: FATAL: Module fuse not found in directory /lib/modules/5.15.49-ipfire
>
> I checked and found the modules in directory /lib/modules/5.15.59-ipfire/kernel/fs/fuse/ just the same as in my running CU169.
>
> In CU169 running modprobe fuse causes the module to be loaded successfully.
>
>
> I am not sure what is different with CU170 and fuse.
>
> Let me know if there is something I need to check out on my vm system.
>
>
>
> Regarding the IP Address Blocklists new function. This has already been mentioned on the forum
> https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/8400
>
> I confirm the same effect as mentioned in the forum. Trying to enable any list and pressing save gives a clear white page. Reload does not do anything. Rerunning the IPFire web app gives a system with everything still disabled.
>
> Looked in httpd/error_log but no errors from trying to run the ipblocklists page but the following error entries look to have been from the upgrade by pakfire.
>
> Can't locate IO/Socket/INET.pm: /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/IO/Socket/INET.pm: Permission denied at /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/IO/Socket.pm line 21.
> Compilation failed in require at /var/ipfire/general-functions.pl line 19.
> BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line 19.
> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 30.
> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 123588682180160] [client 192.168.200.10:54370] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
> sh: error while loading shared libraries: libreadline.so.8: cannot open shared object file: Permission denied
> Can't locate overload.pm: /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/overload.pm: Permission denied at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
> BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
> BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
> [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 123588782827072] [client 192.168.200.10:45148] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/settings at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>
>
> Regards,
> Adolf.
>
>
> On 15/08/2022 18:00, IPFire Project wrote:
>> IPFire Logo
>>
>> there is a new post from Peter Müller on the IPFire Blog:
>>
>> *IPFire 2.27 - Core Update 170 is available for testing*
>>
>>     The next Core Update is available for testing. It features new IP blocklists for the firewall engine, significant improvements to Pakfire, modernizes the default cryptographic algorithm selection for IPsec connections, as well as a new kernel, and a plethora of bug fixes and security improvements under the hood.
>>
>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-170-is-available-for-testing>
>>
>> The IPFire Project
>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>

Re: IPFire 2.27 - Core Update 170 is available for testing

[Adolf Belka]

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

Hi All,


Further follow-up on the ipblocklist issue I mentioned in the first email below.

The version of IPFire was master/ef7d41ef

I have now tried doing as fresh install of the same version and with that the ipblocklist option works without any issues. I get the message to update the Firewall Rules to implement the blocklists.

It looks like the issue with the ipblocklist not functioning that I and others have mentioned is related to something that is occurring or not occurring in the update script as a fresh install works fine but an update from CU169 to CU70 has the problem.

Regards,

Adolf.

On 16/08/2022 16:36, Adolf Belka wrote:
> Hi all,
>
>
> Further follow up on CU170 Testing
>
> Have tested out as many of the menu items that I am able to and have not found any problems with them.
>
> Menu options I can't currently test are:-
>
> IPSec
>
> OpenVPN Site to Site
>
> Quality of Service
>
> URL Filter and Update Accelerator
>
> Captive Portal
>
> DNS Forwarding
>
> Static Routes
>
> Wake on Lan
>
> Assign MAC Address
>
>
> Everything else has been tested or the output checked and no problems found beyond the original issues with fuse for borgbackup and ipblocklists mentioned in the earlier communication.
>
>
> Regards,
>
> Adolf.
>
>
> On 16/08/2022 15:58, Adolf Belka wrote:
>>
>> Hi All,
>>
>> I just tried out CU170 and tested out the fuse fix for borgbackup.
>>
>> It failed.
>>
>> When I tried to do the mount I got the message:-
>>
>>        fuse: device not found, try 'modprobe fuse' first
>>
>> I then tried running modprobe fuse and got the following message
>>
>>        modprobe: FATAL: Module fuse not found in directory /lib/modules/5.15.49-ipfire
>>
>> I checked and found the modules in directory /lib/modules/5.15.59-ipfire/kernel/fs/fuse/ just the same as in my running CU169.
>>
>> In CU169 running modprobe fuse causes the module to be loaded successfully.
>>
>>
>> I am not sure what is different with CU170 and fuse.
>>
>> Let me know if there is something I need to check out on my vm system.
>>
>>
>>
>> Regarding the IP Address Blocklists new function. This has already been mentioned on the forum
>> https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/8400
>>
>> I confirm the same effect as mentioned in the forum. Trying to enable any list and pressing save gives a clear white page. Reload does not do anything. Rerunning the IPFire web app gives a system with everything still disabled.
>>
>> Looked in httpd/error_log but no errors from trying to run the ipblocklists page but the following error entries look to have been from the upgrade by pakfire.
>>
>> Can't locate IO/Socket/INET.pm: /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/IO/Socket/INET.pm: Permission denied at /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/IO/Socket.pm line 21.
>> Compilation failed in require at /var/ipfire/general-functions.pl line 19.
>> BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line 19.
>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 30.
>> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 123588682180160] [client 192.168.200.10:54370] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
>> sh: error while loading shared libraries: libreadline.so.8: cannot open shared object file: Permission denied
>> Can't locate overload.pm: /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/overload.pm: Permission denied at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>> BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
>> BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
>> [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 123588782827072] [client 192.168.200.10:45148] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/settings at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>>
>>
>> Regards,
>> Adolf.
>>
>>
>> On 15/08/2022 18:00, IPFire Project wrote:
>>> IPFire Logo
>>>
>>> there is a new post from Peter Müller on the IPFire Blog:
>>>
>>> *IPFire 2.27 - Core Update 170 is available for testing*
>>>
>>>     The next Core Update is available for testing. It features new IP blocklists for the firewall engine, significant improvements to Pakfire, modernizes the default cryptographic algorithm selection for IPsec connections, as well as a new kernel, and a plethora of bug fixes and security improvements under the hood.
>>>
>>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-170-is-available-for-testing>
>>>
>>> The IPFire Project
>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>>

Re: IPFire 2.27 - Core Update 170 is available for testing

[Michael Tremer]

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

Hi Adolf,

Can we have bugzilla tickets raised for these issues, please?

> On 16 Aug 2022, at 14:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> 
> Hi All,
> 
> I just tried out CU170 and tested out the fuse fix for borgbackup.
> 
> It failed.
> 
> When I tried to do the mount I got the message:-
> 
>       fuse: device not found, try 'modprobe fuse' first
> 
> I then tried running modprobe fuse and got the following message
> 
>       modprobe: FATAL: Module fuse not found in directory /lib/modules/5.15.49-ipfire
> 
> I checked and found the modules in directory /lib/modules/5.15.59-ipfire/kernel/fs/fuse/ just the same as in my running CU169.
> 
> In CU169 running modprobe fuse causes the module to be loaded successfully.
> 
> 
> I am not sure what is different with CU170 and fuse.
> 
> Let me know if there is something I need to check out on my vm system.
> 
> 
> 
> Regarding the IP Address Blocklists new function. This has already been mentioned on the forum
> https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/8400
> 
> I confirm the same effect as mentioned in the forum. Trying to enable any list and pressing save gives a clear white page. Reload does not do anything. Rerunning the IPFire web app gives a system with everything still disabled.
> 
> Looked in httpd/error_log but no errors from trying to run the ipblocklists page but the following error entries look to have been from the upgrade by pakfire.
> 
> Can't locate IO/Socket/INET.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/IO/Socket/INET.pm: Permission denied at /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/IO/Socket.pm line 21.
> Compilation failed in require at /var/ipfire/general-functions.pl line 19.
> BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line 19.
> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 30.
> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 123588682180160] [client 192.168.200.10:54370] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
> sh: error while loading shared libraries: libreadline.so.8: cannot open shared object file: Permission denied
> Can't locate overload.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/overload.pm: Permission denied at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
> BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
> BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
> [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 123588782827072] [client 192.168.200.10:45148] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/settings at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.

Stefan is going to be unavailable for the next couple of weeks. So I will have a go at this :)

-Michael

> 
> 
> Regards,
> Adolf.
> 
> 
> On 15/08/2022 18:00, IPFire Project wrote:
>> IPFire Logo
>> there is a new post from Peter Müller on the IPFire Blog:
>> *IPFire 2.27 - Core Update 170 is available for testing*
>>    The next Core Update is available for testing. It features new IP blocklists for the firewall engine, significant improvements to Pakfire, modernizes the default cryptographic algorithm selection for IPsec connections, as well as a new kernel, and a plethora of bug fixes and security improvements under the hood.
>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-170-is-available-for-testing>
>> The IPFire Project
>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.

Re: IPFire 2.27 - Core Update 170 is available for testing

[Peter Müller]

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

Hello *,

> Hi Adolf,
> 
> Can we have bugzilla tickets raised for these issues, please?

first, thank you for the testing feedback. Second, I second the wish for tickets. :-)

On the general front, apologies for being rather quiet recently. I will work through
the mailing list and community later today and tomorrow, and give Core Update 170 and
all the other things in need of it some love and care.

Also, due to ${dayjob}, I will be unavailable from August 23 to August 29.

Thanks, and best regards,
Peter Müller


> 
>> On 16 Aug 2022, at 14:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>>
>> Hi All,
>>
>> I just tried out CU170 and tested out the fuse fix for borgbackup.
>>
>> It failed.
>>
>> When I tried to do the mount I got the message:-
>>
>>       fuse: device not found, try 'modprobe fuse' first
>>
>> I then tried running modprobe fuse and got the following message
>>
>>       modprobe: FATAL: Module fuse not found in directory /lib/modules/5.15.49-ipfire
>>
>> I checked and found the modules in directory /lib/modules/5.15.59-ipfire/kernel/fs/fuse/ just the same as in my running CU169.
>>
>> In CU169 running modprobe fuse causes the module to be loaded successfully.
>>
>>
>> I am not sure what is different with CU170 and fuse.
>>
>> Let me know if there is something I need to check out on my vm system.
>>
>>
>>
>> Regarding the IP Address Blocklists new function. This has already been mentioned on the forum
>> https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/8400
>>
>> I confirm the same effect as mentioned in the forum. Trying to enable any list and pressing save gives a clear white page. Reload does not do anything. Rerunning the IPFire web app gives a system with everything still disabled.
>>
>> Looked in httpd/error_log but no errors from trying to run the ipblocklists page but the following error entries look to have been from the upgrade by pakfire.
>>
>> Can't locate IO/Socket/INET.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/IO/Socket/INET.pm: Permission denied at /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/IO/Socket.pm line 21.
>> Compilation failed in require at /var/ipfire/general-functions.pl line 19.
>> BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line 19.
>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 30.
>> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 123588682180160] [client 192.168.200.10:54370] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
>> sh: error while loading shared libraries: libreadline.so.8: cannot open shared object file: Permission denied
>> Can't locate overload.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/overload.pm: Permission denied at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>> BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
>> BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
>> [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 123588782827072] [client 192.168.200.10:45148] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/settings at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> 
> Stefan is going to be unavailable for the next couple of weeks. So I will have a go at this :)
> 
> -Michael
> 
>>
>>
>> Regards,
>> Adolf.
>>
>>
>> On 15/08/2022 18:00, IPFire Project wrote:
>>> IPFire Logo
>>> there is a new post from Peter Müller on the IPFire Blog:
>>> *IPFire 2.27 - Core Update 170 is available for testing*
>>>    The next Core Update is available for testing. It features new IP blocklists for the firewall engine, significant improvements to Pakfire, modernizes the default cryptographic algorithm selection for IPsec connections, as well as a new kernel, and a plethora of bug fixes and security improvements under the hood.
>>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-170-is-available-for-testing>
>>> The IPFire Project
>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
> 

Re: IPFire 2.27 - Core Update 170 is available for testing

[Adolf Belka]

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

Hi Peter,

On 19/08/2022 11:12, Peter Müller wrote:
> Hello *,
> 
>> Hi Adolf,
>>
>> Can we have bugzilla tickets raised for these issues, please?
> 
> first, thank you for the testing feedback. Second, I second the wish for tickets. :-)
Will do so.
> 
> On the general front, apologies for being rather quiet recently. I will work through
> the mailing list and community later today and tomorrow, and give Core Update 170 and
> all the other things in need of it some love and care.
No problems, I know you are all very busy people. I know you will get 
round to the emails when you are able to.

Regards,
Adolf.
> 
> Also, due to ${dayjob}, I will be unavailable from August 23 to August 29.
> 
> Thanks, and best regards,
> Peter Müller
> 
> 
>>
>>> On 16 Aug 2022, at 14:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>
>>>
>>> Hi All,
>>>
>>> I just tried out CU170 and tested out the fuse fix for borgbackup.
>>>
>>> It failed.
>>>
>>> When I tried to do the mount I got the message:-
>>>
>>>        fuse: device not found, try 'modprobe fuse' first
>>>
>>> I then tried running modprobe fuse and got the following message
>>>
>>>        modprobe: FATAL: Module fuse not found in directory /lib/modules/5.15.49-ipfire
>>>
>>> I checked and found the modules in directory /lib/modules/5.15.59-ipfire/kernel/fs/fuse/ just the same as in my running CU169.
>>>
>>> In CU169 running modprobe fuse causes the module to be loaded successfully.
>>>
>>>
>>> I am not sure what is different with CU170 and fuse.
>>>
>>> Let me know if there is something I need to check out on my vm system.
>>>
>>>
>>>
>>> Regarding the IP Address Blocklists new function. This has already been mentioned on the forum
>>> https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/8400
>>>
>>> I confirm the same effect as mentioned in the forum. Trying to enable any list and pressing save gives a clear white page. Reload does not do anything. Rerunning the IPFire web app gives a system with everything still disabled.
>>>
>>> Looked in httpd/error_log but no errors from trying to run the ipblocklists page but the following error entries look to have been from the upgrade by pakfire.
>>>
>>> Can't locate IO/Socket/INET.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/IO/Socket/INET.pm: Permission denied at /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/IO/Socket.pm line 21.
>>> Compilation failed in require at /var/ipfire/general-functions.pl line 19.
>>> BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line 19.
>>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 30.
>>> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 123588682180160] [client 192.168.200.10:54370] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
>>> sh: error while loading shared libraries: libreadline.so.8: cannot open shared object file: Permission denied
>>> Can't locate overload.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/overload.pm: Permission denied at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>>> BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
>>> BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
>>> [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 123588782827072] [client 192.168.200.10:45148] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
>>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/settings at /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>>
>> Stefan is going to be unavailable for the next couple of weeks. So I will have a go at this :)
>>
>> -Michael
>>
>>>
>>>
>>> Regards,
>>> Adolf.
>>>
>>>
>>> On 15/08/2022 18:00, IPFire Project wrote:
>>>> IPFire Logo
>>>> there is a new post from Peter Müller on the IPFire Blog:
>>>> *IPFire 2.27 - Core Update 170 is available for testing*
>>>>     The next Core Update is available for testing. It features new IP blocklists for the firewall engine, significant improvements to Pakfire, modernizes the default cryptographic algorithm selection for IPsec connections, as well as a new kernel, and a plethora of bug fixes and security improvements under the hood.
>>>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-170-is-available-for-testing>
>>>> The IPFire Project
>>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
>>

-- 
Sent from my laptop

Re: IPFire 2.27 - Core Update 170 is available for testing

[Michael Tremer]

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

Hi Adolf,

Can we have bugzilla tickets raised for these issues, please?

> On 16 Aug 2022, at 14:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
> 
> 
> Hi All,
> 
> I just tried out CU170 and tested out the fuse fix for borgbackup.
> 
> It failed.
> 
> When I tried to do the mount I got the message:-
> 
>      fuse: device not found, try 'modprobe fuse' first
> 
> I then tried running modprobe fuse and got the following message
> 
>      modprobe: FATAL: Module fuse not found in directory /lib/modules/5.15.49-ipfire
> 
> I checked and found the modules in directory /lib/modules/5.15.59-ipfire/kernel/fs/fuse/ just the same as in my running CU169.
> 
> In CU169 running modprobe fuse causes the module to be loaded successfully.
> 
> 
> I am not sure what is different with CU170 and fuse.
> 
> Let me know if there is something I need to check out on my vm system.
> 
> 
> 
> Regarding the IP Address Blocklists new function. This has already been mentioned on the forum
> https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/8400
> 
> I confirm the same effect as mentioned in the forum. Trying to enable any list and pressing save gives a clear white page. Reload does not do anything. Rerunning the IPFire web app gives a system with everything still disabled.
> 
> Looked in httpd/error_log but no errors from trying to run the ipblocklists page but the following error entries look to have been from the upgrade by pakfire.
> 
> Can't locate IO/Socket/INET.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/IO/Socket/INET.pm: Permission denied at /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/IO/Socket.pm line 21.
> Compilation failed in require at /var/ipfire/general-functions.pl line 19.
> BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line 19.
> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 30.
> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 123588682180160] [client 192.168.200.10:54370] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
> sh: error while loading shared libraries: libreadline.so.8: cannot open shared object file: Permission denied
> Can't locate overload.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/overload.pm: Permission denied at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
> BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
> BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
> [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 123588782827072] [client 192.168.200.10:45148] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/settings at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.

Stefan is going to be unavailable for the next couple of weeks. So I will have a go at this :)

-Michael

> 
> 
> Regards,
> Adolf.
> 
> 
> On 15/08/2022 18:00, IPFire Project wrote:
>> IPFire Logo
>> there is a new post from Peter Müller on the IPFire Blog:
>> *IPFire 2.27 - Core Update 170 is available for testing*
>>   The next Core Update is available for testing. It features new IP blocklists for the firewall engine, significant improvements to Pakfire, modernizes the default cryptographic algorithm selection for IPsec connections, as well as a new kernel, and a plethora of bug fixes and security improvements under the hood.
>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-170-is-available-for-testing>
>> The IPFire Project
>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.

Re: IPFire 2.27 - Core Update 170 is available for testing

[Adolf Belka]

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

Hi Michael,

On 19/08/2022 10:47, Michael Tremer wrote:
> Hi Adolf,
> 
> Can we have bugzilla tickets raised for these issues, please?
Yes, of course, sorry for not doing it straight away.

I will get them written.

Regards
Adolf
> 
>> On 16 Aug 2022, at 14:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>
>>
>> Hi All,
>>
>> I just tried out CU170 and tested out the fuse fix for borgbackup.
>>
>> It failed.
>>
>> When I tried to do the mount I got the message:-
>>
>>       fuse: device not found, try 'modprobe fuse' first
>>
>> I then tried running modprobe fuse and got the following message
>>
>>       modprobe: FATAL: Module fuse not found in directory /lib/modules/5.15.49-ipfire
>>
>> I checked and found the modules in directory /lib/modules/5.15.59-ipfire/kernel/fs/fuse/ just the same as in my running CU169.
>>
>> In CU169 running modprobe fuse causes the module to be loaded successfully.
>>
>>
>> I am not sure what is different with CU170 and fuse.
>>
>> Let me know if there is something I need to check out on my vm system.
>>
>>
>>
>> Regarding the IP Address Blocklists new function. This has already been mentioned on the forum
>> https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/8400
>>
>> I confirm the same effect as mentioned in the forum. Trying to enable any list and pressing save gives a clear white page. Reload does not do anything. Rerunning the IPFire web app gives a system with everything still disabled.
>>
>> Looked in httpd/error_log but no errors from trying to run the ipblocklists page but the following error entries look to have been from the upgrade by pakfire.
>>
>> Can't locate IO/Socket/INET.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/IO/Socket/INET.pm: Permission denied at /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/IO/Socket.pm line 21.
>> Compilation failed in require at /var/ipfire/general-functions.pl line 19.
>> BEGIN failed--compilation aborted at /var/ipfire/general-functions.pl line 19.
>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 30.
>> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 123588682180160] [client 192.168.200.10:54370] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
>> sh: error while loading shared libraries: libreadline.so.8: cannot open shared object file: Permission denied
>> Can't locate overload.pm:   /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/overload.pm: Permission denied at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>> BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
>> BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
>> [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 123588782827072] [client 192.168.200.10:45148] End of script output before headers: pakfire.cgi, referer: https://ipfire.saturn.pimb.org:444/
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/settings at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
>> Unable to write file /var/ipfire/ipblocklist/modified at /var/ipfire/general-functions.pl line 256.
> 
> Stefan is going to be unavailable for the next couple of weeks. So I will have a go at this :)
> 
> -Michael
> 
>>
>>
>> Regards,
>> Adolf.
>>
>>
>> On 15/08/2022 18:00, IPFire Project wrote:
>>> IPFire Logo
>>> there is a new post from Peter Müller on the IPFire Blog:
>>> *IPFire 2.27 - Core Update 170 is available for testing*
>>>    The next Core Update is available for testing. It features new IP blocklists for the firewall engine, significant improvements to Pakfire, modernizes the default cryptographic algorithm selection for IPsec connections, as well as a new kernel, and a plethora of bug fixes and security improvements under the hood.
>>> Click Here To Read More <https://blog.ipfire.org/post/ipfire-2-27-core-update-170-is-available-for-testing>
>>> The IPFire Project
>>> Don't like these emails? Unsubscribe <https://people.ipfire.org/unsubscribe>.
> 

-- 
Sent from my laptop

Re: IPFire 2.27 - Core Update 170 is available for testing

[Adolf Belka]

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

Hi Michael,

On 19/08/2022 11:33, Adolf Belka wrote:
> Hi Michael,
>
> On 19/08/2022 10:47, Michael Tremer wrote:
>> Hi Adolf,
>>
>> Can we have bugzilla tickets raised for these issues, please?
> Yes, of course, sorry for not doing it straight away.
>
> I will get them written.
>
> Regards
> Adolf
>>
>>> On 16 Aug 2022, at 14:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>
>>>
>>> Hi All,
>>>
>>> I just tried out CU170 and tested out the fuse fix for borgbackup.
>>>
>>> It failed.
>>>
>>> When I tried to do the mount I got the message:-
>>>
>>>       fuse: device not found, try 'modprobe fuse' first
>>>
>>> I then tried running modprobe fuse and got the following message
>>>
>>>       modprobe: FATAL: Module fuse not found in directory 
>>> /lib/modules/5.15.49-ipfire
>>>
Should this bug be raised in the original #12611 borgbackup with pyfuse3 
or should it be a new bug. It is not clear to me if they are related or 
if they are separate issues, although when I tested the pyfuse3 install 
on CU169 it worked without this message, so maybe it needs to be a 
separate one.

Regards,

Adolf
>>> I checked and found the modules in directory 
>>> /lib/modules/5.15.59-ipfire/kernel/fs/fuse/ just the same as in my 
>>> running CU169.
>>>
>>> In CU169 running modprobe fuse causes the module to be loaded 
>>> successfully.
>>>
>>>
>>> I am not sure what is different with CU170 and fuse.
>>>
>>> Let me know if there is something I need to check out on my vm system.
>>>
>>>
>>>
>>> Regarding the IP Address Blocklists new function. This has already 
>>> been mentioned on the forum
>>> https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/8400 
>>>
>>>
>>> I confirm the same effect as mentioned in the forum. Trying to 
>>> enable any list and pressing save gives a clear white page. Reload 
>>> does not do anything. Rerunning the IPFire web app gives a system 
>>> with everything still disabled.
>>>
>>> Looked in httpd/error_log but no errors from trying to run the 
>>> ipblocklists page but the following error entries look to have been 
>>> from the upgrade by pakfire.
>>>
>>> Can't locate IO/Socket/INET.pm: 
>>> /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/IO/Socket/INET.pm: 
>>> Permission denied at 
>>> /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/IO/Socket.pm line 21.
>>> Compilation failed in require at /var/ipfire/general-functions.pl 
>>> line 19.
>>> BEGIN failed--compilation aborted at 
>>> /var/ipfire/general-functions.pl line 19.
>>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi 
>>> line 30.
>>> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 
>>> 123588682180160] [client 192.168.200.10:54370] End of script output 
>>> before headers: pakfire.cgi, referer: 
>>> https://ipfire.saturn.pimb.org:444/
>>> sh: error while loading shared libraries: libreadline.so.8: cannot 
>>> open shared object file: Permission denied
>>> Can't locate overload.pm: 
>>> /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/overload.pm: 
>>> Permission denied at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>>> BEGIN failed--compilation aborted at 
>>> /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>>> Compilation failed in require at /srv/web/ipfire/cgi-bin/pakfire.cgi 
>>> line 24.
>>> BEGIN failed--compilation aborted at 
>>> /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
>>> [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 
>>> 123588782827072] [client 192.168.200.10:45148] End of script output 
>>> before headers: pakfire.cgi, referer: 
>>> https://ipfire.saturn.pimb.org:444/
>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>> /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/settings at 
>>> /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>> /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>> /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>> /var/ipfire/general-functions.pl line 256.
>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>> /var/ipfire/general-functions.pl line 256.
>>
>> Stefan is going to be unavailable for the next couple of weeks. So I 
>> will have a go at this :)
>>
>> -Michael
>>
>>>
>>>
>>> Regards,
>>> Adolf.
>>>
>>>
>>> On 15/08/2022 18:00, IPFire Project wrote:
>>>> IPFire Logo
>>>> there is a new post from Peter Müller on the IPFire Blog:
>>>> *IPFire 2.27 - Core Update 170 is available for testing*
>>>>    The next Core Update is available for testing. It features new 
>>>> IP blocklists for the firewall engine, significant improvements to 
>>>> Pakfire, modernizes the default cryptographic algorithm selection 
>>>> for IPsec connections, as well as a new kernel, and a plethora of 
>>>> bug fixes and security improvements under the hood.
>>>> Click Here To Read More 
>>>> <https://blog.ipfire.org/post/ipfire-2-27-core-update-170-is-available-for-testing>
>>>> The IPFire Project
>>>> Don't like these emails? Unsubscribe 
>>>> <https://people.ipfire.org/unsubscribe>.
>>
>

-- 
Sent from my laptop

Re: IPFire 2.27 - Core Update 170 is available for testing

[Adolf Belka]

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

Hi,

Having thought about it I realise that it should be a separate bug. 
Although it is impacting bug #12611, it is not occurring directly 
because of that bug but die to some other issue.

Will raise a new bug for this.

Regards,

Adolf.

On 19/08/2022 11:54, Adolf Belka wrote:
> Hi Michael,
>
> On 19/08/2022 11:33, Adolf Belka wrote:
>> Hi Michael,
>>
>> On 19/08/2022 10:47, Michael Tremer wrote:
>>> Hi Adolf,
>>>
>>> Can we have bugzilla tickets raised for these issues, please?
>> Yes, of course, sorry for not doing it straight away.
>>
>> I will get them written.
>>
>> Regards
>> Adolf
>>>
>>>> On 16 Aug 2022, at 14:58, Adolf Belka <adolf.belka(a)ipfire.org> wrote:
>>>>
>>>>
>>>> Hi All,
>>>>
>>>> I just tried out CU170 and tested out the fuse fix for borgbackup.
>>>>
>>>> It failed.
>>>>
>>>> When I tried to do the mount I got the message:-
>>>>
>>>>       fuse: device not found, try 'modprobe fuse' first
>>>>
>>>> I then tried running modprobe fuse and got the following message
>>>>
>>>>       modprobe: FATAL: Module fuse not found in directory 
>>>> /lib/modules/5.15.49-ipfire
>>>>
> Should this bug be raised in the original #12611 borgbackup with 
> pyfuse3 or should it be a new bug. It is not clear to me if they are 
> related or if they are separate issues, although when I tested the 
> pyfuse3 install on CU169 it worked without this message, so maybe it 
> needs to be a separate one.
>
> Regards,
>
> Adolf
>>>> I checked and found the modules in directory 
>>>> /lib/modules/5.15.59-ipfire/kernel/fs/fuse/ just the same as in my 
>>>> running CU169.
>>>>
>>>> In CU169 running modprobe fuse causes the module to be loaded 
>>>> successfully.
>>>>
>>>>
>>>> I am not sure what is different with CU170 and fuse.
>>>>
>>>> Let me know if there is something I need to check out on my vm system.
>>>>
>>>>
>>>>
>>>> Regarding the IP Address Blocklists new function. This has already 
>>>> been mentioned on the forum
>>>> https://community.ipfire.org/t/core-170-test-ip-address-blocklists-error/8400 
>>>>
>>>>
>>>> I confirm the same effect as mentioned in the forum. Trying to 
>>>> enable any list and pressing save gives a clear white page. Reload 
>>>> does not do anything. Rerunning the IPFire web app gives a system 
>>>> with everything still disabled.
>>>>
>>>> Looked in httpd/error_log but no errors from trying to run the 
>>>> ipblocklists page but the following error entries look to have been 
>>>> from the upgrade by pakfire.
>>>>
>>>> Can't locate IO/Socket/INET.pm: 
>>>> /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/IO/Socket/INET.pm: 
>>>> Permission denied at 
>>>> /usr/lib/perl5/5.32.1/x86_64-linux-thread-multi/IO/Socket.pm line 21.
>>>> Compilation failed in require at /var/ipfire/general-functions.pl 
>>>> line 19.
>>>> BEGIN failed--compilation aborted at 
>>>> /var/ipfire/general-functions.pl line 19.
>>>> Compilation failed in require at 
>>>> /srv/web/ipfire/cgi-bin/pakfire.cgi line 30.
>>>> [Tue Aug 16 15:24:57.647655 2022] [cgid:error] [pid 17207:tid 
>>>> 123588682180160] [client 192.168.200.10:54370] End of script output 
>>>> before headers: pakfire.cgi, referer: 
>>>> https://ipfire.saturn.pimb.org:444/
>>>> sh: error while loading shared libraries: libreadline.so.8: cannot 
>>>> open shared object file: Permission denied
>>>> Can't locate overload.pm: 
>>>> /usr/lib/perl5/site_perl/5.32.1/x86_64-linux-thread-multi/overload.pm: 
>>>> Permission denied at /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>>>> BEGIN failed--compilation aborted at 
>>>> /usr/lib/perl5/site_perl/5.32.1/URI.pm line 28.
>>>> Compilation failed in require at 
>>>> /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
>>>> BEGIN failed--compilation aborted at 
>>>> /srv/web/ipfire/cgi-bin/pakfire.cgi line 24.
>>>> [Tue Aug 16 15:25:00.765653 2022] [cgid:error] [pid 17207:tid 
>>>> 123588782827072] [client 192.168.200.10:45148] End of script output 
>>>> before headers: pakfire.cgi, referer: 
>>>> https://ipfire.saturn.pimb.org:444/
>>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>>> /var/ipfire/general-functions.pl line 256.
>>>> Unable to write file /var/ipfire/ipblocklist/settings at 
>>>> /var/ipfire/general-functions.pl line 256.
>>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>>> /var/ipfire/general-functions.pl line 256.
>>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>>> /var/ipfire/general-functions.pl line 256.
>>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>>> /var/ipfire/general-functions.pl line 256.
>>>> Unable to write file /var/ipfire/ipblocklist/modified at 
>>>> /var/ipfire/general-functions.pl line 256.
>>>
>>> Stefan is going to be unavailable for the next couple of weeks. So I 
>>> will have a go at this :)
>>>
>>> -Michael
>>>
>>>>
>>>>
>>>> Regards,
>>>> Adolf.
>>>>
>>>>
>>>> On 15/08/2022 18:00, IPFire Project wrote:
>>>>> IPFire Logo
>>>>> there is a new post from Peter Müller on the IPFire Blog:
>>>>> *IPFire 2.27 - Core Update 170 is available for testing*
>>>>>    The next Core Update is available for testing. It features new 
>>>>> IP blocklists for the firewall engine, significant improvements to 
>>>>> Pakfire, modernizes the default cryptographic algorithm selection 
>>>>> for IPsec connections, as well as a new kernel, and a plethora of 
>>>>> bug fixes and security improvements under the hood.
>>>>> Click Here To Read More 
>>>>> <https://blog.ipfire.org/post/ipfire-2-27-core-update-170-is-available-for-testing>
>>>>> The IPFire Project
>>>>> Don't like these emails? Unsubscribe 
>>>>> <https://people.ipfire.org/unsubscribe>.
>>>
>>
>

-- 
Sent from my laptop

Re: IPFire 2.27 - Core Update 170 is available for testing

[Peter Müller]

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

Hello *,

thank you all for the testing of Core Update 170, and the robust reporting!

>From what I gathered, there are currently three bugs unresolved in this update:

- #12916 (messagebus: multiple "/etc/rc.d/init.d/functions: line 332: shift: 2: shift count out of range")
	=> Affects people having installed the "dbus" add-on

- #12917 (When enabling ipblocklist WUI page a blank screen is shown)
	=> Hopefully fixed by https://patchwork.ipfire.org/project/ipfire/patch/06825b38-ec53-38c5-c8ce-12d70c1acb5b(a)ipfire.org/.

- #12918 (When running a fuse mount for borgbackup get error message "fuse: device not found, try 'modprobe fuse' first")
	=> Might be a local testing issue, not a general problem with the Core Update

For an update of this size and changes, that strikes me as a rather short list
of bugs, so it may either be that we are all really overlooking something, or it
is just a pretty solid Core Update. :-)

Due to my current workload situation, I would like to give C170 another ~ two weeks,
and would aim for a release around September 2nd or 3rd. Given the currently
unresolved bugs, I think the time is sufficient to have any missing patches developed
until then.

As always, comments/questions/complaints are appreciated.

Best,
Peter Müller

Re: IPFire 2.27 - Core Update 170 is available for testing

[Michael Tremer]

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

Hello,

I just wanted to reach out and hear if there is any more feedback on this update.

Lots of people have been away, and so it was *very* quiet in the last few weeks.

I don’t feel confident at all about this update, yet. Anyone who can take concern away from me?

-Michael

> On 22 Aug 2022, at 21:36, Peter Müller <peter.mueller(a)ipfire.org> wrote:
> 
> Hello *,
> 
> thank you all for the testing of Core Update 170, and the robust reporting!
> 
> From what I gathered, there are currently three bugs unresolved in this update:
> 
> - #12916 (messagebus: multiple "/etc/rc.d/init.d/functions: line 332: shift: 2: shift count out of range")
> 	=> Affects people having installed the "dbus" add-on
> 
> - #12917 (When enabling ipblocklist WUI page a blank screen is shown)
> 	=> Hopefully fixed by https://patchwork.ipfire.org/project/ipfire/patch/06825b38-ec53-38c5-c8ce-12d70c1acb5b(a)ipfire.org/.
> 
> - #12918 (When running a fuse mount for borgbackup get error message "fuse: device not found, try 'modprobe fuse' first")
> 	=> Might be a local testing issue, not a general problem with the Core Update
> 
> For an update of this size and changes, that strikes me as a rather short list
> of bugs, so it may either be that we are all really overlooking something, or it
> is just a pretty solid Core Update. :-)
> 
> Due to my current workload situation, I would like to give C170 another ~ two weeks,
> and would aim for a release around September 2nd or 3rd. Given the currently
> unresolved bugs, I think the time is sufficient to have any missing patches developed
> until then.
> 
> As always, comments/questions/complaints are appreciated.
> 
> Best,
> Peter Müller
> 

Re: IPFire 2.27 - Core Update 170 is available for testing

[Peter Müller]

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

Hello Michael,

> Hello,
> 
> I just wanted to reach out and hear if there is any more feedback on this update.

nothing from my end. The update runs fine on my physical testing machine since two weeks.

> Lots of people have been away, and so it was *very* quiet in the last few weeks.

Yes, I kind of have a bad conscience for being away again next week, but it can't be helped.

> I don’t feel confident at all about this update, yet. Anyone who can take concern away from me?

See below.

> 
> -Michael
> 
>> On 22 Aug 2022, at 21:36, Peter Müller <peter.mueller(a)ipfire.org> wrote:
>>
>> Hello *,
>>
>> thank you all for the testing of Core Update 170, and the robust reporting!
>>
>> From what I gathered, there are currently three bugs unresolved in this update:
>>
>> - #12916 (messagebus: multiple "/etc/rc.d/init.d/functions: line 332: shift: 2: shift count out of range")
>> 	=> Affects people having installed the "dbus" add-on

Patch merged into "next".

>>
>> - #12917 (When enabling ipblocklist WUI page a blank screen is shown)
>> 	=> Hopefully fixed by https://patchwork.ipfire.org/project/ipfire/patch/06825b38-ec53-38c5-c8ce-12d70c1acb5b(a)ipfire.org/.

Submitted a version 3 that is hopefully finally fine.

>>
>> - #12918 (When running a fuse mount for borgbackup get error message "fuse: device not found, try 'modprobe fuse' first")
>> 	=> Might be a local testing issue, not a general problem with the Core Update

Turned out to be a local issue indeed.

Two additional bugs crept up recently (indicating to me that there _is_ some testing audience):

- #12919 (IPSec/alias-IP failure)
	=> Not sure if this should be considered a show-stopper, waiting for user feedback

- #12924 (Cannot access https web pages in CUPS)
	=> Currently unassigned, root cause under investigation

Since no really severe bugs or user complaints arose, I would consider C170 to be free of major
surprises/disappointments. #12917 obviously needs to be fixed before a release, and #12919 should
be, AFAIK. I would not consider #12924 to be a show-stopper.

Hopes this clarifies the situation a bit. :-)

Thanks, and best regards,
Peter Müller

>>
>> For an update of this size and changes, that strikes me as a rather short list
>> of bugs, so it may either be that we are all really overlooking something, or it
>> is just a pretty solid Core Update. :-)
>>
>> Due to my current workload situation, I would like to give C170 another ~ two weeks,
>> and would aim for a release around September 2nd or 3rd. Given the currently
>> unresolved bugs, I think the time is sufficient to have any missing patches developed
>> until then.
>>
>> As always, comments/questions/complaints are appreciated.
>>
>> Best,
>> Peter Müller
>>
>