mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-01-27 18:18:55 +00:00
f2b6c205c2
Currently, `snownet` still supports this notion of "reconnecting" which is a mix between resetting some state but keeping other. In particular, we currently retain the `StunBinding` and `Allocation` state. This used to be important because allocations are bound to the 3-tuple of the client and thus needed to be kept around in case we weren't actually roaming. We always rebind the the local UDP sockets upon reconnecting and thus the 3-tuple always changes anyway. In addition, we always reconnect to the portal, meaning we receive another `init` message and thus can actually completely clear the `Node`'s state. This PR does that an in the process, rebrands `reconnect` as `reset` which now makes more sense. Related: #5619.
Rust development guide
Firezone uses Rust for all data plane components. This directory contains the Linux and Windows clients, and low-level networking implementations related to STUN/TURN.
We target the last stable release of Rust using rust-toolchain.toml.
If you are using rustup, that is automatically handled for you.
Otherwise, ensure you have the latest stable version of Rust installed.
Reading Client logs
The Client logs are written as JSONL for machine-readability.
To make them more human-friendly, pipe them through jq like this:
cd path/to/logs # e.g. `$HOME/.cache/dev.firezone.client/data/logs` on Linux
cat *.log | jq -r '"\(.time) \(.severity) \(.message)"'
Resulting in, e.g.
2024-04-01T18:25:47.237661392Z INFO started log
2024-04-01T18:25:47.238193266Z INFO GIT_VERSION = 1.0.0-pre.11-35-gcc0d43531
2024-04-01T18:25:48.295243016Z INFO No token / actor_name on disk, starting in signed-out state
2024-04-01T18:25:48.295360641Z INFO null