It seems correct : http://ix.io/jit
What is the best addon for the test : System tools or network tools ? And what kind of test can I perform with these tools ?
It seems correct : http://ix.io/jit
What is the best addon for the test : System tools or network tools ? And what kind of test can I perform with these tools ?
Ok done.
I added the -v option to have more detail: http://ix.io/1bqh
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.
Ok but as I said, my IP camera gets the time from NTP through the same wifi modem/router.
I will try the workaround you proposed but I'm a little bit frustrated to not understand the root cause.
Many thanks for your help and if you have a new idea, don't hesitate to post it
And if I find the solution, I will post it here.
Camera is also wifi?
The only difference is that camera is out the dhcp domain.
Well, I newer saw this issue in real life. So someone else would need to step in to help you.
Ok, thanks.
Setting different TOS could help according to [Solved] Time does not sync on Pi 3 and with official dongle - Raspberry Pi Forums
QuoteThat 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 : ^^^^
Effectively, it's a good thing to test. I will test with my other PI3 (not a B+) just to see if there is the same issue.
You say that it's impossible to test with ToS = 0 without to build a dedicated image?
So, I have the same issue with my second PI3
Hello vpeter,
I am at work now, I will try this evening.
Thank you.
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
Display More
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
Raspberry Pi 3 built-in WiFi SSH NTP Problem · Issue #1519 · raspberrypi/linux · GitHub
links to Sets the BCDC priority to constant 0 · raspberrypi/linux@983cf7a · GitHub which from the age of commits i'd expect to be included with our kernel, but it's not something I can test (am travelling at the moment).
I've pinged some of the pi folks, but traffic to that GH ticket might be a good idea too
It is not included in LE9 for RPi2.