Well it's at least clear what MT is meaning with 'long-term' now... Really not so long-term apparently. Binning 6.40.xxx is a big mistake, since it is simply not in the interest of the business customers of MT, only in the interest of the enthusiasts. It has been discussed at length here before 'why...

You called 6.40.X versions as "Long-Term". How long-term it will be? One year? 2 years ? +1 Is it just a name change, or a serious strategy change? Please MT, portrait clearly what is in store for the future with regards to config-stability. Official info about this would be greatly appre...

Almost every major version they have released lately has brought about config changes that, unless they are auto-converted by the upgrade process, prevents an older config from being loaded into a newer version router. Even simple changes like moving to interface lists for the MAC server / IP neigh...

I agree with most of the points being made here, at least in a technical sense. Sequentially: 1) First MT needs to add all current options into the bridge-menu, without disabling them in the switch-menu. 2) After "1", as 2nd step a proper (auto)conversion must be created (although there ca...

I do not personally know what MikroTik's plans are in this regard, but I would caution against reading too much into the "bugfix-only" being renamed "long-term" as having anything to do with a long term continuation of the 6.40.x software, unless they have made a specific announ...

Why do you need master ports back? Hi MduCharme, I realize that it might be somewhat unclear why I take masterports and switch-config as a candidate in one legacy package. In the past in the early public testing of the new bridge model (I believe it was 6.37rc or 6.38rc) it was stated that, because...

Why do you need master ports back? Hi, It is not so much that I do not like the efforts of MT to make it easier for everyone. And by now, I know how to reconfigure it too... I'm all for having a proper 1-fits-all easy bridge config, although I personally never felt the old switch config was to hard...

bugfix-only/long-term named 'stable' instead? I have a theory that they may want to support 6.40.x line (the last release branch before the bridge overhaul) for an extended period of time, hence the "long-term". This does not justify, however, renaming "current" to "stable&...

eddieb: I agree that this may not be the most appropriate place, as it is not a 6.42.4 specific issue. But if you make a separate thread for it, apparently MT and community don't care to look to serious fundamental issues. This also have been proven on this forum time and time again. General threads...

mducharme: You are just emphasizing my point now... apparently MT is now more involved in dumbing down Ros than providing a technically better and stable OS. By removing code supporting previous features normal upgrade process is blocked, and therefore continuity is lost. Therefore RB also LOST its ...

This is pertinent NOT true! arm models with 6.41 are not working properly with PPPoE. I wasn't saying anything about other issues with 6.41. My reply was only regarding the VLAN config in the bridge menu, which was changed in 6.41, and nowhere did I say that 6.41 was bug free in all regards. I have...

Dear forum, I since long use RB as my preferred device, and thus far was able to figure everything out without actually posting questions here myself. I could either work it out, or it was already mentioned at the MT wiki, forum or elsewhere "googleable". Thank you all for this! But recent...