Upgrade LE 8.2.5 to 9.0.0: Wifi connected but no NTP link => SSL Certificate error !

**chewitt** · February 19, 2019 at 6:14 PM Official Post

Ahh.. would be good to test then. Can you spin an image for the user?

**vpeter** · February 19, 2019 at 6:38 PM

Sure. libreelec-rpi2.arm-9.0-set-bcdc-0.img.gz

This image should work out of the box then.

Tos26 · February 19, 2019 at 6:51 PM

Hello,

I tested the new image you generated vpeter and unfortunately, there is the same issue

The verbose log file

We can see the ToS config taken into account here:

Code

Jun 22 13:11:52 LibreELEC systemd[1]: Starting Iptables set TOS for NTP...

And the result of tcpdump : http://ix.io/1bvv

ToS is set well to 0x0.

Some ideas ?

chewitt: I will see the links you gave.

Tos26 · February 19, 2019 at 6:53 PM

Yeah ! I didn't see your recent reply.

So I have to test the BCDC image ?

**chewitt** · February 19, 2019 at 6:55 PM Official Post

Yes pls.

**vpeter** · February 19, 2019 at 6:57 PM

Quote from Tos26

So I have to test the BCDC image ?

That's second test.

Also try using ntpd_tos_00 I posted.

Strange that first didn't work even if tos is set to 0. Maybe your issue is different

Tos26 · February 19, 2019 at 7:25 PM

I test right now the bcdc...

And does it mean that you want the test like that:

Code

    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

Tos26 · February 19, 2019 at 7:48 PM

Congratulations guys !!

It works with the bcdc image : Log file

Code

Jun 22 13:11:57 LibreELEC connmand[341]: wlan0 {del} route fe80:: gw :: scope 0 <UNIVERSE>
Jun 22 13:11:57 LibreELEC connmand[341]: wlan0 {del} route ff00:: gw :: scope 0 <UNIVERSE>
Jun 22 13:11:57 LibreELEC connmand[341]: wlan0 {add} address 192.168.0.19/24 label wlan0 family 2
Jun 22 13:11:57 LibreELEC connmand[341]: wlan0 {add} route 192.168.0.0 gw 0.0.0.0 scope 253 <LINK>
Jun 22 13:11:57 LibreELEC connmand[341]: wlan0 {add} route 192.168.0.254 gw 0.0.0.0 scope 253 <LINK>
Jun 22 13:11:57 LibreELEC connmand[341]: wlan0 {add} route 212.27.40.240 gw 192.168.0.254 scope 0 <UNIVERSE>
Jun 22 13:11:57 LibreELEC connmand[341]: wlan0 {add} route 212.27.40.241 gw 192.168.0.254 scope 0 <UNIVERSE>
Jun 22 13:11:57 LibreELEC connmand[341]: wlan0 {add} route 0.0.0.0 gw 192.168.0.254 scope 0 <UNIVERSE>
Jun 22 13:11:57 LibreELEC connmand[341]: wlan0 {add} route 212.227.81.55 gw 192.168.0.254 scope 0 <UNIVERSE>
Jun 22 13:11:57 LibreELEC connmand[341]: ntp: adjust (jump): +20939080.231378 sec
Feb 19 20:36:39 LibreELEC nmbd[368]: [2019/02/19 20:36:39.527158,  0] ../lib/util/become_daemon.c:138(daemon_ready)
Feb 19 20:36:39 LibreELEC nmbd[368]:   daemon_ready: STATUS=daemon 'nmbd' finished starting up and ready to serve connections

Display More

What are the next steps:

Open a ticket to Libreelec : Who is in charge of this ? (No issue request on github)
My personal case : can I use this test image "in production" at home? Is it based on the 9.0.0 official version ?

Thank you for your support and your availability, it was a pleasure to work with you...

**chewitt** · February 20, 2019 at 3:55 AM Official Post

milhouse will pick that commit into his builds for some testing and as long as no issues are observed we'll add it into an update while reminding the Pi Foundation folks that the issue is still outstanding. The patch will probably miss LE 9.0.1 (which is due imminently) but land in LE 9.0.2. Keep using the modified test image for now; it's better to have a system that works with a few more unresolved Kodi bug than something with fewer bugs that doesn't work.

Tos26 · February 20, 2019 at 7:11 AM

Ok chewitt.

I think I can close the discussion.

Thank you again to both of you.

**chewitt** · March 9, 2019 at 4:21 AM Official Post

I've been experiencing the same "connman attempting to use IPv6 NTP servers" issue while poking WireGuard support. I finally managed to track down one of the connman developers, which led to this chat:

Code

[22:28:39]  <wagi>    IIRC, we try resolve the nameservers and when we get an IPv6 we try it. Don't know if we have some logic in place which checks if IPv6 is up
[22:31:04]  <wagi>    Indeed, we try IPv6 without checking if IPv6 is setup
[22:31:20]  <wagi>    So that explains the 'Time request for server' message
[22:31:44]  <wagi>    We should check if IPv6 is up and running before trying to send IPv6 frames :D

Fingers crossed there will a patch to test in the near future

Tos26 · March 9, 2019 at 2:25 PM

I hope so too.

Tos26 · March 19, 2019 at 5:53 PM

Hello chewitt, vpeter,

I try to find where is located the workaround provided by vpeter for my issue in the librelec repository and I don't find.

Could you indicate me where is the file(s) modified in the repo in order to check when this issue will be officially solved and when I can switch to an official version ?

In other words, how can I know if this issue is fixed ?

Thank you.

**vpeter** · March 19, 2019 at 6:04 PM

It is not fixed because this part is not (yet) included in LE.

Tos26 · March 19, 2019 at 6:11 PM

Ok vpeter, but how can I check when this part will be included in LE?

How did you check that just now?

**chewitt** · March 22, 2019 at 7:56 AM Official Post

vpeter can you do an RPi image for these folks to test with this commit: TEMP: bump connman to HEAD to test ntp fix · chewitt/LibreELEC.tv@10982bd · GitHub

There are some connman changes in the last week which tweak the retry behaviour (it also impacts behaviour with WireGuard) and those changes may also resolve the issue. If it does fix I will get the connman folks to make a release so we can bump master/9.0.

**vpeter** · March 22, 2019 at 9:35 AM

Quote from chewitt

can you do an RPi image for these folks to test with this commit: TEMP: bump connman to HEAD to test ntp fix · chewitt/LibreELEC.tv@10982bd · GitHub

libreelec-rpi2.arm-9.0-connman-head-ntp-fix.img.gz

Tos26 · March 25, 2019 at 7:36 PM

Hello guys !

I just tested this image and I got the same issue : No NTP sync.

Sorry chewitt.