Jamil

Notice the direct connection failed established originally failed and it moved to a Relayed connection. Since the Gateway reported the ICE timeout perhaps there is an issue on macOS or...

To add more, it looks like the connection went idle (!!) for an SSH session, causing a noticeable delay when I tried to use the SSH session again. ``` 2024-08-19T17:15:48.331053Z...

Yeah I can reliably reproduce `Connection is idle` for SSH sessions. I wonder if this will cause issues if the portal picks a different Gateway for resuming the SSH session...

If the TCP keepalive is 2 hours, and the NAT(s) treat TCP and UDP differently, it's entirely possible that behavior with Firezone enabled would be different than without. I.e. it...

> If the TCP keepalive is 2 hours, and the NAT(s) treat TCP and UDP differently, it's entirely possible that behavior with Firezone enabled would be different than without. I.e....

Seems to be fixed with the sticky Gateways fix.

User reports this is still an issue, reopening. Behavior is that connection lags / hangs after some time. I think the idle timeout might be less than SSH keepalive.

Customer reporting this still to be an issue. If we buffer the connection intent I _think_ that would solve it, assuming the underlying TCP connection is able to get re-established...

Wondering if it just makes sense to extend the idle timeout to something like 8 hours for desktop clients and gateways. That should solve this issue immediately and the power/network...

> > Wondering if it just makes sense to extend the idle timeout to something like 8 hours for desktop clients and gateways. That should solve this issue immediately and...