TAI/UTC offset never gets set

[Steve-Tech]

Hi, maybe this is some sort of user error, but I noticed that the TAI offset never gets set for either the system or in the announce messages.

In my Wireshark captures, a Statime grandmaster never sets originCurrentUTCOffset, leaving it at 0, PTP_UTC_REASONABLE is also False; even though Chrony has set ADJ_TAI to 37 on the grandmaster device. I would expect originCurrentUTCOffset to be equal to ADJ_TAI (37).

Even if originCurrentUTCOffset is not 0, e.g. 37, such as with a LinuxPTP grandmaster. Statime never sets the system's ADJ_TAI resulting in the UTC time being 37 seconds ahead.

I also have concerns that leap seconds might not be working, as set_properties is responsible for both setting ADJ_TAI and leap seconds, however I haven't tested it.

Thanks,
Steve

[davidv1992]

Getting the UTC offset from the system clock when statime is a grandmaster is not something we currently implement unfortunately. Feel free to open a PR implementing this, however this will likely change significantly anyway when we start merging statime-linux into ntpd-rs hopefully later this year or early next year.