From: Adolf Belka <ahb.ipfire@gmail.com>
To: development@lists.ipfire.org
Subject: Re: Core 151 testing feedback
Date: Sun, 11 Oct 2020 13:18:31 +0200 [thread overview]
Message-ID: <48842a1f-420c-9b89-9adb-2d9851e35e80@gmail.com> (raw)
In-Reply-To: <352ae035-847c-f8e0-08cb-d5d473946885@ipfire.org>
[-- Attachment #1: Type: text/plain, Size: 1610 bytes --]
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
>
next prev parent reply other threads:[~2020-10-11 11:18 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-09 11:46 ummeegge
2020-10-09 14:26 ` Michael Tremer
2020-10-09 20:56 ` ummeegge
2020-10-10 11:52 ` Michael Tremer
2020-10-11 5:27 ` ummeegge
2020-10-11 7:52 ` ummeegge
2020-10-11 8:00 ` Matthias Fischer
2020-10-11 11:57 ` ummeegge
2020-10-11 16:29 ` Matthias Fischer
2020-10-09 19:31 ` Peter Müller
2020-10-11 11:18 ` Adolf Belka [this message]
2020-10-11 11:58 ` Adolf Belka
2020-10-11 11:29 Core 151 Testing feedback Adolf Belka
2020-10-12 10:14 ` Michael Tremer
2020-10-12 11:14 ` Adolf Belka
2020-10-12 13:10 ` Michael Tremer
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=48842a1f-420c-9b89-9adb-2d9851e35e80@gmail.com \
--to=ahb.ipfire@gmail.com \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox