#203 closed defect (invalid)
reconnect in winswitch menu needs two tries
Reported by: | pmarek | Owned by: | Antoine Martin |
---|---|---|---|
Priority: | minor | Milestone: | 0.12 |
Component: | Client | Keywords: | |
Cc: |
Description (last modified by )
I've got a remote tunnel, via
ssh -L 8022:host1:22
and connect to host2 via winswitch and the localhost:8022
tunnel.
Now, if I stop that outer SSH session (eg. via the "\n\n~." escape sequence) winswitch sees that the connection is severed, and displays "reconnect" in the servers menu.
But this doesn't work; on the first "reconnect" winswitch says that it couldn't connect, and only on the second try it really reconnects.
So it seems like there's some old state that is not being updated when a connection breaks.
Change History (6)
comment:1 Changed 13 years ago by
Description: | modified (diff) |
---|---|
Milestone: | → 0.12 |
Owner: | changed from Antoine Martin to Antoine Martin |
Status: | new → accepted |
comment:2 Changed 12 years ago by
comment:3 Changed 12 years ago by
Resolution: | → invalid |
---|---|
Status: | accepted → closed |
Correction: I only see this problem if I forget to re-start the ssh tunnel, if I do re-start it then it connects just fine.
comment:4 Changed 12 years ago by
Well, I don't use a manual SSH tunnel for this connection - winswitch/xpra should start it's own for that server.
And there shouldn't be an old connection being seen - having a weekend inbetween should be more than enough to get a timeout on any old connection ...
(BTW, the machine was powered on in the meantime, so any SSH/TCP tunnel should be gone by now).
comment:5 Changed 12 years ago by
This does not make sense:
Well, I don't use a manual SSH tunnel for this connection - winswitch/xpra should start it's own for that server.
And:
I've got a remote tunnel, via
ssh -L 8022:host1:22
Both cannot be true.
comment:6 Changed 12 years ago by
Ah sorry, the comment was mixed up with #218 (which references this ticket).
I'm using the same session on a server from the office (automatic SSH tunnel via winswitch) and from abroad (manual tunnel, inner automatic tunnel) - perhaps my problems are related to some connection mix-up inside winswitch (same server key, name, or whatever?)
Reproduced, here is the log sample I was looking for: