Hello, We have found an issue with a certain boundary clock that only responds to a single grant request TLV per signaling message in unicast configuration. For instance, our slave clock running ptp4l requests 300 seconds of SYNC and DELAY_RESP messages in a single signaling message, but the BC only responds with a TLV for the SYNC message. This causes ptp4l to repeatedly (every 2 seconds) send out the same grant request with both message type requests, and the BC always responds with just the SYNC.
Eventually, the grant for DELAY_RESP expires, and when we request again, it responds with the sync grant with a duration of 0. My question: is there any way to configure ptp4l to not concatenate TLVs in unicast grant requests? The same boundary clock works ok with a proprietary ptp stack, which is sending unicast grant requests one message type at a time. Thank you, Peter Sadrozinski -- This electronic communication and the information and any files transmitted with it, or attached to it, are confidential and are intended solely for the use of the individual or entity to whom it is addressed and may contain information that is confidential, legally privileged, protected by privacy laws, or otherwise restricted from disclosure to anyone else. If you are not the intended recipient or the person responsible for delivering the e-mail to the intended recipient, you are hereby notified that any use, copying, distributing, dissemination, forwarding, printing, or copying of this e-mail is strictly prohibited. If you received this e-mail in error, please return the e-mail to the sender, delete it from your computer, and destroy any printed copy of it.
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
