Posts by vpeter

Quote from balbes150

You again give inaccurate information (you have previously tried to intentionally spread fakes about N2, after that I am skeptical about your information). As far as I know, the representative of Beelinc offered CE sample KING, but CE representatives said they need a lot of samples for all developers. This requirement is very similar to the attempt to put obviously impossible requirement that would then hide behind this, why they were not able to release the CE image for King.

..............when used in normal mode (when the radiator is looking down), its efficiency is about 40%.

"intentionally spread fakes": Where and what exactly? I only pointed to your (wrong) speculations.

Company makes big profit from other people's work and they can't send few samples? Only one! If they are serious they should send few samples. And not "lot of samples"

Update: It is alive

How did you calculated or measure exactly 40%? So others can repeat the tests.

Quote from balbes150

Perhaps for this reason CE do not want to engage in Beelink King (s922).

If you can't read on CE forum what is the reason to not support this device (yet) with "old" kernel it is your fault. If you don't understand ask someone to translate the reason to your language.

Hint: Test LibreELEC images with KODI-18 for S9xxx

Quote from snixel

Does this mean that those applications don't have support for ipv6?

Probably. You can check that in source code. Or maybe ipv6 is disabled on start and only ipv4 is used.

No, it was not me who implemented fw in le.

You can open a ticket here if you want: Ticket System - LibreELEC Forum

Try adding this two rules (first one is for dhcp, second one is for icmp):

-A INPUT -p udp -m udp --dport 546 -m state --state NEW,ESTABLISHED -j ACCEPT
-A INPUT -p ipv6-icmp -j ACCEPT

Or find some working script on Internet to see if your commands are missing something else.

Looks ok here You can also change timestamp format in awk/strftime.

[2019-06-04 14:49:25] Server listening on 0.0.0.0 port 22.
[2019-06-04 14:49:25] Server listening on :: port 22.
[2019-06-04 14:49:26] Accepted password for root from 192.68.1.2 port 56393 ssh2
[2019-06-04 14:49:58] Failed password for root from 192.68.1.3 port 56405 ssh2
[2019-06-04 14:49:58] Connection closed by authenticating user root 192.68.1.3 port 56405 [preauth]
[2019-06-04 14:49:59] Failed password for root from 192.68.1.4 port 56407 ssh2
[2019-06-04 14:49:59] Connection closed by authenticating user root 192.68.1.4 port 56407 [preauth]

I keep few things in my head. But in this case I was using sshd(8) - OpenBSD manual pages and few suggestions from Google

Well, then one option is to fix sshd service file.

First remove added SSH_ARGS value from /storage/.cache/services/sshd.conf file.

Then copy sshd service file to storage and change ExecStart line.

cp /usr/lib/systemd/system/sshd.service /storage/.config/system.d/
vi /storage/.config/system.d/sshd.service

ExecStart=/bin/sh -c "/usr/sbin/sshd -D $SSH_ARGS -e 2>&1 | awk '{print strftime(\"[%%Y-%%m-%%d %%H:%%M:%%S] \") $0}' >>/var/log/sshd.log"

systemctl daemon-reload
systemctl restart sshd
systemctl status sshd -l --no-pager

Can you post both outputs of iptables -L and ip6tables -L to compare?

edit file /storage/.cache/services/sshd.conf and change/add -E log_file

SSH_ARGS="-E /var/log/sshd.log"

restart sshd service

systemctl restart sshd

check log file /var/log/sshd.log

cat /var/log/sshd.log

Check if you can add StandardOutput to file in sshd.service file.

I don't know if there is any such log file. BUt i see with command above

Jun 02 11:25:22 LibreELEC sshd[1340]: Failed password for root from 192.168.2.3 port 47442 ssh2
Jun 02 11:25:22 LibreELEC sshd[1340]: Connection closed by authenticating user root 192.168.2.3 port 47442 [preauth]

Maybe some cron job could create log file with grepping systemctl status.

Quote from Borygo77

Anyone can point me where accepted and failed logins to ssh are stored ?

Maybe

systemctl status sshd -l --no-pager

Would not be easier to restart Kodi at 3AM every night? It is not a fix but still

Try

robocopy "D:\Media\Fotoramen" "Z:\Fotoramen" /MIR /COPY:DT /DCOPY:T

Compare the content of both archives to see what is the difference

I updated build Milhouse #0528and removed kodi profile folder. After new start I could install whatever addon version was in the repository.

Are you sure you look enough?