trippy VS vopono

[3] https://github.com/fujiapple852/trippy/issues/1104

You are right that showing packet loss for intermediate hops is a frequent source of confusion.

Rather than leave it out, I added a status column which shows different statuses for intermediate hops (blue if the hop responds to less than 100% of probes and brown if it responds to 0%) vs the target hop (amber and red).

Where this breaks down is when dealing with ECMP for UDP & TCP tracing, as a given hop (ttl) may represent the target for a given round of tracing but not for the next. The mistake, imho, is to associate _any_ data with a hop (ttl) rather than the hop in the context of a tracing flow.

That is why Trippy had a number of features aimed at helping with ECMP, such as Paris and Dublin tracing, and the ability to filter tracing by unique flow id. I've covered these quite a bit in the 0.8.0 [0] and 0.9.0 [1] release notes if you want to know more.

[0] https://github.com/fujiapple852/trippy/releases/tag/0.8.0

Tracing flows: breakdown complex UDP/TCP ECMP traces into individual flows (i.e. common network path); render a chart of flows in GraphViz DOT format (example)

u/queiss_ the 0.8.0 release note has a section covering this, but the TL;DR is:

Vopono (https://github.com/jamesmcm/vopono):

"vopono is a tool to run applications through VPN tunnels via temporary network namespaces. This allows you to run only a handful of applications through different VPNs simultaneously, whilst keeping your main connection as normal.

vopono includes built-in killswitches for both Wireguard and OpenVPN."

I think for now on Linux you (still!) have to use external application to do the splitting. Such is vopono

I use vopono to manage it for me with Mullvad though.

you might want to check out vopono, i've gotten it working with firefox and its nice

https://github.com/jamesmcm/vopono

I highly recommend using something like vopono with this on Linux that runs only the target application (e.g. Transmission) in a network namespace in the VPN and only forwards the specified ports and only allows traffic via the VPN.

This is why I use vopono - you can run just the torrent client in the VPN on its own and the killswitch keeps it safe.

You can find the option in the settings of windows and android apps. Unfortunately, it's Still not available for Linux. As a workaround for Linux, you can use vopono, which has OpenVPN support for Proton. Or just manually add routing table entries :)

I wrote vopono, I use it all the time for quickly spinning up browsers through different VPNs for checking geographical restrictions, etc.