On Thu, Apr 16, 2020 at 09:22:59AM -0700, Ahmad Byagowi wrote:
> Oh I see. What does it take to add unicast to the TC code? Would you
> be interested? I would love help with the implementation. Perhaps
> the first question is, do you see a major roadblock to do that?
The main issue is the IPv4/6
Oh I see. What does it take to add unicast to the TC code? Would you be
interested? I would love help with the implementation. Perhaps the first
question is, do you see a major roadblock to do that?
Sent from my iPhone
> On Apr 16, 2020, at 8:10 AM, Richard Cochran wrote:
>
> On Thu, Apr 16,
On Thu, Apr 16, 2020 at 12:29:36AM -0700, Ahmad Byagowi wrote:
> I was able to figure out the routing issue by adding the sub net instead of
> the IP for the next hop.
> However I am still unable to get the transparent clock working.
I am sorry to say that the TC code does not support unicast.
Th
I was able to figure out the routing issue by adding the sub net instead of
the IP for the next hop.
However I am still unable to get the transparent clock working.
on the GM side I am using the followings
ptp4l -P -i enp25s0f0 -f GM.cfg
with GM.cfg being
[global]
dataset_comparison
On Tue, Aug 14, 2018 at 06:50:13PM +, Keller, Jacob E wrote:
> In hardware timestamping mode, I believe you just need a device which
> supports a single clock over multiple ports.
Right. In practice, you can use the marvell link street devices, as
these already have kernel support.
> You c
> -Original Message-
> From: Reto Hermann [mailto:reto.herm...@kistler.com]
> Sent: Tuesday, August 14, 2018 12:37 AM
> To: 'linuxptp-users@lists.sourceforge.net' us...@lists.sourceforge.net>
> Subject: [Linuxptp-users] Transparent Clock
>
> Hi,
>
> what hardware does the ptp4l v2.0 tran
