We have some hosts that run ptp4l on interface net3.  Then net8 (a
completely different physical port, though the same network card) goes up
and down during a fault.  Then ptp4l never bothers to reopen the UDP socket
again forevermore. (lsof never shows the UDP binding ever again)  It seems
odd that running ptp on net3 would have any dependency on an unrelated
physical port.  Do you have any bright ideas on how to work around?  Seems
like perhaps a bug.  Note that if net8 does not go up and down, that ptp4l
automatically recovers from the fault on net3 within a very short period of
time.

Only nonstandard options on Centos7.9:

# cat /etc/sysconfig/ptp4l
OPTIONS="-s -i net3 -P -f /etc/ptp4l.conf"

# cat /etc/ptp4l.conf|grep -i domain
domainNumber            6
_______________________________________________
Linuxptp-users mailing list
Linuxptp-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/linuxptp-users

Reply via email to