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 master >> 10.64.10.13. > >This patch doesn't actually fix the root cause. > >If the cancel request fails or is ignored by the remote master, then >the master will continue to send Sync messages, and the issue >persists. > >In general, there is no way for a program to enforce good behavior >from another networked computer. > >The proper fix would be to check the source address of the received >messages.
Added more comprehensive fix. PATCH v2 to follow. Thanks, Vincent _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
