RB133C : Error downgrading from 3.28 to 2.9.51

RouterOS General
1

Hi,

I need RTS-CTS to work with some non-mikrotik CPE so I’m going to downgrade the AP (RB133) and others MT CPEs to 2.9.51 from 3.28.

now I have trouble downgrading the RB133C CPE:

jan/01/1970 01:00:18 system,error broken package routeros-rb500-2.9.51.npk

I have downloaded the file from several sites but after /system downgrade it reboots but still in 3.28 and this is the 1st line in the log.

routeros-rb500-2.9.51.npk - size=10879057 - md5sum = 85d40be22b271ada0973a881f84e1d2d

I have uploaded the npk file to the rb133c ftp root folder

Is there any reported issue doing this? Something related to the license file/format?

Thanks,
Antonio

2

First you need to downgrade to 3.23, then you with 3.23 installed you can downgrade to 2.9.51

Jorge

3

Hi,

thanks for your answer. I downgraded successfully to 3.23, then the old key has been requested. From this point I’m still unable to download to 2.9.51 ; the same error: broken package.

May be is required another staging step?

Regards,
Antonio

4

I have a RB133C with FW2.9 and had ROS4.2 installed. I have saved the 2.x license for this board.

I used the Netinstall on 4.2 and tried to load 2.9.43, but it failed (timeout).
I used the Netinstall on 4.2 and tried to load 3.30, worked.
Downgraded FW to 2.18
I used the Netinstall from 3.30 and tried to load 2.9.43, but it failed (timeout).
Loaded my old Key from 2.x
Tried to down grade, didnt take.
I used the Netinstall from 3.30 and tried to load 3.0rc1.
FTP 2.9.43
Downgraded to 2.9.43 successful.

I am sure you could simplify this but this worked for me.

5

I thought recent mikrotik OS support RTS-CTS no problem? 4.x, and 3.x with wireless-test package?

6

Hi,

finally it seems I get working the RTS-CTS with ROS 3.28 and wireless-test package with NS5 clients. The issue seems related with the “Default forward” which was active because I need STA to STA communication. I rewrote the network addressing scheme in order to route instead bridge the communication between STAs (the AP must route) and it is now working.

Thank you everybody for your assistant
Regards
Antonio