In-Reply-To: Hello,
Following somewhat from the previous thread "Forwarding management messages to UDS port" https://sourceforge.net/p/linuxptp/mailman/message/36148604/ I understand that the UDS is for "local control only" and so not treated the same as other ports managed by ptp4l. An example of this difference is that clock_do_forward_mgmt() explicitly does not forward certain Management messages to the UDS. I'm assuming that Responses (and Acknowledge) messages are whitelisted since it could be user of the UDS which made the original request, an example being using pmc to poll every clock reachable within some number of hops. Is this a safe assumption? And if so, is there any reason to forward-to-UDS Responses whose targetClockId is *not8 the local ptp4l instance? I have a case where ptp4l is overhearing another OC's response to some 3rd party request, and because it's a RESPONSE with boundaryHops > 0 is being forwarded down the UDS. Worse if those responses are errors due to propritary TLVs. I can and will beef up my UDS client to be mindful that despite using effectively -b0, responses on the network outside my control may still arrive. If it's acceptable, I'll also send through a patch checking clockId's before forwarding responses to the USD. I'm not yet checking for the wildcard id, but then I don't really know if a response message to the broadcast ID is a sensible thing to allow anyway. Thanks, David _______________________________________________ Linuxptp-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
