pub const TUN_STARTUP_TIMEOUT: Duration;Expand description
How long to wait for the TUN readiness signal (device creation + stack
init + child-task setup) before treating the listener as failed to
start. Shared between the startup path (meow-app/src/main.rs) and the
config-reload path (routes.rs::spawn_tun_from_raw) so the two don’t
drift.
Setup failures return immediately via TunReady::Failed — this bound
only covers genuine hangs and legitimately slow startups: wintun adapter
creation, first-time driver install, and the PowerShell DNS backup/set
can together take minutes on slow Windows machines (5 s and 30 s both
proved too aggressive there; 300 s measured comfortable in practice).
Trade-off to be aware of: the config-reload path awaits this while
holding config_mutation_lock, so a hung startup blocks every
config-mutation API call for the full duration.