On both MOS (Remote Shell) and Windows (PuTTY) I use a ssh session to connect to my router.

When using PuTTY to connect to the router and typing 'exit', the log tells me:

Code:

When using Remote Shell and typing 'exit' the log tells me:

Code:

Together with this behaviour I notice Remote Shell is 'stalled' for a few seconds after displaying 'Connection to 192.168.1.1 closed.' and then jumps to the entry I selected in the drop down menu.
Instead of typing 'exit' the session can also be closed by typing the following:

Code:

When doing it like this, the log entry is still the same, but the mentioned delay above is no longer present: it jumps to the entry selection right away.

This makes me wonder if the 'exit' procedure is handled correctly in Remote Shell.

Quote:
I always press enter once more to skip that "stalling". I don't know if there's something wrong, but at least that does the trick and Remote Shell doesn't need to abort the connection if (when) you don't have the patience to wait the delay there.

This is some shell incompatibility I never had the time to address... Doesn't have anything to do with the connection itself.

jPV, thanks, the additional enter does indeed skip the stalling.

Quote:

jacadcaps, are you referring to the stalling with your remark or the "Exited normally" vs. "Disconnect received" log entry?

The stalling.