I ended up cloning the pping repo and running make locally. Installing was a few steps: 1. mkdir ~/src/libtins/build 2. cd ~/src/libtins/build 2. git clone https://github.com/mfontanini/libtins.git 3. make 4. sudo make install 5. cd ~/src 6. git clone https://github.com/pollere/pping.git 7. cd pping 8. make 9. ./pping The promise of this, as Kathleen Nichols points out, is that we can passively monitor production flows to get a novel sense of end to end performance per flow. I don't know of any other passive monitoring technique, beyond a port mirror + a whole gang of systems, that can provide this level of detail. Please enlighten me if I'm wrong. The only other passive monitoring mechanisms I'm aware of are SNMP polling, IPFIX/*Flow, and Streaming Telemetry Interface. None of those systems provide end to end flow performance details. The standard in-band active monitoring tools are good for determining node to node and full path metrics, but this provides a more complete picture of end to end performance beyond active y.1731/802.3ag/OAM probes. I'm a little surprised that I'm only learning about it now. Now to figure out how to make it show me something.. Jason On Thu, Feb 25, 2021 at 1:02 PM Jason Iannone wrote: > Thanks, I have tried moving around the src directory hierarchy to no > avail, including searching for explicit references to 'pping'. > > On Thu, Feb 25, 2021 at 11:52 AM Toke Høiland-Jørgensen > wrote: > >> Jason Iannone writes: >> >> > Hi, >> > >> > I'm new here. Can anyone help me get pping installed? As far as I can >> tell, >> > cmake, make, and make install all worked, but I don't have pping. Does >> > anyone with a bigger brain than mine have a suggestion? >> > >> > $ pping >> > -bash: pping: command not found >> >> My bet would be a $PATH issue. You could try just running it from the >> directory where you compiled it? I.e., substitute './pping' for 'pping' >> - or look at the output of 'make install' and see if you have the >> corresponding directory in your $PATH. >> >> -Toke >> >