On Fri, Apr 20, 2018 at 03:24:50PM +0200, Jord Pool wrote: > 15:17:55.746473 IP 10.0.0.218.ptp-event > ptp-primary.mcast.net.ptp-event: > UDP, length 44 > 15:17:55.746504 IP 10.0.0.218.ptp-general > > ptp-primary.mcast.net.ptp-general: UDP, length 44 > 15:17:55.784460 IP 10.100.0.1.ptp-event > ptp-primary.mcast.net.ptp-event: > UDP, length 44 > > When running the command $ sudo ptp4l -H -i eno1 -s -m it returns the > following: > > ptp4l[9820.775]: selected /dev/ptp0 as PTP clock > ptp4l[9820.776]: port 1: INITIALIZING to LISTENING on INIT_COMPLETE > ptp4l[9820.777]: port 0: INITIALIZING to LISTENING on INIT_COMPLETE > ptp4l[9828.219]: selected best master clock 3c5282.fffe.5abe30 > ptp4l[9834.262]: selected best master clock 3c5282.fffe.5abe30 > ptp4l[9842.064]: selected best master clock 3c5282.fffe.5abe30 > ptp4l[9848.472]: selected best master clock 3c5282.fffe.5abe30
I think that means ptp4l is not receiving or is ignoring the PTP messages. Maybe it's a different PTP domain? Running ptp4l in strace and/or with -l 7 might give us more clues. -- Miroslav Lichvar ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
