> -----Original Message----- > From: Taber, Alan [mailto:alan.ta...@lmco.com] > Sent: Thursday, December 15, 2016 12:07 PM > To: Richard Cochran <richardcoch...@gmail.com> > Cc: linuxptp-users@lists.sourceforge.net > Subject: Re: [Linuxptp-users] EXTERNAL: Re: PTP packets not being acted upon > by > RHEL 7 server > > Thanks, Richard. We're running IPv4 only. I'll check into Layer2 and report > back. > > Since my previous email I've tried the same ptp4l -i enp9s0 -m on a second > server > on the network, and it also is ignoring the other two asserting sources and > declaring itself as the master clock, and I see announce and sync packets > from all > three sources on Wireshark. So there's something in the setup of the servers > that > is preventing them from listening for those packets. > > Best regards, > Alan >
Try running tcpdump without it setting the promiscuous flag. This smells suspiciously of a firewall issue, so maybe it's not the same thing you checked earlier? in RHEL 7 that should be firewalld but it might just iptables... What I suggest: run ptp4l and simultaneously run tcpdump but set the flag that prevents tcpdump from enabling promiscuous mode. If tcpdump still indicates that it sees packets but ptp4l does not then that is a different issue. You could also try running tcpdump in promicuous mode at the same time as ptp4l and see if that causes ptp4l to start seeing the packets. Thanks, Jake ------------------------------------------------------------------------------ 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
