Hi all, i wanted to report a problem with SSH after updating to core 151 testing.
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 ?
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",
but apart from that no further problems so far.
Best,
Erik
Hello,
Could you please open a ticket on BZ for both of them?
Best, -Michael
On 9 Oct 2020, at 12:46, ummeegge ummeegge@ipfire.org wrote:
Hi all, i wanted to report a problem with SSH after updating to core 151 testing.
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 ?
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",
but apart from that no further problems so far.
Best,
Erik
Hi all,
Am Freitag, den 09.10.2020, 15:26 +0100 schrieb Michael Tremer:
Hello,
Could you please open a ticket on BZ for both of them?
Done --> https://bugzilla.ipfire.org/show_bug.cgi?id=12495 https://bugzilla.ipfire.org/show_bug.cgi?id=12494
apart from that my Prime has been smoked up with a read-only file system and is gone into the "Ewige Jagd Gründe" after a reboot but this might have other reasons but further testings/developments are currently a little awkward.
Best from shit happens,
Erik
Best, -Michael
On 9 Oct 2020, at 12:46, ummeegge ummeegge@ipfire.org wrote:
Hi all, i wanted to report a problem with SSH after updating to core 151 testing.
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 ?
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",
but apart from that no further problems so far.
Best,
Erik
Hi,
On 9 Oct 2020, at 21:56, ummeegge ummeegge@ipfire.org wrote:
Hi all,
Am Freitag, den 09.10.2020, 15:26 +0100 schrieb Michael Tremer:
Hello,
Could you please open a ticket on BZ for both of them?
Done --> https://bugzilla.ipfire.org/show_bug.cgi?id=12495 https://bugzilla.ipfire.org/show_bug.cgi?id=12494
Done and dealt with.
apart from that my Prime has been smoked up with a read-only file system and is gone into the "Ewige Jagd Gründe" after a reboot but this might have other reasons but further testings/developments are currently a little awkward.
Software failure?
-Michael
Best from shit happens,
Erik
Best, -Michael
On 9 Oct 2020, at 12:46, ummeegge ummeegge@ipfire.org wrote:
Hi all, i wanted to report a problem with SSH after updating to core 151 testing.
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 ?
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",
but apart from that no further problems so far.
Best,
Erik
Good morning,
Am Samstag, den 10.10.2020, 12:52 +0100 schrieb Michael Tremer:
Hi,
On 9 Oct 2020, at 21:56, ummeegge ummeegge@ipfire.org wrote:
Hi all,
Am Freitag, den 09.10.2020, 15:26 +0100 schrieb Michael Tremer:
Hello,
Could you please open a ticket on BZ for both of them?
Done --> https://bugzilla.ipfire.org/show_bug.cgi?id=12495 https://bugzilla.ipfire.org/show_bug.cgi?id=12494
Done and dealt with.
Great.
apart from that my Prime has been smoked up with a read-only file system and is gone into the "Ewige Jagd Gründe" after a reboot but this might have other reasons but further testings/developments are currently a little awkward.
Software failure?
No the SSD died.
-Michael
Best from shit happens,
Erik
Best, -Michael
On 9 Oct 2020, at 12:46, ummeegge ummeegge@ipfire.org wrote:
Hi all, i wanted to report a problem with SSH after updating to core 151 testing.
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 ?
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",
but apart from that no further problems so far.
Best,
Erik
Hi all, did a fresh install of Core 150 and updated it to Core 151 testing. By calling the OpenVPN WUI i get an internal server error with the following error_log entry:
Can't locate Net/DNS/RR/NXT.pm in @INC (you may need to install the Net::DNS::RR::NXT module) (@INC contains: /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.30.0 /usr/lib/perl5/5.30.0/x86_64-linux-thread-multi /usr/lib/perl5/5.30.0) at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/RR.pm line 86. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/RR.pm line 131. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Packet.pm line 15. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Packet.pm line 15. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver/Base.pm line 20. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver/Base.pm line 20. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver/UNIX.pm line 9. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver/UNIX.pm line 9. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver.pm line 19. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver.pm line 22. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS.pm line 37. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS.pm line 37. Compilation failed in require at /srv/web/ipfire/cgi-bin/ovpnmain.cgi line 26. BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/ovpnmain.cgi line 26. [Sun Oct 11 09:48:22.546603 2020] [cgid:error] [pid 8658:tid 127223231145536] [client 192.168.75.2:58726] End of script output before headers: ovpnmain.cgi
So it seems that some perl moduls are missing. Does someone have similar problems ?
Best,
Erik
Am Sonntag, den 11.10.2020, 07:27 +0200 schrieb ummeegge:
Good morning,
Am Samstag, den 10.10.2020, 12:52 +0100 schrieb Michael Tremer:
Hi,
On 9 Oct 2020, at 21:56, ummeegge ummeegge@ipfire.org wrote:
Hi all,
Am Freitag, den 09.10.2020, 15:26 +0100 schrieb Michael Tremer:
Hello,
Could you please open a ticket on BZ for both of them?
Done --> https://bugzilla.ipfire.org/show_bug.cgi?id=12495 https://bugzilla.ipfire.org/show_bug.cgi?id=12494
Done and dealt with.
Great.
apart from that my Prime has been smoked up with a read-only file system and is gone into the "Ewige Jagd Gründe" after a reboot but this might have other reasons but further testings/developments are currently a little awkward.
Software failure?
No the SSD died.
-Michael
Best from shit happens,
Erik
Best, -Michael
On 9 Oct 2020, at 12:46, ummeegge ummeegge@ipfire.org wrote:
Hi all, i wanted to report a problem with SSH after updating to core 151 testing.
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 ?
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",
but apart from that no further problems so far.
Best,
Erik
Hi,
=> https://bugzilla.ipfire.org/show_bug.cgi?id=12491
Confirmed.
The mean part was https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=5f1039dda984ed3a06da95ba...
MT and Fred found a solution (Thanks!).
The only thing: I'm not quite sure how to integrate a fix deleting the old directory and file(s) under consideration of the respective client architecture.
Best, Matthias
On 11.10.2020 09:52, ummeegge wrote:
Hi all, did a fresh install of Core 150 and updated it to Core 151 testing. By calling the OpenVPN WUI i get an internal server error with the following error_log entry:
Can't locate Net/DNS/RR/NXT.pm in @INC (you may need to install the Net::DNS::RR::NXT module) (@INC contains: /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.30.0 /usr/lib/perl5/5.30.0/x86_64-linux-thread-multi /usr/lib/perl5/5.30.0) at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/RR.pm line 86. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/RR.pm line 131. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Packet.pm line 15. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Packet.pm line 15. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver/Base.pm line 20. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver/Base.pm line 20. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver/UNIX.pm line 9. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver/UNIX.pm line 9. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver.pm line 19. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS/Resolver.pm line 22. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS.pm line 37. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi/Net/DNS.pm line 37. Compilation failed in require at /srv/web/ipfire/cgi-bin/ovpnmain.cgi line 26. BEGIN failed--compilation aborted at /srv/web/ipfire/cgi-bin/ovpnmain.cgi line 26. [Sun Oct 11 09:48:22.546603 2020] [cgid:error] [pid 8658:tid 127223231145536] [client 192.168.75.2:58726] End of script output before headers: ovpnmain.cgi
So it seems that some perl moduls are missing. Does someone have similar problems ?
Best,
Erik
Am Sonntag, den 11.10.2020, 07:27 +0200 schrieb ummeegge:
Good morning,
Am Samstag, den 10.10.2020, 12:52 +0100 schrieb Michael Tremer:
Hi,
On 9 Oct 2020, at 21:56, ummeegge ummeegge@ipfire.org wrote:
Hi all,
Am Freitag, den 09.10.2020, 15:26 +0100 schrieb Michael Tremer:
Hello,
Could you please open a ticket on BZ for both of them?
Done --> https://bugzilla.ipfire.org/show_bug.cgi?id=12495 https://bugzilla.ipfire.org/show_bug.cgi?id=12494
Done and dealt with.
Great.
apart from that my Prime has been smoked up with a read-only file system and is gone into the "Ewige Jagd Gründe" after a reboot but this might have other reasons but further testings/developments are currently a little awkward.
Software failure?
No the SSD died.
-Michael
Best from shit happens,
Erik
Best, -Michael
On 9 Oct 2020, at 12:46, ummeegge ummeegge@ipfire.org wrote:
Hi all, i wanted to report a problem with SSH after updating to core 151 testing.
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 ?
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",
but apart from that no further problems so far.
Best,
Erik
Hi Matthias,
Am Sonntag, den 11.10.2020, 10:00 +0200 schrieb Matthias Fischer:
Hi,
=> https://bugzilla.ipfire.org/show_bug.cgi?id=12491
Confirmed.
The mean part was
https://git.ipfire.org/?p=ipfire-2.x.git;a=commit;h=5f1039dda984ed3a06da95ba...
MT and Fred found a solution (Thanks!).
Great thanks to all, haven´t checked bugzilla ;-)
The only thing: I'm not quite sure how to integrate a fix deleting the old directory and file(s) under consideration of the respective client architecture.
May i am terribly unright but shouldn´t a wildcard solve this /usr/lib/perl5/site_perl/5.30.0/*/Net/DNS
Best, Matthias
Best,
Erik
On 11.10.2020 09:52, ummeegge wrote:
Hi all, did a fresh install of Core 150 and updated it to Core 151 testing. By calling the OpenVPN WUI i get an internal server error with the following error_log entry:
Can't locate Net/DNS/RR/NXT.pm in @INC (you may need to install the Net::DNS::RR::NXT module) (@INC contains: /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.30.0 /usr/lib/perl5/5.30.0/x86_64-linux- thread-multi /usr/lib/perl5/5.30.0) at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS/RR.pm line 86. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS/RR.pm line 131. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS/Packet.pm line 15. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS/Packet.pm line 15. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS/Resolver/Base.pm line 20. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS/Resolver/Base.pm line 20. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS/Resolver/UNIX.pm line 9. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS/Resolver/UNIX.pm line 9. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS/Resolver.pm line 19. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS/Resolver.pm line 22. Compilation failed in require at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS.pm line 37. BEGIN failed--compilation aborted at /usr/lib/perl5/site_perl/5.30.0/x86_64-linux-thread- multi/Net/DNS.pm line 37. Compilation failed in require at /srv/web/ipfire/cgi- bin/ovpnmain.cgi line 26. BEGIN failed--compilation aborted at /srv/web/ipfire/cgi- bin/ovpnmain.cgi line 26. [Sun Oct 11 09:48:22.546603 2020] [cgid:error] [pid 8658:tid 127223231145536] [client 192.168.75.2:58726] End of script output before headers: ovpnmain.cgi
So it seems that some perl moduls are missing. Does someone have similar problems ?
Best,
Erik
Am Sonntag, den 11.10.2020, 07:27 +0200 schrieb ummeegge:
Good morning,
Am Samstag, den 10.10.2020, 12:52 +0100 schrieb Michael Tremer:
Hi,
On 9 Oct 2020, at 21:56, ummeegge ummeegge@ipfire.org wrote:
Hi all,
Am Freitag, den 09.10.2020, 15:26 +0100 schrieb Michael Tremer:
Hello,
Could you please open a ticket on BZ for both of them?
Done --> https://bugzilla.ipfire.org/show_bug.cgi?id=12495 https://bugzilla.ipfire.org/show_bug.cgi?id=12494
Done and dealt with.
Great.
apart from that my Prime has been smoked up with a read-only file system and is gone into the "Ewige Jagd Gründe" after a reboot but this might have other reasons but further testings/developments are currently a little awkward.
Software failure?
No the SSD died.
-Michael
Best from shit happens,
Erik
Best, -Michael
> On 9 Oct 2020, at 12:46, ummeegge ummeegge@ipfire.org > wrote: > > Hi all, > i wanted to report a problem with SSH after updating to > core > 151 > testing. > > 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 ? > > 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", > > but apart from that no further problems so far. > > Best, > > Erik > > >
Hi,
[unneeded stuff deleted]
On 11.10.2020 13:57, ummeegge wrote:
...
The only thing: I'm not quite sure how to integrate a fix deleting the old directory and file(s) under consideration of the respective client architecture.
May i am terribly unright but shouldn´t a wildcard solve this /usr/lib/perl5/site_perl/5.30.0/*/Net/DNS
*Sigh* You're right. I'm in the need of holidays...
Wrote patch. Tested. Works. Please confirm.
=> https://bugzilla.ipfire.org/show_bug.cgi?id=12491#c9
I also added it here. Please find attached an updated 'update.sh' plus a proposed patch for Core 151 for .../config/rootfiles/core/151'.
I didn't want to push this to the 'master' branch and something like https://git.ipfire.org/?p=ipfire-2.x.git;a=shortlog;h=refs/heads/core151 doesn't exist yet.
Best, Matthias
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.
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
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
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
-
Adolf Belka -
Matthias Fischer -
Michael Tremer -
Peter Müller -
ummeegge