On Mon, 10 Jul 2023 at 04:08, Vladimir Dubrovsky <vdubrov...@crestron.com> wrote:
> Hello Erez, > > Thank you for your time. > > I think the problem is not in Ethernet driver, because all applications > over IPv6 work fine, at least I am not aware of a problem. PTP over IPv4 > works fine as well. > Your conclusion is wrong. As time-stamps and PTP have a separate handling in the Ethernet driver. Other IPv6 applications do not indicate if PTP IPv6 works or not in the Ethernet driver. > The problem is only in PTP over IPv6, and the problem is on receive side, > because I decoded packets in WireShark and I see reasonable time stamps. I > think somehow PTP extracts wrong time stamps. I agree it can > As far as I know, you can not see the TX time-stamp in wireshark, as they are sent in a separate SKB. You should not conclude the PTP state based on wireshark. I use wireshark to see if PTP packets pass from side to side, i.e. the 2 peers are connected. It is better to look at ptp4l 's own log to understand what happens on the PTP itself. > be misconfiguration in PTP or Linux kernel or something else. If you tell > me what information you need I will send it to you. I just don’t know what > can be needed. > Please send it to the group, there are other engineers in the group that might find the proper solution. The ptp4l configuration and the command line used to start ptp4l. A description of your network. Are m1 and m2 connected directly, or through a switch? A short description of the Linux you use. Does the ptp4l come from the Linux distribution or did you build it from source. And the ptp4l log (for 2 to 3 seconds, and errors if you see). Do not send long logs, we will not read it anyway. Is the Linux you use is vanille or is it a vendor kernel? What Ethernet driver do you use with ptp4? You can put in a compressed archive to save space. Erez Thank you. > > Vladimir > > > Vladimir Dubrovsky | Lead Firmware Engineer > Phone: 201‑367‑6695 > Ext: 12422 > Email: vdubrov...@crestron.com > Crestron Electronics, Inc. > 22 Link Drive, Rockleigh, NJ 07647 > [image: Crestron] <https://www.crestron.com/> > CONFIDENTIALITY NOTICE: This e-mail message and any attachments may > contain confidential and/or privileged information and is solely for the > use of the intended recipients. Any unauthorized review, use, disclosure, > or distribution is strictly prohibited. If you have received this message > in error, please promptly notify the sender, and destroy all copies of the > message and any attachments. > > *From:* Erez <erezge...@gmail.com> > *Sent:* Saturday, July 08, 2023 9:36 AM > *To:* Vladimir Dubrovsky <vdubrov...@crestron.com> > *Cc:* linuxptp-devel@lists.sourceforge.net > *Subject:* Re: [Linuxptp-devel] PTP4L over IPv6 doesn't converge clock > > > > Hi, There are 2 types of time-stamps RX and TX Both are retrieved in the > msghdr of https: //man7. org/linux/man-pages/man3/recvmsg. 3p. html The RX > time-stamp comes with the same message that contains the received packet. > The TX is received with > > ZjQcmQRYFpfptBannerStart > > *This Message Is From an Untrusted Sender * > > You have not previously corresponded with this sender. Please use proper > judgment and caution when opening attachments, clicking links, or > responding to this email. > > ZjQcmQRYFpfptBannerEnd > > Hi, > > > > There are 2 types of time-stamps > > RX and TX > > Both are retrieved in the msghdr of > > https://man7.org/linux/man-pages/man3/recvmsg.3p.html > <https://urldefense.com/v3/__https:/man7.org/linux/man-pages/man3/recvmsg.3p.html__;!!PkykpUBa!Q7GcYl1lDd99tGa7LAsVmwKBZQMFhfSFnATrvhuIKodDXYqGCso13hiCRsbO-3SF35hHKD8ws05CskBAxc3b3g$> > > > > The RX time-stamp comes with the same message that contains the received > packet. > > The TX is received with a message on the error queue after the packet is > sent in the vendor Ethernet driver. > > > > RX time-stamp can be applied to all packets or only PTP (with proper > configuration). > > The TX time-stamp is usually reserved for PTP packets. > > ptp4l can configure your kermel/vendor Ethernet driver. > > > > The mechanizm is identical to all sockets/network layers (raw, ipv4, ipv6) > > in ptp4l and in the kernel netlink (layer 2), > > It fills the message header with the time-stamps in the same manner. > > > > However the mechanism relies on the vendor Ethernet driver (module) to > pass the time-stamp to the net-link on TX time-stamp, and add the > time-stamp to the Linux SKB on RX time-stamp. > > > > According to your description, I would first look in the vendor Ethernet > driver. > > First run with IPv4 and find the RX and TX time stamps. > > And then switch to IPv6. > > > > But there could also be a simple misconfiguration of your ptp4l or your > system. > > You did not provide enough information to defer. > > > > Erez > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Fri, 7 Jul 2023 at 20:46, Vladimir Dubrovsky via Linuxptp-devel < > linuxptp-devel@lists.sourceforge.net> wrote: > > Hello, > > I have a problem with ptp4l working with IPv6 messages. > > We use Linux version 4.19.0+ and ptp4l version 3.1. > > Everything works fine with PTP over IPv4. However when I run PTP over IPv6 > I see that clock can’t converge. I checked messages in WireShark, > everything looks reasonable. I run PTP with “- 6” option for IPv6. > > My feeling is PTP doesn’t read timestamp from IPv6 message properly. > > Do you have any idea what can be a problem or how can I debug the case? > > Thank you. > > > > *Vladimir Dubrovsky* > > | > > *Lead Firmware Engineer* > > Phone: 201‑367‑6695 > > Ext: 12422 > > Email: vdubrov...@crestron.com > > *Crestron Electronics, Inc.* > > 22 Link Drive, Rockleigh, NJ 07647 > > [image: Crestron] <https://www.crestron.com/> > > CONFIDENTIALITY NOTICE: This e-mail message and any attachments may > contain confidential and/or privileged information and is solely for the > use of the intended recipients. Any unauthorized review, use, disclosure, > or distribution is strictly prohibited. If you have received this message > in error, please promptly notify the sender, and destroy all copies of the > message and any attachments. > > _______________________________________________ > Linuxptp-devel mailing list > Linuxptp-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/linuxptp-devel > <https://urldefense.com/v3/__https:/lists.sourceforge.net/lists/listinfo/linuxptp-devel__;!!PkykpUBa!Q7GcYl1lDd99tGa7LAsVmwKBZQMFhfSFnATrvhuIKodDXYqGCso13hiCRsbO-3SF35hHKD8ws05CskAD-efCXg$> > >
_______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
