Dear all, about 6 weeks ago I moved most of my routers from 7.2.3 to 7.1.5, which was offered in the “long-term” channel. The the hope was to avoid crashed routers when updating in the (not so…) “stable” channel.
Now I get this. Can some kind soul explain what’s going on here?

That is correct, there NEVER HAS BEEN a version 7 Long Term software/firmware offering yet.
Furthermore the latest Stable Version is 7.4, if you want use vers7.
Well, 7.1.5 was definitely offered in the long-term channel in early June. This is why I installed it.
It was offered as long-term to make people with v7-only devices slightly less irritated. I’m sure some slightly more recent version (e.g. 7.2.3) will appear as long-term soon enough.
The fact that it hasnt been there for a long time indicates it wasnt really, and some overzealous webmaster probably got his peepee slapped no doubt for posting it.
OK, so versions showing up in the long-term channel might or might not be long-term. My bad, I guess I should have known this…
I just moved 4 non-critical routers 7.1.5 → 7.4. Suprisingly, they all survived it.
Good to hear! It was a one time-mistake 7.15, its not the norm.
Easy to tell because a long-term version stays on the board for a long time.
Dont know, dont care, use vers 7.4 for most stable version 7 functionality if you want to use ver7.
Breaking simple NAT, well, it’s not impossible, but quite unlikely. Too many people use that, so if it happened, there would be many unhappy users in release thread. You wouldn’t miss them. Now problem with something else that would result in behaviour that could seem as broken NAT, that’s more likely. What exactly it might be, it’s hard to tell. If you want to know, post all details (config, description) in new thread and maybe there will be something obvious.
Well, that url still gives version 7.1.5 for long-term:
https://upgrade.mikrotik.com/routeros/LATEST.7fix
Thought this is the url that RouterOS uses to check… Looks like it is not.
Does anybody know the correct url?
In general I think this is a bad decision.
I have a number of production devices, that run RouterOS 7.x already. I did test the functionality and was happy with it. However not receiving updates at the moment is bad news.
Those who install RouterOS 7.x should be aware, that some features are missing or incomplete. But a channel that does not provide “.0” releases would be nice anyway.
Well, going to stable then… Sooner or later.
Dont know what you are talking about??
I have a hex router on 7.24rC and when I put select upgrade on the router it finds 7.4 ???
Don’t know what you are talking about.
This thread is about long-term branch and I expressed my displeasure that there will be no 7.3.2 release for long-term.
Sorry too much bratworst today, or did someone stick you on a hook ;-PP
Why do you think there is a fricken rule that each version that comes out has to have a long term… dont make shit up!!
I have been using 6.48.6 long term for many moons, no such 6.49 copy. The world didnt come to end, Surprize.
I have migrated approx 3900 machines on the last weeks from… 6.46.8 (long-term) to 6.48.6 (long-term) after months of testing…
I have another 200 machines to finish all the migration from 6.46.8 / 6.47.10 to 6.48.6 (long-term)
And probably all devices are keeped to that version for years…
I’m forced to use v7 to one RB5009UG+S+ with 7.2.3 and I think I never update that device, as long as it works.
I use future v7 versions only when I’m forced to do that because the factory firmware is 7.x
i am also in 6.48.6 for most devices, recently testing 6.49.6 on some CRS 317 trying to resolve a specific issue about rate limiting (without success)
Well, v7 was so far simply a nightmare for customers and probably ruined quite a bit of Mikrotik’s reputation. Can you imagine: I ran dozens of v6 “stable” routers on auto-update for years, just once some wireless links broke due to changes in frequency allocations of regulatory domains. It’s not a critical installation, and downtime for a day is not a disaster, but I would never (!) risk this with v7. I hope the company management is aware of the disaster, investigated what went wrong when rolling out v7 and reacted accordingly.
It’s simple. RouterOS has different channels, where long-term should be the most stable of all. So if 7.1.5 was there for a while (which many would agree was premature) and someone installed it, it may be a little disappointing to see that MikroTik changed their mind and now there’s really no long-term version yet. First part of it is “so what the hell is the thing I installed?!”. Second worry can be about updates. Those are generally good, especially security ones you’d expect in long-term branch. So someone might fear that if there’s bug in this “fake” long-term version, there won’t be fix for it. But I wouldn’t worry about that too much. There’s not that many security bugs in the first place. And if some really bad one came up, MikroTik can easily release something in long-term channel. It’s not like there’s some rigorous process for that, they basically promote some version to long-term from time to time, after the base version wasn’t too disastrous for a while.
And eventually there will be “real” long-term version to replace 7.1.5.
It’s simple. RouterOS has different channels, where long-term should be the most stable of all. So if 7.1.5 was there for a while (which many would agree was premature) and someone installed it, it may be a little disappointing to see that MikroTik changed their mind and now there’s really no long-term version yet. First part of it is “so what the hell is the thing I installed?!”. Second worry can be about updates. Those are generally good, especially security ones you’d expect in long-term branch. So someone might fear that if there’s bug in this “fake” long-term version, there won’t be fix for it. But I wouldn’t worry about that too much. There’s not that many security bugs in the first place. And if some really bad one came up, MikroTik can easily release something in long-term channel. It’s not like there’s some rigorous process for that, they basically promote some version to long-term from time to time, after the base version wasn’t too disastrous for a while.
And eventually there will be “real” long-term version to replace 7.1.5.
Sob, you have such little faith in the software processes of MT LOL. Your theory (a very poor one) on how or if they have a process for deciding long term versions is the stuff of trashy tabloids.
Your lowing the quality of this thread! ;-PPPP