mirror of
https://github.com/outbackdingo/firezone.git
synced 2026-01-27 18:18:55 +00:00
7c8bbd550b
Currently, `tunnel_test` executes all actions within the same `Instant`, i.e. time is never advanced by itself. The difficulty with advancing time compared to other actions like sending packets is that all time-related actions "overlap". In other words, all timers within connlib advance at the same time. This makes it difficult to model the expected behaviour after a certain amount of time has passed as we'd effectively need to model all timers and their relation to particular actions (like resending of connection intents or STUN requests). Instead of only advancing time by itself, we can model some aspect of it by introducing latency on network messages. This allows us to define a range of an "acceptable" network latency within everything is expected to work. Whilst this doesn't cover all failure cases, it gives us a solid foundation of parameters within which we should not expect any operational problems.