containers don’t compare to the useless detect-internet 
Now it gets even more weird, the fix is not listed in the 7.5beta8 change list either… I would expect it to be at least in the next beta when it is fixed in stable already.
(and of course I am disappointed once more w.r.t. BGP fixes)
Hopefully they will remove the entire feature, it is just a nuisance.
One can always dream…
I have problem with ntp for now. When I setup some ntp servers to stratum 1 it shows: WARNING: frequency out of range: 0.000542. MAX: 0.000500
Is it normal?
Considering it appeared right after a time sync, you figure it out.
Thanks for the update on this
*) wireless - fixed interface initialization on x86 devices;
There is no error now but seems not yet working. scan frequency is ok but does not discover other APs which are next to it.
Let me do more testings later
The fix was tested with our R11 series wireless cards. Failure to detect a nearby AP may be due to the scan-list (governed by the country setting) not covering frequencies that the APs are operating on.
If you’ve ensured that the settings are correct, but the interface still does not work, please open a support ticket and include a supout.
A Beta changelog contains changes from the last stable release. All changes that were released in stable/RC versions are present in the following betas by default.
I am using a generic MikroTik R11e-5HacT.
In the wireless, it is recognized as Wireless (Atheros AR9888)
I am locating in Hong Kong. I look at the ac2 I have which I did not set anything but it just works
However, now in x86, seems I still miss something
Does anyone know what exactly is fixed here?
*) vrrp - fixed HW offloaded bridge MAC address learning when changing from VRRP master to backup;
I have a weird bug where backup router would not respond to ARP requests for VRRP IP once it became master. VRRP interface is VXLAN VTEP on CCR2216(didn’t work with L3HW or w/o L3HW). Had to do a workaround to add another IP on master and remove on slave using scripts. Wondering if the beta would fix the issue since it contains a lot of VRRP fixes.
Correct. VRF is working now.
I wish this was documented somewhere! This is news for most of us!
Indeed. I would not have guessed that. Then, at least it should refer to the release number of the stable release from which it has all the fixes.
There are two lists on the official change log:
- What’s new in 7.5beta8 (2022-Aug-09 12:36)
- Other changes since v7.4.1
Usually, users install a beta version for faster access to features and fixes they are interested in. Otherwise, there is no point in using beta - just play safe and install the stable version.
ROS 7.5beta8: wireless
In wireless table if on tab Wifiwave2, selecting “detail mode” crashes WinBox (64 bit) V3.35 and V3.37.
That’s fresh basic config and update to latest beta…On v6 and HAP AC2 is everythink ok. So it is my problem find the solution? Haha
What if is a problem on a buggy FW..
Are you experiencing a problem or you just don’t like the warning? because you can hide the warning.
Ok it would be better when the above was also present in the annoucement on the forum. Now we have to gather the info from so many different places…
I had experimented with VRF in 7.4 and encountered the above-mentioned bug, but I am using the beta versions to keep up with the latest additions, because, you never know, maybe the BGP programmer comes back and starts fixing his work.
Then I see the 7.4.1 announcement and I am happy the problem encountered in VRF is fixed there but of course I want to continue using the beta.
So now I will install beta8 knowing that at least this VRF problem is fixed.
+1 And please create a new thread for each release ( eg:1 separate post for beta4 and another one for beta8 )
Posts become so cluttered with issue unrelated with the current release
( see post about docker, if you start using docker on 7.5 beta you have a huge thread full of stale info to digest… )