On Sat, Mar 12, 2022 at 09:33:18PM EST, Richard Cochran wrote:
>On Sat, Mar 12, 2022 at 06:07:11PM -0500, vincent.cheng...@renesas.com wrote:
>
>> However, because there is no checking of received unicast master to
>> configured
>> unicast table, ptp4l is quite content with packets from previous
On Sat, Mar 12, 2022 at 06:07:11PM -0500, vincent.cheng...@renesas.com wrote:
> However, because there is no checking of received unicast master to configured
> unicast table, ptp4l is quite content with packets from previous master
> 10.64.10.13.
This patch doesn't actually fix the root cause.
From: Vincent Cheng
ptp4l currently does not cancel unicast service on program exit.
This causes problems for subsequent ptp4l session that is using different
masters.
Below example has debug statements to print out announce master address and
received
packet address.
Start unicast slave
