Client disconnects after 240s if server timeout is set to 300s

[neben]

I've set the server timeout to 300 seconds (--timeout 300), but now I'm seeing the clients always disconnect after 240s. This looks like the initial client timeout. IIUC the server should update the client timeout to twice the server timeout. Is this timeout info sent with the server keep-alive packet? And is the keep-alive packet sent timeout seconds after connection establishment? This then would explain that if I set the server timeout (300s) to a value higher than the initial timeout (240s), the client times out before ever receiving the timeout update.

If that is the case, wouldn't it make sense to transmit the server timeout value to the client upon connection establishment?

[NHAS]

Hm, this is a bit odd as the client does actually update its own timeout based on the servers timeout setting.

reverse_ssh/internal/client/client.go

Line 396 in 663d5d7

case "keepalive-rssh@golang.org":

				case "keepalive-rssh@golang.org":
					req.Reply(false, nil)
					timeout, err := strconv.Atoi(string(req.Payload))
					if err != nil {
						continue
					}

					realConn.Timeout = time.Duration(timeout*2) * time.Second

[neben]

If I set the timeout to 120, everything works fine. Is there anything I can do to help debug this?

[NHAS]

Hm, other than ensuring that the client is getting the right timeout value via the keepalive I cant really think of much.