Handle rdevcon tunnel timeouts more robustly #6
Description
Occasoinally a user will successfully connect to a device, which involves 2 connections,
- support@hub.example.com (forwarding tunnel to device ssh port)
- user@localhost (connection to device over tunnel, which may carry additional port forwards)
and the support connection times out on the server side, which kills the user connection. This can be diagnosed in the server logs as "Timeout, client not responding ..."
Possible fix:
- Re-connect the tunnel if/when it exits unexpectedly. Or at least flag it as not-connected, so that the next time the user tried to connect to the same device it works.