Hi everyone,

I also found the mismatch in os-release but in my case it showed:-

PRETTY_NAME="IPFire 2.25 (x86_64) - core147"

fireinfo/profile showed:-

"release": "IPFire 2.25 (x86_64) - core151 Development Build: master/a9f69cbf"


Regards,

Adolf


On 11/10/2020 13:18, Adolf Belka wrote:
> Hi everyone,
>
>
> On 09/10/2020 21:31, Peter Müller wrote:
>> Hello *,
>>
>> upcoming Core Update 151 (testing) still contains some glitches.
>>
>>> SSH runs regular on port 222 after updating SSH runs on port 22 and
>>> wasn´t reachable via the old settings. After pressing the save button
>>> in SSH section in the WUI everything worked again.
>>>
>>> May someone else have that too ?
>>
>> Yes, I bumped into that as well.
> The ssh effect did not happen to me. I updated to core 151 and rebooted and after that was able to ssh in with port 222 as normal.
>>
>>> Also, /etc/os-release shows
>>>
>>> PRETTY_NAME="IPFire 2.25 (x86_64) - core145 Development Build: master/405c7326"
>>>
>>> but /var/ipfire/fireinfo/profile shows the correct version
>>>
>>> "release": "IPFire 2.25 (x86_64) - core151 Development Build: master/5e4126c3",
>>
>> This issue can be reproduced here.
>>
>>> but apart from that no further problems so far.
>>
>> The IPsec and OpenVPN CGIs are rendered unusable in Core Update 151 at the time
>> of writing, most probably due to a missing Perl dependency in Net::DNS. This
>> issue is tracked as #12491 and is currently a show-stopper from my point of view.
>>
>> Further, the Tor CGI did not call some location module functions properly, which
>> is tracked as #12492 and fixed by https://patchwork.ipfire.org/patch/3519/.
>>
>> Notices regarding IP addresses belonging to anonymous proxies, satellite providers
>> or anycast services are a bit messy and not translated into German, but this is
>> only a minor issue.
>>
>> Thanks, and best regards,
>> Peter Müller
>>