Running fine on 7.24.5. After upgrading to 7.25 stable (and also tested 7.26beta3), Wi-Fi is basically unusable:
clients mostly can't connect at all
if a client does connect, there's no traffic / no internet and it drops after a few seconds
wired side works normally
Downgrade to 7.24.5 (routeros + wifi-mediatek) fixes it immediately with the same config.
Honestly, I'd expect a release in the stable channel to be properly tested, especially when Wi-Fi on a current product breaks completely. A broken wireless on a home AP is not something that should slip into stable.
Staying on 7.24.5 for now. Happy to provide a supout if MikroTik needs one.
I have a GRE with IPsec that now fails under 7.25 - AES256 CBC with SHA256 between a RB750Gr3 and a CHR on proxmox, both sides with hardware acceleration. When measured with a ping every 100ms, traffic goes through for a few seconds, then does not go through for a few seconds. Disabling IPsec makes the GRE work reliably. Likely the problem is on the RB750Gr3 side, as the tunnel failed when the RB750Gr3 was upgraded to 7.25 while the CHR was still on 7.24.2
@pe1chl i value your posts, but its difficult to ignore the inadequate quality assurance - customers complain for a reason. 7.25 CHR was compiled October 22, at 14:12. Then, October 23 at 11:58 the version is posted here; they do less than 24h of testing. That is OK for my hobby AS on the weekend, but for anything commercial where you have employees not being able to work, IMHO its not.
You are correct. I had added the same channel config to secondary (slave) configs that I was using on master configs (as per most example configs).
Obviously (now I think about it), a channel config should not be necessary for the secondaries as they are supposed to inherit channel info from the master config.
Have unset these parameters in slave configs and reprovisioned without issues. Now need to find time to try on v7.25...
I hope that the pre 7.25 behavior can be restored, where channel/freq info is simply ignored on slaves.
I have a number of configs that, depending on the AP, are deployed as master or slave (one config per SSID, no matter how it is used). With the 7.25 behavior, that would double the number of configs I need to maintain, which would suck.
Have the same problem with the Wi-Fi connection in hAP be lite after the update to 7.25, but when the access list is enabled. Even if the access list is disabled, devices can connect only after a reboot.
After updating my RB3011UiAS from version 7.24.5 to 7.25, the DHCP client on the outbound interface remains stuck in the "Searching" state. The simplest solution was to roll back to 7.24.5. If anyone has a fix for version 7.25 on the RB3011UiAS, I would appreciate it.
Updates for the hAP ac, hAP ac2, and hAP ac3 went through without any issues.
There were (albeit rare) occasions where some more stubborn upgrade issues were (quickly?) resolved by executing a cold boot of affected device. It does seem that certain subsystems are sometimes not properly reset by routerboot if their boot state is not "blank" but rather carry over configuration of previous boot.
And I seem to remember that PoE controller is quite frequently such a subsystem.
Read this and thought I do not have this issue. Logged in and realized I run 7.26Beta to get access to the CMR client so this issue does not appear to be on the current beta at least. I'm gussing it is just a wating game for 7.25.1 to land.
No, stable does not mean it is free from known bugs, it means it is not regularly updated with new features.
Every seasoned MikroTik users knows that you should not update to a 7.xx version like this one. Wait for the 7.xx.1 or better 7.xx.2!
When your time zone changed, it was likely set to "autodetect". Remove that checkmark and set it to the correct value. One of the steps to be done for every installation.
I am very dissapointed about being forced to use the new winbox, the Old Interface is so much slimer and practical for working clean and slim can you not get your developers to give a skin option in settings that allows user tweek winbox-4 to have a the winbox-3 interface design or at least a similar desing to winbox-3.
