It should be online again, sorry i turn off electricity here yesterday
Thanks, no problem, I will try to do the captures again now.
Very odd, but earlier on while I was doing the captures I noticed the router (or something behind it), started rewriting the packets coming from the NTP server. Their UDP destination port had hardcoded value of 123. Now it is working correctly. Do you know why would that possibly happen?
Also could you please flash the device with a clean OS without any application pushed to it? We would like to try to get to the bottom of the issue and this will be super helpful.
Hello
I didn’t change anything
Sometimes my intuition says that this router is forcing something to go through i don’t know why exactly (i have problems with dns sometimes for example)
I will clean and reflash it in 30 minutes
Excellent, thanks a lot!
New device:
https://dashboard.balena-cloud.com/devices/d45990f2423c0349564a416109836911/summary
Ahh i have to create new application right?
Right, it will pull the current one
New device with application:
https://dashboard.balena-cloud.com/devices/d45990f2423c0349564a416109836911/summary
Device without any application:
https://dashboard.balena-cloud.com/devices/72631ea261b9c909f687fdac22397277/summary
Thanks! I tried this with the device without any application and the symptoms are again with the router doing port number rewrites. What is the router model more specifically?
Hi, it’s PHICOMM KE 2P
And i think that i forgot to mention - i don’t have this NTP problem with other networks (like mobile wifi hotspot)
BTW, have you tried updating the router firmware? Or it is already running on latest firmware? From the looks of it it looks like a firmware bug is the root cause of this.
I have a latest firmware (that’s what online upgrade function says)
Thanks, I created a GitHub issue for this: https://github.com/balena-os/meta-balena/issues/2000
You may follow it for seeing how that goes as this will need more input from my colleagues on the OS team.
Thank you very much!
Hello Adam, finally the issue has been closed.
You need to change the value of acquisitionport
in the chrony configuration file from 123 to 1234
.
Let us know if that works
Thanks for the answer! Thanks for the work also.
Unfortunately i changed a router and problem is gone automaticaly