rabito
Cc: linuxptp-users@lists.sourceforge.net
Subject: Re: [Linuxptp-users] recvmsg failed error on multiple slave systems
Another brief update here,
I'm still waiting to hear back from the clock manufacturer. In the meantime, I
did update the clock's on-board software from 1.3.1d to 1.3.1k,
e VersaSync has been via
the web UI.
Thanks,
Adam
From: Essling, Adam M [adam.essl...@udri.udayton.edu]
Sent: Wednesday, September 11, 2019 2:49 PM
To: David Mirabito
Cc: linuxptp-users@lists.sourceforge.net
Subject: Re: [Linuxptp-users] recvmsg failed error on mu
ember 04, 2019 4:47 PM
To: Essling, Adam M
Cc: Richard Cochran; linuxptp-users@lists.sourceforge.net
Subject: Re: [Linuxptp-users] recvmsg failed error on multiple slave systems
Hey Adam,
That's interesting, if the patch turned "FAULTY" into "bad message" logs then
it fee
- anywhere anywhere
>
> Chain DOCKER-ISOLATION-STAGE-2 (2 references)
> target prot opt source destination
> DROP all -- anywhere anywhere
> DROP all -- anywhere anywhere
> RETURN all -- anywhere
___
From: Richard Cochran [richardcoch...@gmail.com]
Sent: Tuesday, September 03, 2019 11:08 PM
To: Essling, Adam M
Cc: linuxptp-users@lists.sourceforge.net
Subject: Re: [Linuxptp-users] recvmsg failed error on multiple slave systems
On Tue, Sep 03, 2019 at 09:00:08PM +, Essling, Ada
On Tue, Sep 03, 2019 at 09:00:08PM +, Essling, Adam M wrote:
> Hi, I'm trying to use ptp4l with [system1] and [system2] as slaves with a
> Spectracom Versasync PTP clock as master. Both slave systems are running
> Ubuntu 16.04 with ptp4l v1.8. I am using the default ptp4l.conf file. When I
>
This smells a bit like the same symptoms as
https://github.com/richardcochran/linuxptp/commit/6b61ba29c78e26109426429c6d6b354f6e4443cd
:
"Avoid fault when receiving zero length packets"
You could confirm with a tcpdump on UDP ports 320 and 319, keeping an eye
for otherwise well-formed UDP messages
Hi, I'm trying to use ptp4l with [system1] and [system2] as slaves with a
Spectracom Versasync PTP clock as master. Both slave systems are running Ubuntu
16.04 with ptp4l v1.8. I am using the default ptp4l.conf file. When I run the
following command (on system1):
sudo ptp4l -i eth0 -f /etc/linu
