LibreELEC even connected to the network does not access the internet

uMarcello · December 18, 2018 at 6:08 PM

First, hello

After I switched my Internet service provider to another, my RPi and other devices went haywire. I set up my router and all of them, with RPi execution, returned to normal. He refuses to help the time, does not update add-on. This all in version 9.0. Using 8.2.5 everything works perfectly.

**chewitt** · December 19, 2018 at 2:50 AM Official Post

run "journalctl -b 0 --no-pager | paste" and "cat /storage/.kodi/temp/kodi.log | paste" a couple of mins after boot and share the URL links.

uMarcello · December 19, 2018 at 9:58 PM

Quote from chewitt

run "journalctl -b 0 --no-pager | paste" and "cat /storage/.kodi/temp/kodi.log | paste" a couple of mins after boot and share the URL links.

Log link: http://ix.io/1wlr

I also noticed that it does not set the right time/day. He says it's June 18, 2018.

**chewitt** · December 20, 2018 at 3:52 AM Official Post

Code

Jun 22 11:12:00 connmand[411]: Time request for server 2607:f740:1::42c failed (101/Network is unreachable)
Jun 22 11:12:00 connmand[411]: Time request for server 2001:41d0:2:b7a2:0:162:b:123 failed (101/Network is unreachable)
Jun 22 11:12:00 connmand[411]: Time request for server 2001:550:1d05:30::58e:3ef3 failed (101/Network is unreachable)
Jun 22 11:12:00 connmand[411]: Time request for server 2001:12ff::8 failed (101/Network is unreachable)
Jun 22 11:12:16 connmand[411]: Time request for server 2607:f740:1::42c failed (101/Network is unreachable)
Jun 22 11:12:16 connmand[411]: Time request for server 2001:41d0:2:b7a2:0:162:b:123 failed (101/Network is unreachable)
Jun 22 11:12:16 connmand[411]: Time request for server 2001:12ff::8 failed (101/Network is unreachable)
Jun 22 11:12:16 connmand[411]: Time request for server 2001:440:1880:5555::2 failed (101/Network is unreachable)
Jun 22 11:12:30 connmand[411]: Time request for server 2607:f740:1::42c failed (101/Network is unreachable)
Jun 22 11:12:30 connmand[411]: Time request for server 2001:41d0:2:b7a2:0:162:b:123 failed (101/Network is unreachable)
Jun 22 11:12:30 connmand[411]: Time request for server 2001:12ff::8 failed (101/Network is unreachable)
Jun 22 11:12:30 connmand[411]: Time request for server 2001:440:1880:5555::2 failed (101/Network is unreachable)
Jun 22 11:12:51 connmand[411]: Time request for server 2607:f740:1::42c failed (101/Network is unreachable)
Jun 22 11:12:51 connmand[411]: Time request for server 2001:41d0:2:b7a2:0:162:b:123 failed (101/Network is unreachable)
Jun 22 11:12:51 connmand[411]: Time request for server 2001:12ff::8 failed (101/Network is unreachable)
Jun 22 11:12:51 connmand[411]: Time request for server 2001:440:1880:5555::2 failed (101/Network is unreachable)

Display More

^ it appears to be attempting NTP requests to IPv6 servers (2001:12ff::8 is poot.ntp.org) and since we don't support IPv6 that will fail. If the time is not set correctly SSL certs are invalidated (they are valid for a start/end time range in the future) and everything which uses SSL (basically everything these days) lots of internet based functions break. If no time is set the system clock defaults to something weird like the release date of the GCC compiler that was used in our build system, which is something like June 2018.

NTP is handled by connman which is configured to fall-back/default to using 0.pool.ntp.org, 1.pool.ntp.org, 2.pool.ntp.org as it's NTP servers if nothing is explicitly set via DHCP or user config, but these are being resolved to IPv6 addresses (presumably by the DNS functions in your router) so you can try overriding these with IPv4 address in the LE settings add-on, e.g.

Code

;; ANSWER SECTION:
0.pool.ntp.org.        149    IN    A    178.32.220.7
0.pool.ntp.org.        149    IN    A    162.213.34.249
0.pool.ntp.org.        149    IN    A    185.103.117.60
0.pool.ntp.org.        149    IN    A    176.221.42.125
;; ANSWER SECTION:
1.pool.ntp.org.        149    IN    A    199.102.46.73
1.pool.ntp.org.        149    IN    A    37.187.5.167
1.pool.ntp.org.        149    IN    A    193.228.143.24
1.pool.ntp.org.        149    IN    A    216.229.0.49
;; ANSWER SECTION:
2.pool.ntp.org.        149    IN    A    69.164.198.192
2.pool.ntp.org.        149    IN    A    80.127.119.186
2.pool.ntp.org.        149    IN    A    167.114.156.48
2.pool.ntp.org.        149    IN    A    45.32.75.249

Display More

^ pick some IP's from those servers. You might also find that the router provides NTP if you configure it's IP address as the first NTP server.

uMarcello · December 20, 2018 at 11:12 AM

From what I understand, I should use one of these IPs instead of DNS in IPv4, right?

**chewitt** · December 22, 2018 at 5:20 PM Official Post

Configure one as an NTP server. If you configure it as a DNS server things will definitely not work.

uMarcello · December 25, 2018 at 4:56 PM

Quote from chewitt

Configure one as an NTP server. If you configure it as a DNS server things will definitely not work.

The result was not successful. I did everything. LibreELEC says the date is July 22, 2018.

**chewitt** · December 26, 2018 at 6:09 AM Official Post

Share the systemd journal again (as in post #3) please.

uMarcello · December 26, 2018 at 11:38 PM

Quote from chewitt

Share the systemd journal again (as in post #3) please.

Here it is: http://ix.io/1wsm

Is there any way to change the certificate?

**chewitt** · December 27, 2018 at 12:21 AM Official Post

That's a Kodi debug log not the systemd journal log (read post #2) so it doesn't show anything useful. And there's nothing wrong with the certificate on the update server .. but your device has broken NTP so the current datetime is before the validity of the cert starts; hence it throws an error.

uMarcello · December 27, 2018 at 12:51 AM

Quote from chewitt

That's a Kodi debug log not the systemd journal log (read post #2) so it doesn't show anything useful. And there's nothing wrong with the certificate on the update server .. but your device has broken NTP so the current datetime is before the validity of the cert starts; hence it throws an error.

Problem is I've already put everything that is NTP server. And even so I did not succeed.

**chewitt** · December 30, 2018 at 7:41 AM Official Post

If you don't show me the systemd debug log I can only guess at the changes you made and what effect they had. Your problem, not my problem.

uMarcello · January 8, 2019 at 4:35 AM

Sorry to delay for feedback. I still have the same problem.

Log: http://ix.io/1xmd

My time zone looks like this:

**chewitt** · January 11, 2019 at 8:24 AM Official Post

The log shows that it's connecting to ipv6 servers (only) for NTP and all requests fail. So did you (as asked) manually configure a single ipv4 address as NTP1 server and reboot to force the change? .. that's the log I want to see. Also remove the autostart.sh script.

KampalaMan · February 6, 2019 at 7:11 AM

Hello Chewitt,

I am having the same issue with connman resolving to and then failing to reach ipv6 addresses for NTP servers. Switching to ipv4 addresses(e.g.163.172.205.63) in place of domain names (europe.pool.ntp.org) did not solve the problem.

Disabling ipv6 with (echo "net.ipv6.conf.all.disable_ipv6=1" >/storage/.config/sysctl.d/ipv6.conf) stopped the multiple errors from appearing in the journal, but then a (99/Cannot assign requested address) appeared one time. And the date/time is still wrong. Manually setting it (date -s 201902060930) did allow access to Add-on repositories, but obviously auto setting would be best.

I'm at a loss as to what to try next, and would appreciate any suggestions. Some log snippets are attached.

Thank you.