Established Sessions

[Chad.Shipman]

Not sure if SecureCRT supports this already or if it is even possiable.. But, I would swear that somewhere in SecureCRT 2 versions this was something of a default..

Lets say I have 3 SSH2 sessions up and i'm on a dialup connection.. The modem disconnects and redials right back and reestablishes a connection. There is a static IP address assigned on this dialup connection. Right now if that happens all my current sessions get disconnect and I have to go thru and reconnect all the sessions, etc.

Is there a way that SecureCRT can transparently reestablish or pickup and contiune the current session? the later option being preferable.

I may be lossing my mind.. but I would swear that older versions of SecureCRT had this ability.

[toloughlin]

Have you enabled the 'auto reconnect' option under Terminal ... in Session Settings or - Global Options - Default Settings?

[mekanik]

Originally Posted by Chad.Shipman

pickup and contiune the current session

Not really, as your talking about the protocol level of the actual transport which is TCP. This would encompass SecureCRT remembering the source TCP port (OS randomizes this using ephermal ports which are ones gt 1023) that the OS was using for the disconnected session (you already know the DST TCP port based on the configured session) along with TCP sequence numbers of the session, window size, and various other things. This would kinda fall under the realm of TCP hijacking (google it if your interested).

However if your are concerned about your session and would like the ability to resume it, then I would advise you to look at using "screen - screen manager with VT100/ANSI terminal emulation". Present on most Linux distros.

Originally Posted by Chad.Shipman

transparently reestablish

toloughlin has this nailed in his response.

[mdella]

I have to agree with mekanik.

Even if you have the same IP address on the reconnect, when you did the disconnect, if you were going through some sort of routing device, it lost the knowledge of the "other" ports extablished for the connection other than 22 (technicially it lost that to, but thats a well-known-port). As such, the connection basically can't be re-established in all cases. There are some devices that it will work, but thats not always the case and its hard to predict.

When using the "auto-reconnect" feature, be aware that any processes under your last login will timeout when that session falls apart on the server machine. Meaning that you might reconnect immediately, but your old session hasn't yet timed out and disconnected on the other end. Again, your milage will vary.

Last thing to note about the auto-reconnect... I used to use it, now I don't. Unfortunately I can't off the top of my head remember what was so frustrating about it, but I do remember having this topic discussed at length on the 5.0 release beta awhile ago. I also remember that the solution wasn't trivial nor could we come up with something reasonable. I'll try searching for previous discussions on this topic...

Marcos