@Buckeye, @skyhawk the next rc version will include additional fixes for correct BPDU processing on MT7621, MT7531 switches.
My reply to you was posting #116 and your posting was #115 and so a direct answer. Also I don’t like to quote because then the pages becomes a mess. My nightmares exist of reading topics, where two users are the only ones active and they quote each other in full in every posting…WHY???
You wrote in post 115 about that if Mikrotik opens an topic then they should also check that topic for what is going on. The link I gave allows them to do that and most likely they already use it. Makes work easier and they have not to browse though the pages to find their own started topics back.
What I have suggest?
http://forum.mikrotik.com/t/v7-11rc-is-released/168431/1
[quote=“, post:91, topic:168431”]
That topic is from 2019 when v7 was in beta. It is not beta anymore,. 4 years have passed. It is stable
[/quote]@Normis…
Is time to change the section name, is ridiculous:RouterOS beta and rc versions
Please report all issues with RouterOS beta / rc pre-release versions.IS time to create a section about "> RouterOS 7> " and leave “RouterOS beta and rc versions” just for… RouterOS beta and rc versions!!!
The real rule in this forum is that there should be no rules.
More moderators to moderate what?
They keep allowing topics like “no internet”, “help me”, “question”. Seriously?
Most of the posts are garbage and spam, and by spam I mean opening other topics to post the same thing for the umpteenth time.
Moderators should delete those bulls–t, and direct people to ask in the right section and for topics that have the same problem.
For example, there are dozens of posts on DDNS of various kinds, which do the same thing, one gets lost even in the search, and I believe they open up new sections.
For me at this point the whole forum should be locked, moving it to a subsection and reopening the relevant and more detailed sections from the beginning,
for example scripting, api, vlan, ipsec, certificates, wireguard, BGP, lte, lora, etc.
all more detailed subsections, instead of generic things,
and a beta/rc section all for it’s own.
Even the discourse of quotations, hundreds of useless posts are produced in the search,
because the search also searches in the quoted text, making a mess that disorients.
The problem is not that MikroTik do not read the topics, they do. See the above reply by normis: apparently he is reading the topic.
The problem is that they ignore “possible bug reports” (and also “possible suggestions for improvement”) and wait until they are reported on the support system. But as users cannot see what others report on the support system, that means double work for them.
What we need is a support system where others can also see and add information to what is being reported, like Bugzilla or Github.
That would of course not cover all support needs, but at least it would cover the reporting of plainly visible issues that multiple people do experience.
When the release thread commentary switches to process…that always seems to be good indicator of a release…
Only thing missing is xMIPSx support for BTH…
Hi!
Something changed from beta firmware(s) (at least 7.11beta2) to RC in relation to OpenVPN - RC version has problems with more than 170 OVPN connections …
I reverted to 7.11beta2 and everything works great.
Luka
Have you open the support ticket sending the supout.rif after and before (or better before, and after)?
If you limit yourself to writing it here on the forum and that’s it,
without opening a separate topic where you give an explanation worthy of that name, and an export of your configuration,
what you write is useless.
Hi, I described it here (http://forum.mikrotik.com/t/v7-10-7-10-1-and-more-stable-are-released/167423/33) and reported to support (SUP-122789). Sadly, no solution yet. They asked to send supout.rif by the way. I think it would be helpful if you could make another report with such a file attached if you don’t mind.
Good point ... It's a ROS 7.11rc2 topic ... please do not flood it with moderation complains. Should I delete or moderate your post?
That is the closest /latest topic to discuss moderation: Forum moderation volunteers
I had the same problem. The connections hang, the interface drops and the addresses in ip/address turn red. Openvpn port 1194 is blocked and only normalizes when I restart the router. I went back to 7.11beta2.
What’s new in 7.11rc3 (2023-Aug-09 17:41):
*) certificate - improved CRL download retry handling;
*) ipsec - fixed public key export (introduced in v7.10);
*) ipsec - fixed signature authentication using secp521r1 certificate (introduced in v7.10);
*) lte - fixed R11e-LTE, R11e-LTE6 legacy 2G/3G RAT mode selection;
*) sms - increased wait time for modem startup;
*) switch - fixed BPDU packet processing on MT7621, MT7531 with HW offloaded vlan-filtering;
*) switch - improved multicast packet forwarding on MT7621;
Out of curiosity, I’ve had a problem (as others have had) with MLAG. The problem was introduced in 7.7, and just prior to 7.10 being released, it was finally acknowledge as a problem with a solution pending. I have not seen in the release notes where this was fixed, and even though my support tickets are “closed” the last communication was (SUP-116568):
“We have managed to reproduce the issue locally in our labs and look forward to fixing it on upcoming RouterOS versions, unfortunately, I cannot provide a release date now.”
Has this been fixed yet or is it still pending? I really need this to be fixed so I can complete an installation.
If it is not mentioned in the release notes, it’s not yet fixed.
I think the problem here with MT they should finished one thing at a time before jumping on to another task at hand and also they should published the roadmap at least people know what to expect or not, otherwise this will be a recurring theme MT will surely delete this post anytime soon just like what they did before.
Many people, myself included, have had similar thoughts about Mikrotik software releases and other companies’ releases as well. Of course this is a naive outlook which is not well matched with reality. If you just think about it a little while you realize it obviously makes no sense to work on one thing at a time. With a team of people you have multiple projects occurring simultaneously simply because you have multiple developers of different levels and skill sets and many things to get done.
In addition to the obvious stuff, there are less obvious factors involved. Sometimes adding additional resources to a particular task can actually slow things down. More developers working on bug x doesn’t necessarily mean bug x gets fixed quicker or more correctly. It’s very difficult to manage large software projects and many fail from poor management. I think MikroTik does a reasonable job overall. I’m not suggesting they couldn’t do better, but I am suggesting that without direct knowledge of all their resources, planning, and management of those resources we certainly can’t be expected to know better then they do how they should be allocated.
Probably the best thing we can do is put in our feature requests and bug reports as clearly and concisely as possible and just be persistent in letting them know what we need and why. The more people that do that the easier it will be for MT to figure out priorities and resolve issues. Keeping the SNR down will be helpful for everyone.
Well…The problem with MLAG is directly related to bridging and spanning-tree for which there have been a number of fixes in the past couple of releases. I’m not sure if any of those posted fixes also fix the MLAG issues or not. Just checking. Would be nice if there were some sort of actual bug tracking number for the MLAG issue that I could search (like other software/equipment manufacturers).
But hey…What do I know? I just use this stuff.
as they always say, if it’s not mentioned in the changelog therefore they won’t fix it
It is quite clear that fixes go into RouterOS without mention in the changelog.
If only because some thing suddenly appear “broken” without any mentioned change in that function or anything related to it.
The changelog is only a recap of the most important changes in that version, otherwise it would be too long.
(I have proposed possible improvements of the whole changelog publication system)
Of course we have no idea about how many people are actually working in MikroTik software development, and how specialized they are on certain areas of the system.
In total the company seems to have about 350 employees, but many of those will work on hardware development, production, shipping, accounting, support, sales, management etc.
So how many are active as developers we do not know (AFAIK there are no published figures about that).
What IS quite apparent is that there have been critical shortages in some areas, that required new hiring or re-training. E.g. the whole “routing protocols in v7” department has experienced at least a year of no progress, before it restarted a couple of months ago.
At the moment they appear to be restaffed, but still it surprises me that rather than finishing the job on the existing problems that have been caused by the routing revamp in v7, they already start on new things like IS-IS. This appears to be a single skill set.