Hello,
last routerboards RB433AH I bought, were loaded with 3.24 software.
It is a very unstable software, and I would know if is it possible to downgrade to 3.13.
I already tried to do so and I get this output:
What is this? 3.24? 3.13? 3.18,5 ?
How can I downgrade to 3.13 ?
I cannot think that it is not possible to downgrade a new software to an old one. Could you please help me ?
Regards,
Alessio
You need to install via netinstall. I’m not sure, but I think it’s not possible to use 3.13 with RB433AH. Try to download 3.13 packages and use netinstall. If this don’t work use 3.27..
tell me what you mean by “unstable”? instead, upgrade to v3.27
Hello,
unstable means that if you delete a MAC address by the wireless Access List sometimes it blocks the board, you cannot reach it again and you must power off and power on it to have up the board again. In this situation the board is not reacheable neither by ethernet cable plugged in.
I have 10 RB433AHs working well with 3.13 software by a lot of months.
I bought other RB433AHs and they arrived already with 3.24 software on (why don’t put a previous stable release on new hardware instead of one sorted out randomly? )
Now I upgraded to 3.27 and with just one customer on the board is out after one day.
So the question is: can I downgrade from 3.24 / 3.27 to 3.13?
Yes or no? If yes how?
You can say: “change the board to see what happen”, but what I ask is if there is any possibilities to downgrade the software. After being sure about software I can make all the tests you’ll want.
Could you please answer?
Thanks,
Alessio
Downgrade won’t help. access list changes restart the AP, this is designed to be so. This is a classic example of when you have to ask before taking decision to blame software bugs. It’s not a bug - it’s normal!
Normis, access list changes restart the AP¿?¿?
When? I don’t see this in any version : ? If I have to add 10 MACs.. then 10 reboots? This don’t work on that way..
not reboots - the clients just are disconnected for a very short moment. they probably won’t even notice. this has been so in all versions.
if you change access list - clients reconnect.
This is ok..
Isn’t the same thing reboot the AP or reboot the wlans of the AP : P
Normis,
probably I’m not so clear when I try to explain my problem.
It is not the AP which is restarting, it is THE ROUTERBOARD which is hanged, blocked, not reachable, not pingable and so on !!
I don’t want to use other software I would know just one thing.
Now, if you can answer my question, please?
Is it possible to downgrade from 3.24 / 3.27 to 3.13?
Yes / No? If yes, how ?
Regards,
Alessio
You should be able to downgrade by uploading packages via ftp and then issuing command
/system package downgrade
if it is not working for some reason, then you can install older version with netinstall.
Dear mrz,
I tried with ftp to put the software on and then downgrade the software.
The result is what you can see in my first message.
It’s one day that I’m trying to make the downgrade by netinstall, putting the sofware, formating the nand, putting the bootloader and again the software without any success.
Now the board tell me that kernel was not found.
Could you please tell me if is it possible or if I’m loosing my time trying to make the downgrade?
Could you confirm: “yes you can make the downgrade and the procedure is…(the same as other software / another one and so on)”.
Big question: did you try to make a downgrade from 3.24 / 3.27 to 3.13 ?
Did you have success ?
Dear Normis, dear mrz,
After putting 3.13 with netistall the result was: kernel not found and the board never went up.
After putting 3.24 with netinstall the board went up soon.
So, probably what you don’t want to say is that with new software you changed the file system and so it is not possible to make a downgrade to the 3.13 software just because it used a different file system.
Because of this forum should be a technical help to who is using mikrotik software, could you please give a technical feedback about the changing of the file system with new software?
Just to don’t loose other time in trying to make downgrade and writing to don’t have answer, could you please tell on what version you changed the file system ?
Thanks,
Alessio
It should not be required to use Netinstall although that should work as well.
You should be able to downgrade from 3.24 to 3.13 just by dragging the file to the files area then open a “New Terminal” and issue the command “system package downgrade”.
We downgraded a bunch of RB411 boards from 3.22 to 3.13 last week and it worked fine that way.
Tom
You might also try slowing down the CPU frequency to 680MHz (the default) as you might be seeing hardware glitches causing your problems.
Tom
true, change the frequency back to 680MHz
I have some boards with problems working at 800 MHz, and some 411AH and 433AH working fine at 800Mhz… Try to use 680 to make the update and later use 800 if you can ; )
Hello,
Roc-noc, I tried to downgrade a RB411 from 3.22 to 3.13 and everything was working fine.
The software is the same of the RB433, but the result is completely different!
As suggested I took my RB433AH and I changed the CPU frequency from 800Mhz back to 680Mhz ftp-ing the file and pushing the downgrade button.
The result was the following:
I restore 3.24 software and I tried to make the downgrade (with CPU at 680Mhz) by netinstall and I get again: “Kernel not found”.
So I put again the 3.24 software on, to have the board working again, and I tried to put every single package of 3.13 by netinstall getting:
Was it changed the file system with new software, as the board said ?
Is it possible that no-one from mikrotik can say if is it possible to downgrade an RB433AH from 3.24 to 3.13 ??
Dear all,
I think this should be considered a very big bug, of course not for a test environment, but for a production environment.
Is someone working on it ?
Can you give a solution or a workaround to solve it ?
Thanks,
Alessio
What exactly is here the bug? which one?
Don’t use 800MHz and don’t downgrade. This is against Mikrotik recommendation anyway
I can easily downgrade to earlier versions. If it is a bug then it is v3.13 bug and already fixed in newer versions.