On the other hand, I found and reported (above) 3 new issues in BGP and none of them are even remotely related to a “What’s new” item about BGP in the opening post.
So clearly there are changes that do not appear in there. It could well be that BFD has been added in this release and we would not have noticed.
iOS devices still have hard time with 802.11r [1]. They can’t re-connect to AP after the latter gets restarted or when wifi interfaces are on → off → on. The logs show the same:
mac-address@wifi2 rejected, can’t find PMKSA
mac-address@wifi1 rejected, can’t find PMKSA
mac-address@wifi2 rejected, can’t find PMKSA
mac-address@wifi1 rejected, can’t find PMKSA
mac-address@wifi2 rejected, can’t find PMKSA
mac-address@wifi1 rejected, can’t find PMKSA
[1] http://forum.mikrotik.com/t/v7-4beta-testing-is-released/158543/186
I only find an on/off switch for the feature.
Isn’t 802.11k supposed to provide the client with a list of neighboring APs? Where does this list come from? I suppose the list should either be manually configurable (I think this is possible in OpenWRT), created by a centralized management solution (like capsman) or populated by the AP itself by scanning its neighborhood (might cause short outages while scanning other channels).
The current 802.11k/r functionality is just a work in progress in preparation for future use in real applications.
At the moment, it only knows about the 2 interfaces of the same AP (2 GHz and 5 GHz) to roam between them. More or less a toy.
Of course for real usability it has to have a “backbone interconnect” between the involved APs, yes. That would likely be part of a new CAPsMAN2 that manages them.
What’s new in 7.5beta5 (2022-Jul-28 10:59):
*) health - renamed “CPU” to “switch” for temperature reading information on CRS518-16XS-2XQ;
*) l3hw - fixed HW offloaded NAT;
*) ppp - improved service stability under high load;
*) ppp - use /32 as default netmask if not specified for “routes” parameter;
*) sfp - fixed “eeprom” reading on single SFP port ARM devices;
*) sfp - fixed unresponsive “sfp1” interface after disabling “ether1” on NetMetal devices;
*) swos - enabled SwitchOS support for CRS310-1G-5S-4S+;
I’m showing my age, but the current Capsman is V2 
Maybe a stupid question: Is create folders in mounted folders in container possible/fixed? I cant get Adguardhome to work because the mkdir-permission-error.
Not yet.
maybe one day rb760 igs SFP port will have (again) SFP status ?
hi,
with ros 7.5beta4 all the sfp and DAC cables still don’t work under ccr2116 & ccr2004. the link just flaps endless, whatever setting you make. reported to support since months now, but still no fix.
even original mikrotik DAC cable doesn’t work anymore since ros 7.3. latest working version in terms of sfp support was 7.2.3.
those are the one we have tested in all combinations and are not working in the top of the line mikrotik hardware with the ‘stable’ ros7 versions:
MT seems able to identify and fix the issue, producing a test release. I am not able to test it because I don’t have spare parts.
Ask MT about this release to test.
regards
Ros
Chateau 5G successfully updated to 7.5beta5
Any Chance of Adding Advertisements in BGP Option. Really Useful to Check what is getting Advertised to peers.
Currently in ROSv7 its very difficult to find our the Advertisements compared to ROSv6.
Please Mikrotik Team Look in to it…
+1
+1
This is just one small detail of the general “improve monitoring capabilities for BGP”…
+1
Documentation is not yet clear
- https://help.mikrotik.com/docs/display/ROS/Container#Container-Requirements page says “container package must be installed” but does not tell you how
- There is no /system/package/install command
- no package repository configured in routeros to list available packages
- https://help.mikrotik.com/docs/display/ROS/Packages does not tell anything about existence of a “container” package
- in https://mikrotik.com/download there is no such thing as a “container” package. only an “main” an an extra package
- which architecture do I need to select ? it’s not shown in /system/routerboard nor in /system/identiy not in /system/package
- how to ship package inside router ?
ech1965, get architecture via /system resource print, download Extra packages, upload container-*.npk via ftp, scp or winbox and reboot to trigger the installation.
Container package is compatible with arm arm64 and x86 architectures.
MANY Thanks !!! glad we have people like you on this forum, because… doc writers have a lot to catch up at mikrotik !