5rc7 ssh still crashing

I have a rb1100 that still has the crashing ssh server issue.

I have to VPN into it then connect via telnet.

It’s a very heavily used router and I can’t reboot it all the time just to fix it.

Please, send the following information to support@mikrotik.com

  • support output file generated, when the problem is present;
  • output from ssh -v -l admin x.x.x.x

Hi, have same problem.
You have a memory leak?

dimedrol, could you provide us with the same information?

I wrote at support@mikrotik.com
Ticket#2010112266000421

dimedrol, we have replied to you in November and not received any feedback.

I think I have a similar issue. (5.0rc7 on a RB1100)

If I connect via SSH, and don’t logout, but rather “exit” the terminal app (Mac OSX) then i’m unable to login again via SSH - I get a connection refused.

/ip service set ssh disabled=yes
/ip service set ssh disabled=no

fixes the problem, and I can login again. I suspect that since the SSH connection didn’t exit cleanly, something gets hung.

Let me know if submitting a support outfile is of any use.

here’s the output from “ssh -v” in the connection refused state.

$ ssh rb1100 -v
OpenSSH_5.2p1, OpenSSL 0.9.8l 5 Nov 2009
debug1: Reading configuration data /Users/nnn/.ssh/config
debug1: Applying options for *
debug1: Reading configuration data /etc/ssh_config
debug1: auto-mux: Trying existing master
debug1: Control socket “/Users/nnn/.ssh/master-nnn@rb1100:22” does not exist
debug1: Connecting to rb1100 [192.168.13.102] port 22.
debug1: connect to address 192.168.13.102 port 22: Connection refused
ssh: connect to host rb1100 port 22: Connection refused

mdatic,
please contact support (support@mikrotik.com), we will give you pre-release package, where the problem is fixed (most likely).

I’ve also installed 5.0rc7 on two different devices this evening (RB1000 and RB1100), and although SSH was working at first, it is now failing for me too.

ssh: connect to host ___ port 22: Connection refused

Any ideas how I can fix this?

I can confirm that enabling and disabling ssh temporarily fixes the issue for me too.

to follow up on this:

i’ve tested the pre-release package, and so far, it seems to resolve the issues i’ve had before with SSH.

Mikrotik just sent me the pre-release 5.0rc8, and this seems to have also fixed the SSH issues for me on the 2 devices I was testing - an RB1000 and RB110.