Oh dear, 7.25 is a very bitter-sweet release and I see before my closed eyes a lot "Introduced in 7.25" statements in the next releases 
Maybe related to this?
dhcpv4-client - ignore forcerenew packets that are not unicasted to client;
While it doesn't look like my current ISPs are sending forcerenew packets, I suspect there might have been a regression or bug during the recent changes to the DHCPv4 client code.
Similar issue with RB5009 (CAPsMAN) and two hAP ax S (CAP). 3 SSIDs configured, 2 dual channel and 1 on 2.4GHz only
- All wifi interfaces appeared steady on CAPsMAN - wifi interface numbers consistent.
- For CAPs, master config was steady and functional while slave configs were constantly reprovisioning (interface numbers increasing) and non-functional.
Downgrading back to v7.24.4 resolved the problem. Also tried downgrading just the CAPs but the same problem occurred, suggesting the behaviour is in CAPsMAN?
All configs, master & slave, use the same channel configs with reselect-interval set. If this is actually to blame then why does it only affect slave configurations?
Because you realistically cant have different channel settings on the slave interface.
good info, thanks
RB5009 - no issues
hAP AX3 - no issues
Smooth upgrades for both devices.
Same problem. Downgraded MLAG switches to 7.24.5
The whole MikroTik MediaTek hardware lineup is underperforming imo.
You talking about something like this: 7.23.8 [long-term] is released! - #29 by Mordulec
Another finding, my SAT>IP UpnP in VLC stopped working since 7.25 from other VLANs.
VLC:
There is a new tab under Routing -> PIM SM -> "IGMP Interface Template":
It seems, this tab is new (dont see it in 7.24.5) for the IGMP Querier to turn on.
After creating here the VLANs (Interfaces) too (as under "Interface Template"), my SAT>IP-list started to show up (IGMP querier frames show up again in Wireshark)!
I dont see it mentioned here:
Should read like "pim - IGMP-querier configuration now under "IGMP Interface Template; no querier configured by default".
Similar config with RB5009 (CAPsMAN) and three hAP ax² (CAP). Three SSIDs have been configured; all three are dual-channel, but only the third for IoT is without WPA3 and without FT.
All configurations use fixed channels and withoutreselect-interval, so I haven't encountered this problem with flapping interfaces. However, the third SSID (with the different configuration) is very unstable, with high latency, and ARP resolution fails regularly.
I tried updating my hAP_be_Lite to 7.25 and it started doing a reboot oscillation. Would not stabilize at all. I had to NetInstall 7.24.5 and it's normal now. While it seems that most other Mikrotik routers are embracing the 7.25 update, I think the hAP_be_Lite version is a bit too hinky for my taste. 
I'll wait for the fixes before I try upgrading again.
Unfortunately, my wireless exists in an extremely congested environment with other people's devices also frequently reselecting their channels. Leaving everything on fixed channels and crossing fingers is an execise in frustrating wireless performance 
I'll just stick on 7.24 for now - everything works 
Adding a data point to balance the thread a bit. I moved most of my kit from 7.24.5 to 7.25 this morning, the day after release, and it has all been clean:
- 3× RB5009 (one UPr+S+, two UG+S+): site gateways, one of them in a datacentre, running BGP with BFD, WireGuard site-to-site, VLANs, firewall and NAT
- CRS310-8G+2S+ switch (no MLAG here, so I can't comment on the log flood reported above)
- hEX (E50UG)
- 2× CHR on x86_64
RouterBOARD firmware is done on the RB5009s as well. Every BGP and BFD session came back without me touching it.
What I haven't upgraded is my pair of wAP 60G Wireless Wires. They're still on 7.24.2, and they'll stay there until a point release has been out for a while. That isn't a contradiction. It's how I've learned to run MikroTik over twenty-odd years.
MikroTik enthusiasts know where the kit is strong and where it isn't, and build around it. Wi-Fi has been the weak spot for as long as I can remember, which is why so many of us pair MikroTik routers and switches with UniFi or similar access points and never use MikroTik for Wi-Fi at all. Look at what's actually broken in this thread: a good chunk of it is CAPsMAN/Wi-Fi (the reselect loop) or devices with radios (the hAP be lite boot loop), and most of the rest is fairly specific setups like MLAG and IPsec.
Years ago I'd have agreed with a lot of what's been said about updates breaking things, but for routers and switches that's mostly old news. For my feature set they've been reliable on every update for more years than I can remember, and I've stopped worrying about upgrading them. Anything with a radio is different. The Wireless Wires have so little free space that I'm always nervous one will fail mid-upgrade, so they get the treatment others here have suggested: skip the .0, wait for .2 or .3, then upgrade.
For routing and switching, very little comes close to MikroTik on price or on updates. There's no subscription, no cloud dependency and years of free RouterOS updates on hardware you bought once. I wish more vendors worked that way, UniFi included. They've come a long way since I started with them.
I also run Debian boxes as routers alongside my MikroTiks (BIRD, WireGuard, HAProxy), so this isn't an anti-Linux post. But on a router, firewalls aren't a separate issue; they're most of the job. Forwarding is one sysctl. A usable router is that plus nftables or iptables rules, NAT, a DHCP server, DNS (dnsmasq, Unbound, BIND or PowerDNS), VLAN interfaces, RA/DHCPv6 for IPv6 and quite possibly PPPoE. That's a lot of moving parts before you're anywhere near what a MikroTik gives you out of the box, and you then own the upgrades for all of them.
This isn't meant as a rant. MikroTik kit is low-power, cheap for what it does and gets updated for years. If your device has a radio in it, take a few extra precautions before upgrading. For everything else, upgrades are pretty robust these days.
Just my two cents.
I don't understand MT. 7.25 stable yeah ok.
Back to 7.24.5 stable!
Same issue with IPv6 connectivity
SmokePing is death in 7.25.
(20014)Internal error (specific information not available): AH00058: Error retrieving pid file /run/apache2/httpd.pid
You can see that I am a new user. However, I have been working with Mikrotik for 10 years now. Therefore, I understand that before any update, you need to read the forum, make a backup in advance and be ready for Netinstall.
That's why I upgraded my home hap be lite first and didn't upgrade my corporate devices.
I wrote my message so that Mikrotik would pay attention to the problem that they missed before the release. Because even an experienced person couldn't make hap be lite work using many different settings changes.