... 0000 = messageId: Sync Message (0x00) ... 0010 = versionPTP: 2 messageLength: 44 subdomainNumber: 0 flags: 0x002c 0... ... ... ... = PTP_SECURITY: False .0.. ... ... ... = PTP profile Specific 2: False ..0. ... ... ... = PTP profile Specific 1: False ...
PTP Pdelay_Req Message PTP Pdelay_Resp Message PTP Pdelay_Resp_Follow_Up Message PTP Signaling Message PTP Management Message BFD BGP BOOTP DHCP DHCPv6 Diameter DNS EVPN IP FPM IFIT L2TP MPLS LDP MSDP Message Format NetStream sFlow NG MVPN Control Messages RIP RIPng NTP RADIUS Segment Routing...
... ...0 = PTP_LI_61: Falsecorrection: 0.000000 nanosecondscorrection: Ns: 0 nanoseconds SubNs: 0.000000 nanosecondsClockIdentity: 0x704433fffe297564SourcePortID: 4363sequenceId: 48672control: Delay_Req Message (1)logMessagePeriod: 127originTimestamp (seconds): 0originTimestamp (nanoseconds): ...
is true, this property provides the current interval used for successive transmissions of the Pdelay_Req message by this port. According to the standards, a message transmission interval is a signed integer in the range -128 to 127, represented as the logarithm to the bas...
> ---Original Message--- > From: Richard Cochran <richardcoch...@gmail.com> > Sent: Sunday, June 13, 2021 11:39 PM > To: Karthick Gunasekaran <karth...@pluribusnetworks.com> > Cc: linuxptp-users@lists.sourceforge.net > Subject...
... ...0 = PTP_LI_61: Falsecorrection: 0.000000 nanosecondscorrection: Ns: 0 nanoseconds SubNs: 0.000000 nanosecondsClockIdentity: 0x704433fffe297564SourcePortID: 4363sequenceId: 48672control: Delay_Req Message (1)logMessagePeriod: 127originTimestamp (seconds): 0originTimestamp (nanoseconds): ...
(IEEE1588)0000 ... = transportSpecific: 0x00...0 ... = V1 Compatibility: False... 0010 = messageId: Path_Delay_Req Message (0x02)... 0010 = versionPTP: 2messageLength: 54subdomainNumber: 0flags: 0x002c0... ... ... ... = PTP_SECURITY: False .0.. ... ... ... = ...