With MASQUE over HTTP/3 being unstable on some networks, Aether often has to reconnect in order to maintain a usable tunnel.
I think it would be very useful to expose a few advanced settings that allow users to tune how tunnel health monitoring works, while keeping sensible defaults for normal users.
For example:
- Tunnel health check interval (how often the connection is verified in the background).
- Maximum consecutive failed health checks before the tunnel is considered dead.
- Reconnect delay before starting a new connection attempt.
- (Optional) Health check timeout for each validation attempt.
This would allow users on unstable networks to detect dead tunnels much sooner by reducing the health check interval, or make the checks less aggressive if they prefer.
For example:
Health check interval: 5 seconds (default: 20)
Consecutive failures before reconnect: 3 (default: 2)
Health check timeout: 5 seconds
The default values should continue to work well for most users, but advanced users could override them to better match the behavior of their network.
This would make Aether more adaptable to different network conditions without changing the default experience.
With MASQUE over HTTP/3 being unstable on some networks, Aether often has to reconnect in order to maintain a usable tunnel.
I think it would be very useful to expose a few advanced settings that allow users to tune how tunnel health monitoring works, while keeping sensible defaults for normal users.
For example:
This would allow users on unstable networks to detect dead tunnels much sooner by reducing the health check interval, or make the checks less aggressive if they prefer.
For example:
The default values should continue to work well for most users, but advanced users could override them to better match the behavior of their network.
This would make Aether more adaptable to different network conditions without changing the default experience.