mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-03-21 20:41:57 +00:00
60bdbb39cb
At present, listening for DNS server change and network change events is handled in the GUI client. Upon an event, a message is sent to the tunnel service which then applies the new state to `connlib`. We can avoid some of this boilerplate by moving these listeners to the tunnel service as part of the handler. As a result, we get a few improvements: - We don't need to ignore these events if we don't have a session because the lifetime of these listeners is tied to the IPC handler on the service side. - We need fewer IPC messages - We can retry the connection directly from within the tunnel service in case we have no Internet at the time of startup - We can more easily model out the state machine of a connlib session in the tunnel service - On Linux, this means we no longer shell out to `resolvectl` from the GUI process, unifying access to the "resolvers" from the tunnel service - On Windows, we no longer need admin privileges on the GUI client for optimized network-change detection. This now happens in the Tunnel process which already runs as admin. Resolves: #9465
59 lines
1.8 KiB
Rust
59 lines
1.8 KiB
Rust
#![cfg_attr(test, allow(clippy::unwrap_used))]
|
|
|
|
pub mod http_health_check;
|
|
|
|
mod dns_control;
|
|
mod network_changes;
|
|
mod tun_device_manager;
|
|
|
|
#[cfg(target_os = "linux")]
|
|
pub mod linux;
|
|
|
|
#[cfg(target_os = "linux")]
|
|
pub use linux as platform;
|
|
|
|
#[cfg(target_os = "windows")]
|
|
pub mod windows;
|
|
|
|
#[cfg(target_os = "windows")]
|
|
pub use windows as platform;
|
|
|
|
#[cfg(target_os = "macos")]
|
|
pub mod macos;
|
|
|
|
#[cfg(target_os = "macos")]
|
|
pub use macos as platform;
|
|
|
|
pub mod device_id;
|
|
pub mod device_info;
|
|
pub mod known_dirs;
|
|
pub mod signals;
|
|
pub mod uptime;
|
|
|
|
pub const TOKEN_ENV_KEY: &str = "FIREZONE_TOKEN";
|
|
|
|
// wintun automatically append " Tunnel" to this
|
|
pub const TUNNEL_NAME: &str = "Firezone";
|
|
|
|
/// Bundle ID / App ID that the client uses to distinguish itself from other programs on the system
|
|
///
|
|
/// e.g. In ProgramData and AppData we use this to name our subdirectories for configs and data,
|
|
/// and Windows may use it to track things like the MSI installer, notification titles,
|
|
/// deep link registration, etc.
|
|
///
|
|
/// This should be identical to the `tauri.bundle.identifier` over in `tauri.conf.json`,
|
|
/// but sometimes I need to use this before Tauri has booted up, or in a place where
|
|
/// getting the Tauri app handle would be awkward.
|
|
///
|
|
/// Luckily this is also the AppUserModelId that Windows uses to label notifications,
|
|
/// so if your dev system has Firezone installed by MSI, the notifications will look right.
|
|
/// <https://learn.microsoft.com/en-us/windows/configuration/find-the-application-user-model-id-of-an-installed-app>
|
|
pub const BUNDLE_ID: &str = "dev.firezone.client";
|
|
|
|
/// Mark for Firezone sockets to prevent routing loops on Linux.
|
|
pub const FIREZONE_MARK: u32 = 0xfd002021;
|
|
|
|
pub use dns_control::{DnsControlMethod, DnsController};
|
|
pub use network_changes::{new_dns_notifier, new_network_notifier};
|
|
pub use tun_device_manager::TunDeviceManager;
|