RouterOS 6.49.10 uses kernel version 3.3.5, and support for 802.11ax started with 4.19, for example, so there’s no new hardware support.
Reading forum posts here and other topics suggest some bugs are product model specific.
This topic’s opening post is where MikroTik maintains the official announcement content.
The 7.11.1 portion has bridge fixed items but without product specific information.
Multiple forum topics report VLAN issues in 7.11.1 resolved by 7.11.2 upgrade.
MikroTik has an excellent position for capturing bug and product model correlations.
Close forum followers have a lesser but still good position to assemble the same over time.
I suggest MikroTik improve the formal announcement with product specific bug information as they learn it.
What’s also missing is the community perspective assembled into a single summary. As that perspective evolves follow up posts add value.
I fantasize a community member can share their consolidated perspective so the casual forum user has easier path with their product model.
TL;DR More bug to product model correlation information from any source is valuable to casual forum user.
AFAICT 7.11.2 release has calmed the waters. Avoiding 7.11.1 altogether is smart.
Who sees compelling reasons to make the 7.11 to 7.11.2 move?
Who sees compelling reasons to stay put at 7.11 version?
Compelling reason to upgrade: it will (would? could?) solve a problem.
Compelling reason to keep at 7.11: works for me.
My hEX is working just fine with 7.11. I will (maybe?) upgrade to 7.12, if the list of fixes/capabilities scratch my itch. Otherwise… meh
If ain’t broke, don’t fix it.
This is an anti-innovation mindset, usually smells of USSR and fascist regimes’ origin.
If it ain’t broke, improve it, re-architect if needed, re-test and re-validate. That’s how network engineering or any branch of engineering should be.
That’s a new low, even for you, DarkNATe.
Just had routing process hangup on HAP ax2 (25% CPU load, random route problems - some routes unreachable despite showing ok in route table) on 7.11.2. supout.rif also hangs at 15% and after 5 min i decided to reboot. (internet was needed asap 
Reboot helped, all works fine… for now.
This is third time it happened on HAP ax2 in two months. Never on ROSv6 (HEX, ac2, HAPac, etc.).
You had one job…
There will be no more development in v6, only patches for security problems.
Unfortunately the work force is split between (largely) developing new gimmicks for v7 and (much less) bringing v7 up to par with v6.
There is nothing we can do about that, development is likely most driven by demands from sales, then by “what the developers find interesting”, and only at the lowest priority by the boring work of going along a long checklist of open bugs and missing features…
Unfortunately this is not up to Mikrotik as TILE chips are not produced any more so CCR1xxx series is finished. Only way to move forward was to switch something else and ARM is the obvious choice…
and that is one of the wrongest assumptions ever made considering software development and upgrade-paths
I am seeing one issue here and I am not sure if this has occured on earlier releases on v7…
If you set static IP address on interface and then disable this interface then this address becomes inactive - at least on v6 it is like that. However this does not seem to be a case on 7.11.2 - even if address is set on physical interface which is not connected to any bridge. Only change is that connected dynamic route associated to this address and interface changes to “unreadhable” and “inactive” state. - but I can still ping this address…
Can this be considered as normal? I am not sure…
I mean, that pesky routing process, it must be THE job, don't you think? Pretty ironic, all other bells&whistles worked.
It takes years to gain reputation, and only days to lose it. ROSv7 can not be considered stable and suitable for production or remote areas. It is strictly SOHO now. A shame.
And i am a huge mikrotik fan, BTW. Some hope still remains.
rOS v7 IMO is able to be used in prod-environment. but it is not funciton-par with v6 when it comes to avery routing aspect - for sure.
just soho - i do not think so. but always depends on the setup and requirements
and for example backbone core routers (bgp, ospf, mpls) are not in the need of a container or wireguard option i’d reckon
7.11.2 finally fixed my Synology NAS’s ability to get an IP via DHCP on a SFP link. It worked on Ethernet, but not via fiber. Link looked fine, Mikrotik saw the DHCP requests, but the Synology never was able to acquire an IP. 7.11.1 had the same problem, but after updating to .2, the issue is resolved. This has been ongoing for at least a few 7.x releases so is quite nice to see corrected.
I do not see why 7.11.2 is not mention in the title. “and more” what is that. As it is now, its hard to see what is the latest release while visiting the forum. Please add 7.11.2 to the title of the tread.
I can’t upgrade my RB4011iGS+5HacQ2HnD to 7.11.1 and 7.11.2 I am stuck with 7.11 after reboot
Perhaps something like “v7.11.2 and older 7.11.x [stable] are released!” would make sense…
Let’s go a step further and remove 7.11.1 from the title and make clear it should be ignored.
OK. Upgrade done from package list
Lora is still broken.
After each reboot:
- Lora does not start automatically
- Server address is lost
- Antenna gain is lost
I can only pray for those user 100 km away from the LoRa station, who will need to go by foot, air or any means and fix this on site. Poor users.
Finally I feel quite happy to be able to reboot and start Lora by “hand”.