mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-01-27 18:18:55 +00:00
e0e9e078a0
In order to handle DNS resources, connlib intercepts all DNS requests on the system once it has started up. The DNS queries are then forwarded to the original DNS resolver in case the query isn't for one of the configured DNS resources _except_ if the configured DNS resovler is also a CIDR resource. In that case, the DNS query will be tunneled to a gateway and forwarded to the DNS resolver from there. Exactly this configuration results in a dead-lock when roaming networks. To make roaming more reliable, we now drop all connections when detecting a network change (see #5308). As a result, DNS queries cannot be tunneled right away. This isn't usually a problem: We just send a connection intent to the portal to connect to the gateway. Upon a network change, we also reconnect the websocket to the portal which also requires to resolve the domain name. Connlib's DNS resolver is still active at the point and thus, we end up deadlocking ourselves because the DNS query to resolve the portal's domain is waiting for a connection to a gateway that can only be established once we are connected to the portal. To prevent this, we extend connlib with a "known hosts" feature. These are DNS records that are defined statically for the lifetime of a connlib session and can thus always be resolved, regardless of the connection state with the portal or the gateways. We populate these records with the portal's API, allowing the reconnect to work without having connected gateways. --------- Co-authored-by: Thomas Eizinger <thomas@eizinger.io>
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