On Wed, May 27, 2020 at 04:38:18PM +0000, Patrick Nowak wrote: > This seems to be a term defined in the Wireshark PTP protocol > implementation (https://wiki.wireshark.org/Protocols/ptp). It looks > like this is transported inside the flags of the PTP message header, > responding to bit 3 of the flags field.
This is how the bits are defined. | Octet | Bit | Name | |-------+-----+------------------------| | 0 | 0 | alternateMasterFlag | | 0 | 1 | twoStepFlag | | 0 | 2 | unicastFlag | | 0 | 5 | PTP profile Specific 1 | | 0 | 6 | PTP profile Specific 2 | | 0 | 7 | reserved | | 1 | 0 | leap61 | | 1 | 1 | leap59 | | 1 | 2 | currentUtcOffsetValid | | 1 | 3 | ptpTimescale | | 1 | 4 | timeTraceable | | 1 | 5 | frequencyTraceable | I guess you are talking about "currentUtcOffsetValid" ? If your ptpl4 instance is the GM, then you can set this value using the GRANDMASTER_SETTINGS_NP management message. For example, you can use somthing like the following shell script example. pmc -u -b 0 \ "set GRANDMASTER_SETTINGS_NP clockClass 248 clockAccuracy 0xfe offsetScaledLogVariance 0xffff currentUtcOffset 37 leap61 0 leap59 0 currentUtcOffsetValid 1 ptpTimescale 1 timeTraceable 1 frequencyTraceable 1 timeSource 0x50 " HTH, Richard _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
