ptpd 2.3.1 not sending delay_req

[Doug Braden]

I'm new to ptpd, but believe I have it configured correctly to act as a slave to a separate hardware master on my network. The master is configured to use 8265.1 and sees a slave connect when I start ptpd with the following options:

ptpd2 -C -s -i enp3s0 -U -u xxx.xxx.xxx.91 -g -d 4 -r -4

where .91 is the master clocks IP address.

The ptpd status file shows:

---

2017-09-12 08:48:46.054360, lstn_reset, 194
2017-09-12 08:48:47.058189, slv, 0020d2fffecd0642(unknown)/2, 0.000000000, 0.000000000, 0.000000000, 0.000000000, 4393.539428711, I, 0.000000000, 0, 0.000000000, 0, 0, 0, 0.000000000, 0.000000000

---

It looks like I never get the offset or delay data. When I run wireshark, I see "Announce Message" from the ptp grand master (A RAD MiCLK SFP with GPS connection) and "Signalling Message" packets from the CentOS 7 box running ptpd configured as a slaveonly. My understanding is that the slave should request the delay from the master and that prompts the master to send a delay_resp packet. Based on all the zeroes in the status file, I'm guessing I never get the delay from the master. The master also never increments its delay_req counter.

Is my understanding of the communication process correct? Are there settings in ptpd I'm missing to successfully use 8265.1? I have disabled all firewalls as well as SELinux while attempting to get this working.

[Sam Chang]

I have the same problem, I used wireshark to capture packet, but I didn't capture any request from slave.

[Sam Chang]

Doug Braden,
I use unicast mode in my slave and add unicast_addres=master address in conf.
it work for me.

[Manu Thakur]