And finally, here it is:
Congratulations on the release of the new version; thank you to all team members who contributed. However, I have a question. When will the stable version for the Raspberry Pi 5 be announced? I imagine there are many Raspberry Pi 5 owners eagerly awaiting this. Best regards.
I don’t think that we are close to a functioning RPi 5 version because so many drivers are still missing in the Linux kernel. With the low availability of the board and high cost I am not sure there are many people who will be running IPFire on it. Nobody on our team has one as far as I know.
Michael, I have a test 201 installed (IPFire 2.29 (aarch64) - Core-Update 201 Development Build: master/da6ccd7a) , how do I refresh it to the current 201 ?
Reset the repository to Stable from Testing and save. Then edit the file
/opt/pakfire/db/core/mine
to change it from 201 to 200.
Then go back to the WUI and if needed do a refresh of the lists and you should then have it say that the CU201 update is available.
Since the update (which went smooth as normal) we discovered outgoing connections to 81.3.27.55 on port 53. We don’t use this server as a recursor and it’s not listed in the documentation (List of Public DNS Servers). Is this a misbehaviour of the update or is it safe to create a firewall exception for this server?
Hello @hardcoretec,
that is the server that is hosting IPFire DBL. If you have enabled the DNS Firewall, you will have to give it access to actually download the blocklists.
Thanks for the super fast reply. Indeed we activated the DNS Firewall on the test server.
Everything is working fine, including the Wireless Access Point.
IPFire 2.29 (aarch64) - Core-Update 201
Thank you very much for your support.