If the IPSec tunnel doesn't support multicast, you would have to use one of the
unicast based profiles, no?
Thanks,
Jake
From: Taber, Alan
Sent: Monday, November 04, 2019 2:35 PM
To: linuxptp-users@lists.sourceforge.net
Subject: [Linuxptp-users] PTP over IPSec?
Hi folks,
Has anyone successful
Hi folks,
Has anyone successfully implemented PTP across an IPSec tunnel? We have a set
up where we have a master clock in one shelter, an IPSec tunnel via hardware on
a pair of ICX-7450 switches between the two shelters, and then a second shelter
with computers that should be slaves to the mas
Hey all, I just wanted to wrap up this thread in case anyone else comes across
this issue. It turns out the source of my problems was the clock I was using.
The VersaSync wasn't sending delay-response messages which was why the slave
systems would never actually sync to VersaSync. This was due t
Hello Richard,
Yeah that's how we expected it to behave thanks.
Means for us we need to patch our VLan dev as it didn't have the pass
through to the hardware.
Other unrelated question how much work do you think it would be to add the
power profile extensions?
E.g the processing for there TLV's
On Mon, Nov 04, 2019 at 07:25:02AM +0100, Armin HAMAR wrote:
> When i use it over a vlan dev then it does have the tag i suspect?
Yes.
Also, with a normal (non-vlan) Linux network interface, ptp4l will
accept vlan tagged Layer-2 frames, ignoring tpid and tci. This might
happen when using the Pow
