FujiApple

Copy of CI log for posterity: [11_sim-test (windows-stable).txt](https://github.com/fujiapple852/trippy/files/14526764/11_sim-test.windows-stable.txt)

What shall we do with this PR @c-git ?

Step (roughyl) to publish manually (for 0.10.0 on `Jammy`): ```shell docker run -it -v (pwd):/data ubuntu:jammy ``` ```shell apt update && apt install build-essential devscripts debhelper cargo wget cd /data...

Issues found when publishing 0.11.0. 1: The downloaded tarball doesn't have the `.1` suffix: ``` mv 0.10.0.tar.gz.1 trippy_0.10.0.orig.tar.gz ``` I just changed the command to remove it. 2: the `changelog`...

@unusualevent what you've said makes sense, and I don't have a good response. What @c-git said is right, Trippy is simply a tool that can help you solve problem X...

@unusualevent I've written some basic notes on different ways to use Trippy: https://github.com/fujiapple852/trippy?tab=readme-ov-file#what-are-the-recommended-settings-for-trippy Let me know what you think. I'll close this issue now, but feel free to add any...

@sthen thank you for [packaging](https://github.com/openbsd/ports/tree/master/net/trippy) trippy for openbsd. In #920 I've enabled building for OpenBSD in CI however it fails with: ``` error: component 'rust-std' for target 'x86_64-unknown-openbsd' is unavailable...

Thanks both. Any recommendations on the best way to enable automated builds in CI and on release?

GitHub actions can be connected to Tailscale: https://github.com/tailscale/github-action This would allow a cross-platform solution for case 2 above, with a Linux based TUN device in a remote machine made available...

@jmanteau could this be done _during_ normal tracing or would this need to be a separate mode of operation? I've only pondered this briefly but I _think_ it would need...