Hi,
Op 18-07-2022 om 11:28 schreef Miroslav Lichvar:
No, there is no option to disable management messages.
I managed to do it on the layer 3 level with iptables and am happy with
the result (want to do some further testing though).
L2 Should be doable in a similar fashion, but I don't nee
Hi,
Even though I understand that Linuxptp has not supported many SET and
CMD PMC-messages yet, I would still like know if there are ways to
disable PTP managment messages, in order to prevent (rogue) clients from
messing things up.
Is this possible?
--
Marco
OpenPGP_signature
Description
Hi,
Most of the time when I reboot this Linux server, ptp0 is connected to eno1:
ptp4l: [18.144] eno1 selected /dev/ptp0 as PTP clock
But sometimes this is ptp1, which is pretty annoying:
ptp4l: [18.745] eno1 selected /dev/ptp1 as PTP clock
Does anyone has a suggestion on how to prevent this
lar
servos and use the phc2sys to transfer the offset to the NTP daemon.
But that wouldn't work iwith software time stamping, would it?
Thanks.
--
Marco
-Original Message-----
From: Marco Davids (SIDN) via Linuxptp-users
Sent: Friday, July 8, 2022 11:04 PM
To: linuxptp-users@lists.
Hi,
So, I decided to configure 'clock_servo ntpshm' to use LinuxPTP as a
'refclock' for an NTP-daemon on a server with software time stamping.
And it appeared to worked well, until I looked a bit closer.
I noticed that with 'ntpshm' the servo state remains 's0' and the port
state remains UNC
Richard,
Op 15-03-2022 om 15:37 schreef Richard Cochran:
2. Run NTP client on the Linux host, and use phc2sys to sync PHC with
Linux system time. Might end up milliseconds offset from global
time due to NTP performance alone.
This one triggered a question;
I have a setup with an int
Hi Richard,
Op 25-02-2022 om 15:34 schreef Richard Cochran:
I created a unicast setup. It was an experiment to verify if I could make my
PTP-service more resilient against 'rogue' masters on the same VLAN that
(falsy) claim to be the best master.
A back actor on the LAN can easily spoof your
Update:
The bug seems fixed (there is a 3.1.1-3 now):
https://bugs.launchpad.net/ubuntu/+source/linuxptp/+bug/1959825
--
Marco
Op 11-02-22 om 08:15 schreef Marco Davids (SIDN) via Linuxptp-users:
This is a heads-up for those planning to move to Ubuntu 22.04.
There was a change in the
Hi,
I created a unicast setup. It was an experiment to verify if I could
make my PTP-service more resilient against 'rogue' masters on the same
VLAN that (falsy) claim to be the best master.
The setup works fine. However, I noticed that when the real (unicast)
master(s) become(s) unavailable
Hello,
This is a heads-up for those planning to move to Ubuntu 22.04.
There was a change in the LinuxPTP package that will prevent it to
coexist with other time daemons such as chrony, ntp and ntpsec, even
though this is a common use case.
The issue is mentioned here:
https://bugs.launchpad
Hello,
This is a heads-up for those planning to move to Ubuntu 22.04.
There was a change in the LinuxPTP package that will prevent it to
coexist with other time daemons such as chrony, ntp and ntpsec, even
though this is a common use case.
The issue is mentioned here:
https://bugs.launchpad
Thanks, this seems to do the trick!
Instead of 'slave Only 1', I tried 'clockClass 255' and that worked. But
it also seems to work with the default clockClass-setting.
Cheers,
--
Marco
Op 11-12-2021 om 03:22 schreef Richard Cochran:
I am working out a setup with two master clocks (one GM/l
Hi Dennis,
Op 10-12-21 om 13:21 schreef Dennis Hagarty (dehagart):
the profile can have a large influence on this.
What PTP profiles are you using and what transport (L2 or L3?)
What are the two BC's sending out in their announce message?
How is the OC connected to VLAN2? Is it using anothe
Hi there,
Here's a newcomers question.
I am working out a setup with two master clocks (one GM/leader, one
slave/follower, depending on what BMCA decides) and two boundary clocks
that both slave from the above setup and both provide time to the same
vlan on the other side. The BC's are slave
14 matches
Mail list logo
