Hi,

I was running 3.25 and downgraded to 3.24. I need to downgrade to 3.13. It's not possible?

via netinstall I get:
WARNING: omitting package system-3.13: it does not support current file system

What is wrong with 3.26? - Disable DNS caching and absolutely no problems

dns cache is not working in 3.26?

memory leak, all other things are in tact.

I need to downgrade to 3.13. It's not possible?

your RB450G doesn't support old versions, support for it was added only later

updated to 3.26. Thanks.

guys,
since i tried v 3.20 and later till 3.25 for RB450 it looks like Torch in those versions is absolutely crazy.
Looks like it put interface in promiscuous mode so it's listening all the shit from network.
My boss liked to use this tool since we started to use MT with ROS v 3.10 .
How can I downgrade one RB450 from 3.25 to 3.13?
He is annoying me a lot about this #$%ng Torch, so now I'm sick of it and I want to give him back what he wants.

p.s. ..v 3.10 has some bug so we can not keep it anymore.

hi,

rb450G isn't compatible with 3.13.

I don't know if you can use RB450 with 3.13, but sure yes..

You can use netinstall to downgrade. Or put the 3.13 NPK in the /files and go to system package downgrade.

Or put the 3.13 NPK in the /files and go to system package downgrade.

thank you.
It helped.

Now there is the question to see if Torch of v 3.13 is the same like it was in 3.10 ...
I can not understand why it's behaviour was changed? Or it's a bug?

I don't know why, but in new releases are always things that don't work but work perfect in older releases.. I think in 3.13 torch work ok.

I don't know why, but in new releases are always things that don't work but work perfect in older releases.. I think in 3.13 torch work ok.

it's funny that you will be saying the same thing about v3.27 after some time maybe there is nothing wrong, just how you look at things.

Well Normis, I can see his point. Version v.3.27 is not there because we all look different at things nowadays. Its just a result of patch after patch.
That's why some Pro users with big networks always are a couple of upgrades behind. Errors in the new upgrade will surface after some time. Look at 3.25 and 3.26.

But then again, is this not the normal behaviour in IT land? We are getting patches and updates of Windows on a weekly base and each so many years a complete new Os.
Linux is not so much different and whatever consumer hardware I buy, upgrades are part of live..

So although Ibersystem is completely right in his remark and it frustrates a lot of us, I also think we have to accept it as a normal process to get a good system like MT-ROS is..

Rudy

Yes, always make sure to upgrade some non-important router. It's great if you have some test router where you can check if it works, and if there aren't any major problems.

Mikrotik has a simulation network consisting of different kinds of hardware, where a multitude of tests is run, to check all functions, before the version is then put on our own internal network. If there are no further problems, we give the version to volunteer testers, who urgently need some issue to be fixed. If they confirm the fix, we release it to the web.

And even then, there can be some things Mikrotik has missed. Therefore, upgrade test systems, wait for other reports, and only then upgrade your important routers.