General list for discussing Bufferbloat
 help / color / mirror / Atom feed
From: Jason Iannone <jason.iannone@gmail.com>
To: "Toke Høiland-Jørgensen" <toke@toke.dk>
Cc: bloat <bloat@lists.bufferbloat.net>
Subject: Re: [Bloat] Trouble Installing PPing in MacOS
Date: Fri, 26 Feb 2021 19:36:04 -0500	[thread overview]
Message-ID: <CAGL1wDRAbtD72Sb9fu9R4xT4gnMq6MHNyCN0BOiVCofR4v73qg@mail.gmail.com> (raw)
In-Reply-To: <87blc6zghv.fsf@toke.dk>

[-- Attachment #1: Type: text/plain, Size: 1656 bytes --]

Beyond getting acquainted with a new dataset? I'm a transit network that
supports, among other traffic types, science flows. I think new monitoring
methods can help identify targets for intervention.

On Fri, Feb 26, 2021, 4:06 PM Toke Høiland-Jørgensen <toke@toke.dk> wrote:

> TJason Iannone <jason.iannone@gmail.com> writes:
>
> > 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.
>
> What's your use case? :)
>
> -Toke
>

[-- Attachment #2: Type: text/html, Size: 2412 bytes --]

  reply	other threads:[~2021-02-27  0:36 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-25 15:58 Jason Iannone
2021-02-25 16:52 ` Toke Høiland-Jørgensen
2021-02-25 18:02   ` Jason Iannone
2021-02-26 12:56     ` Jason Iannone
2021-02-26 21:06       ` Toke Høiland-Jørgensen
2021-02-27  0:36         ` Jason Iannone [this message]
2021-02-27  2:22           ` [Bloat] offtopic to: " David Collier-Brown
2021-02-27 16:00           ` [Bloat] " Toke Høiland-Jørgensen
2021-02-27 16:31             ` Jason Iannone
2021-02-27 16:49               ` Toke Høiland-Jørgensen
2021-02-26 22:16       ` Kathleen Nichols
2021-02-27  1:36         ` Jason Iannone

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://lists.bufferbloat.net/postorius/lists/bloat.lists.bufferbloat.net/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=CAGL1wDRAbtD72Sb9fu9R4xT4gnMq6MHNyCN0BOiVCofR4v73qg@mail.gmail.com \
    --to=jason.iannone@gmail.com \
    --cc=bloat@lists.bufferbloat.net \
    --cc=toke@toke.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox