Xpra: Ticket #111: Keep ssh tunnel alive

SSH through a NAT will often stop working after some idle time. The "real" solution is to add ServerAliveInterval to ssh_config.

We should either pass this to the ssh tunnel command, or implement a heartbeat mechanism.

As it stands, my Xpra sessions die after about 2h of idle.

Wed, 18 Apr 2012 17:34:24 GMT - ahuillet:

-o ServerAliveInterval=300 on ssh commandline solves the problem. I propose adding that by default.

Thu, 19 Apr 2012 05:20:09 GMT - Antoine Martin: description changed

My understanding of ssh is that specifying -o OPTION overrides whatever is in the user's config file, so we probably don't want to do that. Some users may have a low alive-interval set, others not, it should really be up to them to set this value - and they can do that already, in a much more flexible way (per host, etc) via ~/.ssh/config

Maybe we should just enable pings in xpra with a reasonable delay (currently the pings are enabled only when displaying statistics and are sent every second)

Thu, 19 Apr 2012 07:19:07 GMT - Antoine Martin: owner, status changed

please close as 'wontfix' when the launcher is ready

Sun, 03 Jun 2012 17:42:28 GMT - Antoine Martin:

note: --enable-pings will send a ping every second, which will effectively keep the session alive, we may want to make the delay configurable and replace this with --ping-frequency=N

Wed, 04 Jul 2012 08:32:48 GMT - Antoine Martin: status changed; resolution set

r1007 enables pings unconditionally with a delay of 20 seconds. --enable-pings now only increases the frequency of pings to 1 per second.

This should detect dead connections.

Sat, 23 Jan 2021 04:45:51 GMT - migration script:

this ticket has been moved to: https://github.com/Xpra-org/xpra/issues/111