On Mon, Apr 11, 2016 at 03:04:58PM +0000, Ledda William EXT wrote: > Using the ethernet interface I get the port dataset of all ports of > the Boundary Clock where my local port is connected, but not the > port dataset of the local port. Using UDS I get the port dataset of > the local port but not of the boundary clock. Is there any special > reason about this difference?
When you send out through the Ethernet interface, the local port does not receive the message, and even if it did, it cannot reply to itself. So, to get local status, use the UDS method. If you use '-b 1' with the UDS option, then ptp4l will forward the message, and you should see replies from your BC as well. HTH, Richard ------------------------------------------------------------------------------ Find and fix application performance issues faster with Applications Manager Applications Manager provides deep performance insights into multiple tiers of your business applications. It resolves application problems quickly and reduces your MTTR. Get your free trial! https://ad.doubleclick.net/ddm/clk/302982198;130105516;z _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
