I need to configure unicast communications between one ptp master and 2 slaves, using ptpd 2.3.1. Before that, I've tried to setup the master/slaves configuration for multicast and everthing works fine.
By editing client-e2e-socket.conf these are my actual choices (I will omit the default parameters that I didn't edit)
Those config examples are out of date unfortunately, we will update them for the next version.
You cannot set multiple entries of the same type, you end up setting it only once so the last value is set: in your config, only slave 2 will get PTP.
use this on the master:
ptpengine:unicast_destinations=ip_1,ip_2,ip_n
You can also use unicast negotiation (G.8265.1) in ptpd 2.3.1, then you don't need to configure slave IPs on the GM, just set ptpengine:unicast_negotiation=y on both.
Thanks.
Wojciech
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi everyone,
I need to configure unicast communications between one ptp master and 2 slaves, using ptpd 2.3.1. Before that, I've tried to setup the master/slaves configuration for multicast and everthing works fine.
By editing client-e2e-socket.conf these are my actual choices (I will omit the default parameters that I didn't edit)
MASTER
ptpengine:interface = int_master
ptpengine:preset = masteronly
ptpengine:ip_mode = unicast
ptpengine:unicast_address = ip_addr_slave1
ptpengine:unicast_address = ip_addr_slave2
ptpengine:clock_class = 126
SLAVES
ptpengine:interface = int_slave
ptpengine:preset = slaveonly
ptpengine:ip_mode = unicast
ptpengine:unicast_address = ip_addr_master
ptpengine:clock_class = 255
With this configuration none of the slaves can synchronize with the master.
Do you see some errors in the configurations?
I'm not sure about "ptpengine:unicast_address", maybe it should be "ptpengine:unicast_destinations"?
Best regards,
Mark
Last edit: Mark Cate 2015-10-07
Hi,
Those config examples are out of date unfortunately, we will update them for the next version.
You cannot set multiple entries of the same type, you end up setting it only once so the last value is set: in your config, only slave 2 will get PTP.
use this on the master:
ptpengine:unicast_destinations=ip_1,ip_2,ip_n
You can also use unicast negotiation (G.8265.1) in ptpd 2.3.1, then you don't need to configure slave IPs on the GM, just set ptpengine:unicast_negotiation=y on both.
Thanks.
Wojciech
Hi Wojciech,
I modify the master configuration as you suggested (ptpengine:unicast_destinations parameter) and now all the slaves are synchronized, thank you!
Mark