netdev - Re: [PATCH net-next 00/10] PTP support for DSA and mv88e6xxx driver.

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]

Message-ID: <20180214035939.qlamdershe7ydllk@localhost>
Date:   Tue, 13 Feb 2018 19:59:40 -0800
From:   Richard Cochran <richardcochran@...il.com>
To:     Andrew Lunn <andrew@...n.ch>
Cc:     David Miller <davem@...emloft.net>,
        netdev <netdev@...r.kernel.org>,
        Vivien Didelot <vivien.didelot@...oirfairelinux.com>,
        brandon.streiff@...com
Subject: Re: [PATCH net-next 00/10]  PTP support for DSA and mv88e6xxx driver.

On Wed, Feb 14, 2018 at 01:07:41AM +0100, Andrew Lunn wrote:
> Further work is requires to support bridges using Boundary Clock or
> Transparent Clock mode.

Small correction: Boundary Clock (BC) works just fine if the DSA ports
are separate (not in a bridge device).

If the DSA ports *are* connected together in a bridge device, the
multicast PTP messages are incorrectly (?) forwarded out all ports by
the kernel SW bridge code.  The work around is to add a bridge rule to
drop these frames.  With the rule in place, BC also works in this
configuration.

Transparent Clock would work as far as the driver and kernel go, but
ptp4l does not yet implement it.

Thanks,
Richard