Hi, It happens with one message "Delay Response" in the length 104 bytes. Did you check your VLAN, may be the VLAN add the 4 bytes? Did you see this behavior without using VLAN?
What is your ptp4l configuration? Erez ________________________________ From: Sun, Steven (NSB - CN/Qingdao) [steven....@nokia-sbell.com] Sent: 09 January 2019 19:18 To: Linuxptp-devel@lists.sourceforge.net Subject: [Linuxptp-devel] linuxptp2.02 processing the extra 4 bytes which is not in PTP length Hello all, Glad to join the linuxptp devel mail list. We met an issue about ptp4l processing 4 more bytes which is not in PTP but in UDP payload. Ptp4l keep reporting failure log as below: Jan 07 12:11:58 slot-15 ptp4l[12876]: [247083.836] port 1: new foreign master fcaf6a.fffe.029a96-1 Jan 07 12:11:59 slot-15 ptp4l[12876]: [247084.572] selected local clock 48df37.fffe.3a9f51 as best master Jan 07 12:12:02 slot-15 ptp4l[12876]: [247087.836] selected best master clock fcaf6a.fffe.029a96 Jan 07 12:12:02 slot-15 ptp4l[12876]: [247087.836] running in a temporal vortex Jan 07 12:12:02 slot-15 ptp4l[12876]: [247087.836] port 1: LISTENING to UNCALIBRATED on RS_SLAVE Jan 07 12:12:02 slot-15 ptp4l[12876]: [247087.962] port 1: bad message Jan 07 12:12:02 slot-15 ptp4l[12876]: [247088.031] port 1: bad message Jan 07 12:12:03 slot-15 ptp4l[12876]: [247088.985] port 1: bad message These 4 bytes is out of the PTP length which defined in PTP header. I checked they are included in the UDP payload, so should not be FCS bytes. Not sure about the purpose of these 4 bytes but PTP may should not process them. [cid:image001.png@01D4A804.863060C0] Thanks, Steven
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
