@FilterPunk: Working fine for me. The tolerance which chrony calculates is +/- 5-6 microseconds (Setup: PTP grandmaster is provided by a CM4 IO board; PTP slaves are Raspberry Pi5's running `timemaster`; PTP packets are delivered over ordinary PTP-agnostic switches, lacking transparent clock, thus introducing inaccuracy)
On the client side
On the client side
Code:
$ chronyc sourcesMS Name/IP address Stratum Poll Reach LastRx Last sample===============================================================================#* PTP0 0 2 377 3 +202ns[ +331ns] +/- 5461ns^- ntp.creoline.net 2 10 377 337 +207us[ +203us] +/- 51ms^- byggvir.de 2 10 377 1005 -421us[ -466us] +/- 41ms^- ntp2.lwlcom.net 1 10 377 557 -26us[ -44us] +/- 11ms^- ntp1.rrze.uni-erlangen.de 1 10 337 69 -176us[ -176us] +/- 3723usStatistics: Posted by sgiessl — Wed Feb 28, 2024 8:10 am