On Thu, Jun 15, 2017 at 08:58:40AM -0400, Chris Perl wrote:
> On Thu, Jun 15, 2017 at 8:48 AM, Miroslav Lichvar <mlich...@redhat.com> wrote:
> > It works even with <7.4 kernels if there is only one interface which
> > supports HW timestamping as SOF_TIMESTAMPING_OPT_CMSG is not required
> > in such case.
> Oh, exciting, thanks!
> Does that mean exactly one up interface that supports HWTSTAMP_FILTER_ALL?
> Meaning, would I be ok if the other interfaces on the machine
> supported things like HWTSTAMP_FILTER_PTP_V1_L4_SYNC,
> HWTSTAMP_FILTER_PTP_V1_L4_DELAY_REQ, etc, but did not support
No, that won't work. The filter applies to received packets. If an
interface doesn't have HWTSTAMP_FILTER_ALL, it can still generate
transmit timestamps and chronyd won't know from which interface it
Please note that the OPT_CMSG option is needed only for IPv4. If you
could use NTP over IPv6, that should work even with multiple
To unsubscribe email chrony-users-requ...@chrony.tuxfamily.org
with "unsubscribe" in the subject.
For help email chrony-users-requ...@chrony.tuxfamily.org
with "help" in the subject.
Trouble? Email listmas...@chrony.tuxfamily.org.