Posts by vpeter

Works perfectly fine here. Maybe it is something special to your setup?

Quote from conny

IPTV Simple Client works for me on pi 3b+ with 9.0.0... strange...

Why would be strange to be working?

Test image: libreelec-rpi2.arm-9.0-set-tos-ntp.img.gz

After it boots set tos with command below and reboot. Then time should be set with NTP.

cat > /storage/.config/system.d/ntp-set-tos.service <<EOF
[Unit]
Description=Iptables set TOS for NTP
Before=network.target
Wants=network.target

[Service]
Type=oneshot
ExecStart=/usr/sbin/iptables -w -t mangle -I POSTROUTING 1 -p udp --dport 123 -j TOS --set-tos 0x00
ExecReload=/usr/sbin/iptables -w -t mangle -I POSTROUTING 1 -p udp --dport 123 -j TOS --set-tos 0x00
RemainAfterExit=yes

[Install]
WantedBy=multi-user.target
EOF

systemctl enable ntp-set-tos

Would be probably easier to patch connman to use TOS 0x00. Or run patched ntpd from http://autostart.sh/custom service. Or use curl approach.

Update: Seems there were at least one user with same problem Raspberry Pi 3 built-in WiFi SSH NTP Problem

I think message is clear: upgrade your wget. Or use suggested build host (Ubuntu 16.04.x (LTS)).

Ok, can you try

wget -O ntpd_tos_00 http://vpeter.libreelec.tv/tmp/ntpd_tos_00
chmod +x ntpd_tos_00
./ntpd_tos_00 -d -d -d -n -p pool.ntp.org

Tomorrow I will try to make test image for you.

Setting different TOS could help according to [Solved] Time does not sync on Pi 3 and with official dongle - Raspberry Pi Forums

Quote

That points to some firmware/driver defect in RPI3 (it seems unable to forward IP packets with ToS != 0).

But kernel module is disabled and you can't test that.

I think LE guys should ask RPi guys if this is still and issue. Or someone should make you appropriate image to test. Or just use USB wifi stick

chewitt : ^^^^

Well, I newer saw this issue in real life. So someone else would need to step in to help you.

Camera is also wifi?

As already figure out: you don't get NTP response packets No idea what is causing this. I assume it must be something on your modem/router in case wifi is used.

Try setting date/time with the help of timeapi.herokuapp.com as I suggested. Until you figure out the reason for your problem.

It is network tools.

In one terminal run

tcpdump -vvnAs0 -i any port 123

and in another

ntpd -d -d -d -n -p pool.ntp.org

Copy result from tcpdump to Pastebin.com

Post url for command

iptables -L -n | pastebinit

I think you should install system tools addon and capture network traffic to see what is going on.

Quote from Mario77

Did something changed regarding CEC in LE9?

With 2 years of development? I would say yes

Quote from Cryologic

Why Coreelec, Alexelec have Python 3? Only you cannot use Python 3? why?

They have Python2 as default Python and extra Python3.

Something like include addon in image

As you can see you don't get any response back from NTP server (which listen on port UDP 123). Routing table seems fine. Are you using some firewall? Does any other network action works like curl?

curl http://libreelec.tv

As a temporary workaround you could set time like this (from autostart.sh maybe periodically):

date -s @$(curl -s 'http://timeapi.herokuapp.com/utc/now?\s')

Ok, it was just a try.

What about

ntpd -d -d -d -n -p pool.ntp.org

Also can you run this and post url?

route -n | pastebinit

Seems your network is just not ready yet.

What about adding this 2 lines at start of file Autostart.sh [LibreELEC.wiki]

sleep 5
systemctl restart connman.service

If it doesn't work try use longer sleep (in seconds).

Post log.

Check ffmpeg-tools addon.