RB493G: After upgrade to 5.21 SSH doesn't work anymore

RouterOS General
1

Hi,

on my RB493G I did an upgrade from version 5.xx to version 5.21 via WinBox using the “All packages” package. After the reboot, the SSH service refuse to work.
When I login to the box via WinBox right after the reboot, “IP > Services” shows a red “I” in front of the SSH line. When trying to activate it, a message pops up saying

“Couldn’t change IP Service - feature is not implemented (2)”

After that, the service remains greyed out and another attempt to activate it ends with the same result. So I did a reset of the box via

System > Reset Configuration (default options)

After the reboot there was the same result. SSH still refuses to work. Anybody has an idea what is going on here or how to fix this?

Btw.:
I found a hint in a another thread from 2010 that this may be related with corrupted keys (see http://forum.mikrotik.com/t/cant-enable-ssh-service/55007/1). Is this maybe related?

Routerboard firmware is at version 2.41.

Cheers and thanks in advance
Markus

2

if it is the-corrupted-keys problem then you can do ‘/ip ssh regenerate-host-key’ and reset the router keys.

Also, by chance, check if security package is enabled (just in case it is not)

3

Thanks for the quick reply.

Well, “IP > SSH” is not available from the menu thus I can’t regenerate or reset keys.
The security package is enabled, visible through “System > Packages”.

I forgot to mention that I don’t have access to the console at all, that means, when in WinBox, the button “New Terminal” opens a window but this remains static and empty. Starting the feature from WebFig displays a pop-up window saying “error undefined” in red letters.

Any other idea? :slight_smile:

Cheers

4

So, after updating to version 5.22, the box is bricked.

No response on any port (ethernet, serial, USB), no flashing LED on the ethernet ports. Resetting the box via short-circuiting (http://wiki.mikrotik.com/wiki/Manual:Password_reset) makes the ethernet LEDs flashing again, but still no response on ether1 (trying 192.168.88.1/24).

Any idea? :smiley: