> -----Original Message----- > From: Jord Pool [mailto:jord.p...@outlook.com] > Sent: Monday, June 18, 2018 11:49 AM > To: Richard Cochran <richardcoch...@gmail.com> > Cc: Keller, Jacob E <jacob.e.kel...@intel.com>; Cliff Spradlin via > Linuxptp-users > <linuxptp-users@lists.sourceforge.net> > Subject: Re: [Linuxptp-users] Synchronisation > > Hi Richard, > > I must honestly admit that before trying this setup on my production systems I > had tested it and got it to work on a different environment (all Dockerized): > > System Clock (Client) —> Physical Hardware Clock (GM) —> Physical Hardware > Clock (Client) —> System Clock (Client) > > The test environment existed of two HP Z440 Workstation PC’s running Ubuntu > 16.04. On these two systems I have used the exact same Docker image of > linuxptp and the exact same commands for starting the synchronisation > processes dockerized (ptp4l and phc2sys). > > On the HP Z440 environment, the synchronisation processes worked (still work) > flawlessly. These machines also use the e1000e network driver (3.2.6-k version > and later the 3.4.0.2 (latest) version). The network adapter in the Z440’s is > the > Intel Ethernet Connection I218-LM. The HP Z440’s have only one NIC and > therefore (?) also just one PTP device; /dev/ptp0. > > So basically, I had got it working before (still running steady) in > containers on my > test environment. But thus not on the production systems with multiple NICs / > MAC addresses. > > Jord
I'm surprised you got this working in a containerized environment. How are you getting the network and ptp interfaces into the container? Thanks, Jake ------------------------------------------------------------------------------ Check out the vibrant tech community on one of the world's most engaging tech sites, Slashdot.org! http://sdm.link/slashdot _______________________________________________ Linuxptp-users mailing list Linuxptp-users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/linuxptp-users
