Not just errors - some features and solution explicitly rely on xSTP to be able to work properly - like topology solutions with path redundancies and MLAG.
These clearly don’t appear in mindset of @wfburton …
STP is not as innocent as you may think. I also disable it where it isn’t required.
Remember it takes some time for a port to “come up” with STP (it can be more or less depending on configuration) and this often conflicts with devices that have automatic detection of a valid network. WiFi clients may disconnect when they cannot quickly establish DHCP and internet connectivity.
Recently I had enabled RSTP on my home router and 2nd AP, and also on a small Netgear switch, but it never recognized the Netgear switch as part of the network, and when I recently encountered problems I disabled it again.
But indeed, at work where MLAG is in use, I have RSTP enabled.
I think that STP dilemma (to have it or not to have it) is somehow similar to the dilemma about default firewall action (allow everything not forbidden or block everything not allowed). In certain cases the answer is clear, mostly it’s murky, but in principle it’s good to have STP (or rather RSTP) unless one determines it makes problems. You named one (slow port unblocking), there may be other, like the bug with station-pseudobridge, but normally it’s better to have it enabled as it normally doesn’t interfere with traffic. And due to this I support MT’s decision to have it enabled by default … because problems are always easier to spot than the missing functionality.
Yeah, I agree with it. It’s easier to spot something that causes a problem than something that is off and should be on. Not to mention that it usually works.
Now, about firewall… I’m a firm believer of “block everything not allowed”. I think it makes a neater and safer config.
On a side note:
Upgraded one RB5009 to 7.15.2
Almost everything works: one IPsec peer didn’t come back. I need further investigation, as this peer has a past history of weird traffic problems. Since it’s not controlled by me, it may take a while.
But Wireguard, BGP, BGP filters and EoIP are all working ok.
I too upgraded our RB5009’s but unfortunately there is a bug in PoE for which I had to install 7.16beta4 to fix it 
[quote=wfburton post_id=1085352 time=1720794983 user_id=215408]
I don’t see having RSTP enabled if you don’t have another switch with RSTP enabled.
[/quote]
Any ROS bridge acts as a “switch” AFAIK.
[quote=wfburton post_id=1085352 time=1720794983 user_id=215408]
I don’t see having RSTP enabled if you don’t have another switch with RSTP enabled. All you would have is a designated root.
[/quote]
As explained earlier: in most cases having RSTP enabled doesn't do any harm. But it can prevent probkems caused by some stupid mistakes (such as connecting two switch ports ... can be over a wall cable run, so not really obvious). Which IMO means that having it enabled by default is a sane thing. If somebody discovers that it causes a problem, then that particular admin can disable it.
As to insults: what you deem as an insult was a colorful response to your "
I'm not trying to tell you that you need anything (do I couldn't care less if you need MLAG or not), I'm just saying that you can't expect MT to adapt defaults to some plain use case.
PoE in or out? I’m powering mine from a CSS106-1G-4P-1S. It’s working perfectly.
PoE out. I am powering a hAP ac and a wAP ac from it (the hAP was originally powering the wAP but now the routing is done on the 5009 and the hAP is just for WiFi).
It worked fine on 7.12.1 and after upgrade to 7.15.1 it still worked, but then a powerfailure occurred and after that the port connected to the hAP ac showed repeated “overload” messages.
I asked support and they replied it was an error in the PoE chip firmware and 7.16beta4 would fix it.
Indeed, beta2 already:
*) poe-out - upgraded firmware for SAMD20 PSE (AF/AT) controlled boards (the update will cause brief power interruption to PoE-out interfaces);
I have a HAP AX2 with CAPSMAN setup and have been noticing that every 5-15 min the WIFI interface lock up for 10-20 seconds - no data passing to WIFI clients. When this happens, some clients will disconnect (infamous “disconnected, connection lost, signal strength -40”) some cycles more clients than other. Not the same clients every cycle but even the clients that don’t disconnect can’t pass packets in this time. It’s a new setup so haven’t tried previous versions so that is my next troubleshooting step. Have tried just about every channel on 2.4 and 5ghz and have seen no difference between any of them so don’t think it has to do with noisy environment. Have no issues with HAP AC lite in my home.
Only WIFI clients are affected - wired have no issues at this time. Anyone experiencing similar issues on 7.15.2?
So after trying several different config changes and even PSU swap I couldn’t solve the WIFI stability issue. As a last resort I downgraded to 7.14.3 and after 3 hours not a single stability issue - except for 3 SA query timeouts on IOT devices.
Definitely seems like there is a WIFI stability issue in 7.15.2.
There was ROS version string in v6 visible from every menu. What happened to that in v7?
Please explain in detail what you mean…
Almost everywhere we had a string saying “RoS 6.x.x”. It doesn’t happen anymore with V7.
Take the web interface: It shows “RouterOS v6.49” just above the login. With V7 we have “RouterOS” only.
This behavior happens everywhere. We used to just look at the interface and know the OS version. Now we have to look into “packages” or “Resources”.
It’s not a big deal, but I think that’s what he’s talking about.
Oh in webfig? He did not say it was about webfig… in winbox the version is in the title bar for both v6 and v7.
In general it is not a good idea to reveal the version on a login page. Scanners and intruders use that to know if you are running a version for which they know how to break in to it.
Well, in webfig I’m certain of it. Rarely use Winbox, and the command line… well, no one expects to see the version at every command output.
Yes, I do agree with the security problem. But, You see, with webfig we had the version (after login) at the top bar. At every page. It’s gone now. In its place we have the identity we chose.
Again, a minor inconvenience - but I think that’s what he is talking about. It was not only the front page.
That can be argued regarding what to display before you are logged in.
But once you are logged in there is no reason to hide the version even if its 2 clicks away (you can in ROS 7.x click in the upper right corner on that settings icon and then select about to get to the page with /system/resources who will display current version and current boot version).
When you use CLI/SSH the version is displayed in the MOTD (that ascii-art Mikrotik logotype).
I do not think it is that useful or important to always know what the version is.
What I would consider useful and important is to display the “Note” from the winbox neighbor list next to the “Session”.
When you have several devices to manage it is helpful to know immediately which device you are accessing.