I have a SecureSync 9400 GrandMaster clock that is appropriately putting out 
PTPv2 Sync and Announce packets (verified by Wireshark listening on a different 
network node). I have run tcpdump -i enp9s0 -v to check to see that the packets 
are getting through to my RHEL 7 server, and they are showing up.

Yet, when I run ptp4l -i enp9s0 -m, I get the following:

Selected /dev/ptp1 as PTP clock
driver changed our HWTSTAMP options
tx_type 1 not 1
rx_filter 1 not 12
port 1: INITIALIZING to LISTENING on INITIALIZE
port 0: INITIALIZING to LISTENING on INITIALIZE
port 1: link up
port 1: LISTENING to MASTER on ANNOUNCE_RECEIPT_TIMEOUT_EXPIRES
selected best master clock 0cc47a.fffe.acbaf7


at this point I can see sync and announce packets on the network from both my 
GrandMaster clock and this RHEL 7 server.

What indicators should I be looking at to see why the local ptp daemon isn't 
listening to the packets the server is receiving?

Thanks in advance for any insight you can share.

Best regards,

Alan Taber
------------------------------------------------------------------------------
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

Reply via email to