hello,
please read this thread, that's solved the issue for me.
hello,
please read this thread, that's solved the issue for me.
So, it works perfectly. Thank you again.
I posted a request on the RPI github here. Please confirm that it's in the right place.
Ok vpeter, but how can I check when this part will be included in LE?
How did you check that just now?
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.
If the date is not updated (NTP sync), the certificate is not validated and some addons don't work.
See this thread.
Congratulations guys !! ![]()
It works with the bcdc image : Log file
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:
Thank you for your support and your availability, it was a pleasure to work with you...
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:
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.