mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-01-27 18:18:55 +00:00
dabe493e9e
Currently, we always emit a connection intent whenever we see a DNS query for a domain of one of our DNS resources. However, especially for wildcard DNS resources, we are very likely already connected to the corresponding gateway. In that case, sending a connection intent triggers another handshake with the portal only to learn that - surprise - we should reuse a connection that we already have to that gateway. We can short-circuit this by checking if we are already connected to the gateway for this resource and directly requested access for the domain name in question. We reuse the same event here as we do for refreshing DNS resources. At a later stage, we should rename this to something else to make this clearer. Co-authored-by: Gabi <gabrielalejandro7@gmail.com>
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