Hallo @svrovpn
Welcome to the IPFire community.
Your links are totally wrong for the IPFire infrastructure locations and the mirrors. That is why you are not getting any response.
The IPFire url’s might well have changed in the last 5 years since CU150 was released. However the mirror structure has not changed.
One thing to note is that the major version changed from 2.25 to 2.27 in CU159 and then from 2.27 to 2.29 in CU183.
Here is a link for the Netherlands mirror for the directory for the major version 2.29 which contains the core-upgrade-151.ipfire file and all of those files back to CU140.
https://ftp.nluug.nl/os/Linux/distr/ipfire/pakfire2/2.29.2-x86_64/paks/
You will find similar files in all the mirrors.
I am not sure why your are looking to download these files as pakfire will not work with files you have downloaded. It will try and download them itself.
If you are having trouble with this that may be due to the 48 Core Updates in between your existing installation and the current released version.
Pakfire will try its best to do the update from CU150 to CU198 but an awful lot has changed in those intervening 5 years. The update, if successful will take quite a while and if it fails part way through you will have no alternative but to do a fresh install.
Therefore before doing the upgrade make sure you have all the information needed to do a fresh install beforehand, such as the IP’s used for the different IPFire interfaces, the MAC addresses of your IPFire NIC’s etc.
If pakfire is failing to start the update then it would be useful to be able to see the log messages provided by pakfire.
Good luck in your update. Once you have successfully achieved it then I would recommend doing your updates much more regularly.
Your production system is currently running without any of the fixes that have been implemented for all the vulnerabilities that have been identified over the last 5 years in packages such as apache, openssl, openvpn, etc …
EDIT:
I have installed CU150 onto a vm system. I got the following message:-
The update at this stage will be limited to CU159 as the major version is 2.25 and pakfire does its update one major version at a time.
Here is the system after doing the update and doing a reboot. It is now at CU159 but major version 2.27.
pakfire now shows the following.
So it is now working on the update from CU159 to CU183 which covers major version 2.27
So far pakfire is doing the update correctly, just taking a bit of time.
Occasionally I am finding that error messages come up on the browser in place of the WUI but each time I am finding that if I re-access the WUI I can get there. It looks like there might be some mismatches between the very old apache server in the old version and what the browser is willing to accept.
At CU169 the browser had a period where it could not access the WUI but checking via the console the updates was still occurring. After some time the browser could access the WUI again. It is now up to CU175.
Update to CU183 has been completed which now makes it on major version 2.29.
Rebooted and then checked pakfire and it now shows CU183 to CU198 being available.
System is now working through those core updates.
Update has got to CU198 and has been rebooted and IPFire is working the same as it did beforehand.
From start to finish it took 60 minutes and 3 reboots but it was able to successfully do it without any manual downloading of files.
Pakfire was able to work with it, just needing to split each set of updates into those for a major version.
