[Linuxptp-users] instable mapping of ptp device to interface

[Marco D. (SIDN) <mar...@si...>]

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 and make the mapping 
between interface and ptp device more robust?

-- 
Marco