Jiri Benc <jbenc@...> writes: > > On Wed, 2 Apr 2014 18:15:27 +0200, Richard Cochran wrote: > > > +/* > > > + * Send message to the given address. This is intended for management > > > + * messages only, thus goes always to the general port. > > > > There are a couple of unicast options for PTP. We should try to make > > this new interface in a way that will be useful later on to support > > unicast, which includes events, IIRC. > > Okay, I can add a couple more parameters to match the "send" callback. > Not sure it's worth it, though - adding them later, when they are > actually needed, would be very easy. > > I have no strong preference either way. > > Jiri >
Hi, I have the same request about unicast either uds or pptp4l. Actually, Shall it call hybrid mode? Master send sync and follow up by multicast, slave send Delay_Req to master by unicast, master send Delay_Resp to slave by unicast if E2E mode. I don't know why you don't implement this, but unicast really reduce the network loading than multicast, doesn't it? And maybe multicast have the limitation of communication between master and slave if one of them is behind the secure gateway or high-end router? Anyway, would you provide the whole patch for unicast based on linuxptp- 1.5. After I change the address instead of multicast in trasnport_send, it really send to host, but always failed in poll in sk_recceive. Regards, Duncan ------------------------------------------------------------------------------ _______________________________________________ Linuxptp-devel mailing list Linuxptp-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-devel
