FujiApple

@marcb a few (vaguely defined and unplanned) long term ideas I have for Trippy are: - Support for operating at layer 2/3 for all protocols (via TAP/TUN and/or eBPF) -...

> I really like the idea of it emitting events, it keeps it very open for how the events are handled. And makes alternate options for handling the events a...

To add some more detail; trippy currently uses [tracing](https://github.com/tokio-rs/tracing) to emit logs and spans. You can enable trace logging (`-v`), output it in `json` format (`--log-format json`) and use `silent`...

Thanks for the details @ShaguarWKL and congratulations on the IPOs and exit! > False Positives. Ping Plotter was notorious for it Can you give some examples of the types of...

May be of interest: https://cloudevents.io/

@almereyda Linux provides (at least) three mechanisms for an _unprivileged_ (non-root) user to run a ping/traceroute. The first way is what @c-git is referring to; where the `CAP_NET_RAW` capability can...

It is not entirely clear if Dublin-style NAT detection is _supposed_ to work or whether it is an artefact of a device which does not conform to specification. Specifically, NAT...