I have a hAP ac^2 with a factory software version 6.45.9. I need to downgrade it to version 6.45.8 that uses an older bootloader. Is that possible?
Officialy: NO. You can try but there are no promises taht it would work.
Okay, but how do I try? Netinstall didn’t work for me.
There are lots of reasons why netinstall might fail.
My preferred method might look more complicated on its face, but I think it’s more inherently reliable and, in the end, simpler.
I’m not telling you it will work for this particular case, but at least if it fails, you get a text log of what it tried and where in the process it failed. GUIs hide things.
AFAIK all official install modes (native inside running ROS, Netinstall) will check the “factory-software” (and “factory-firmware”) and will refuse to install software (and routerboot firmware) of lower version.
There are other, more “hacker way” possibilities to install older firmware, but are also highly prone to errors … and in this case, you may loose ROS license and/or brick device for good. These include using 3rd party hardware and software.
I wonder why you want to run so an ancient ROS version (6.45.
on your hAP ac2? Hacking disappropriated device (to put it mildly) is one use case that comes to my mind.
First question I asked myself too …
Because later bootloaders are not supported by OpenWRT, which I want to install on my device. I specifically chose this model because it was listed as fully supported by the latest OpenWRT.
Fair enough. But as I wrote, I’m affraid you can’t force to install routerboot with version lower than factory default using official Mikrotik methods.
I wonder, though, where does the information about routerboot version up to and including 6.45.8 come from? Official OpenWRT page warns against routerboot v7, not the earlier ones?
[edit] OK, I found the page saying routerboot 6.46 or newer isn’t OK … but that would mean that 6.45.9 should be fine?
Have impression that you are on wrong forum 
BTW … what means “fully supported”?
The problem is that OpenWRT sites don’t deal with problems like @OP has, they simply state “boot ROS and downgrade routerboot” without any details or warnings.
Here it says thay I need 6.45.8 or earlier.(
Hello,
I’ve come across this thread in a search for a solution to my issue.
I’ve recently purchased an RB4011iGS+ which has come with v7 rather than v6, like all my previous 4011’s.
I have a script that appears to be incompatible with v7.
I’ve not used v7 and not really a fan either as over the last couple of years I have seen lots of people experiencing issues - which I could well do without.
Some of the earlier posts, mentioned that there aren’t any official ways, can you share some links on unofficial resources that I could review?
I’m annoyed that there was no indication that v7 is now being pre-loaded, and I’d like to consider downgrade options before I think about trying to understand what is going to be involved if I decide to try and convert the script.
Thanks
VW
Give up. Convert the script.
Hello tangent,
The router supports v6, I have the exact same model running v6. Would that not mean that converting to v6 ought to be possible, if not fairly straight-forward?
But assuming that you’re suggestion is the best option (which I’m not convinced that it is); is there documentation that describes the differences between scripting in v6 and v7?
For example the following code generates an error when I try to import the script
:set pong [/ping $addr routing-table=$tableName count=$count]
The option
routing-table
doesn’t appear to exist for the ping command in v7
I believe that there is a given router design called by the name “RB4011” that supports v6, but I do not believe that every “RB4011” shipped by MikroTik supports v6. Until you have opened both up and compared that they have the exact same chips inside, you cannot say they are “the exact same.”
Two cars sit side-by-side in the parking lot, both called a “Camaro”. Are they “the exact same?” Well, they’re both red, and they both have four tires, a steering wheel, and run on gasoline. Trick is, one was made in 1973 and the other in 2023. They probably don’t take the same spark plugs.
Would that not mean that converting to v6 ought to be possible, if not fairly straight-forward?
My information comes from MikroTik, confirmed here in the forums by MikroTik employees every few months; do a search. As far as I can tell, your source is wishes and hopes.
is there documentation that describes the differences between scripting in v6 and v7?
There is, but it’s thin to the point of near-nonexistence. It is, alas, not the feature-by-feature conversion guide one should expect given a major breaking release.
(I say this as the author of documentation of that type, for my own work products.)
Worse, the current v7 /ping docs claim the routing-table option exists, but local testing shows that it does not.
You have grounds to report a bug.
Hello tangent,
Thanks for sharing the link and info re the script commands. That is helpful.
This update is a PITA.
I’m going to take this up with the reseller.
Regards,
VW
They’re unlikely to be able to produce v6-era RB4011s for you on demand, and if they can do it at all, they won’t be able to do it indefinitely into the future. Unless you’re leaving MikroTik entirely, a far more productive solution is to take the product as you find it and make it work.
Reporting the missing feature to MikroTik has a real chance of getting you the feature you want.
Weird, I think I’ve updated my hEX to the latest v6 (.49 something) and OpenWrt runs fine with it.
Surely with v7 not so much.
Wish MikroTik was more open source friendly.
I can see both sides on OpenWRT. Mikrotik could make bootloader more friendly to OpenWRT … but then it becomes a cycle: if the next driver doesn’t work/has issue…what to they do? e.g. say you got OpenWRT installed, then next Wi-Fi doesn’t work on some MT platform. Is that the best place for “tough luck bro we don’t support OpenWRT”…AFTER it’s installed 
.
You lost me right after “..it becomes a cycle:” .
Care to be more specific about that?