*) wifi - create first interface without number when using “name-format” provisioning setting;
Duh I missed that. OK change it back then. It’s ugly and pointless.
Or, make it suffix-less only if there are no slaves.
Or, make it optional. With default based on, whether there are slaves or not.
With numbered WAP, it makes sense to add dash or underscore at the end to separate device number from wireless interface (SSID) number. I agree, it would result to be ugly.
However, ideally, I would like to have ability to set suffix/prefix for master and each slave explicitly. Such as “private-%I” (“%I-private”) and “guest-%I” (%I-guest"). It would show up more informative in logs - connected to private/guest AP, roamed between private/guest APs.
Though, this release is great. WifiWave2 (renamed to WiFi) was brought to 802.11ac devices (ARM only). It allows people to upgrade/expand old network and keep everything under one (new) CAPsMAN. And, allows also to setup 802.11r/k/v roaming between all the devices - old ac ones, and new ax ones.
OK change it back then. It’s ugly and pointless.
[/quote]
Though, this release is great. WifiWave2 (renamed to WiFi) was brought to 802.11ac devices (ARM only). It allows people to upgrade/expand old network and keep everything under one (new) CAPsMAN. And, allows also to setup 802.11r/k/v roaming between all the devices - old ac ones, and new ax ones.
[/quote]
Yeah I completely agree. Knowing since the beginning the ARM-AC chipsets were underutilised and underperforming and years of weird crashes requiring reboots and cranky clients has now given way to a new lease of life on the AC units. I am very, very happy with this development. I am trialling a small site with them and it’s been just fine. Once this RC is done I’ll try it at bigger sites. I don’t expect any major issues.
Since updating a CAP AC I detected this error in the log after booting:
error while running customized default configuration script: no such item
Apparently the device is running fine (except for the lack of vlan assignment via new capsman), but how should I get rid of this error?
Is there prevision for a future release where vlan assignment will work again as expected and used to?
Regards
The error (perhaps worded slightly differently) is there for any ac device if wave2/wifi driver is installed instead of default wireless (e.g. wifiwave2 on audience). It had been reported numerous times, @rextended also pointed out exact location and proposed a solution. MT devs chose to ignore the reports though.
True and I agree, very excited to upgrade the many cap AC and AC XL that I have installed for customers 
And, allows also to setup 802.11r/k/v roaming between all the devices - old ac ones, and new ax ones.
I’m not too sure about this though. With another vendor’s gear, I found that some clients do not want to roam from ax to ac device (a client side issue of course). So i’m not sure mixing is a good idea. I’ll try it soon anyway, maybe when Mikrotik release a wAP or a cAP that isn’t the size of a frickin pizza.
I’ve tested it with hAP ax³ (7.12 CAPsMAN), hAP ax² (7.12 CAP) and wAP ac (7.13beta CAP). Clients do roam between all of them. I even run wAP 5GHz radio only on 40MHz width, and it works ok. Maybe, it’s based on signal strength and predicted speed based on strength - i.e. slightly worse ax signal might be preferred over ac, but not heavily worse.
My goal is, that when connection to indoors ax access point is going to die, then it roams seamlessly to outdoors ac access point, without trying to hold on to poor signal to ax AP giving just 1MBit connection. This is accomplished.
(If interested, I’ve already shared the config for CAPsMAN and CAP in the beta thread)
RB5009 + cAP XL ac (with CAPsMAN) work like a charm. Thank you, MikroTik!
For some reason I thought wap ac was mipsbe and couldn’t get new WiFi driver. Hmm.
Anyway cool good news and thanks for sharing
New version have ipq40xx soc inside.
There are 2 versions of wap ac
Mipsbe and arm.
Only arm will work with new drivers.
Sorry if dumb question.
I have multiple CAP AC devices. Before this would run with capsman, multiple SSIDs with each SSID on their own vlan. Practically different datapaths, security, etc configured in capsman. So far i’ve just managed cap AX devices individually, and kept cap AC devices under capsman. So like many very excited at the possibility to manage under a single capsman going forward.
As I understand the vlans i’ve done via capsman no longer work if I use the new capsman under wifi with 7.13. Is this considered ‘as it will be’ when released, or is there efforts ongoing to bring this functionality into capsman on the wifi packagee?
Trying to understand if I should start finding a solution to this limitation, or should just hold out for future releases with that functionality.
You can still do that. The configuration on the cap side is a bit special but that only matters if you are configuring yourself instead of caps-mode defaults (I posted about my difficulties getting this working, but got there in the end). I did struggle a bit though and an not super eager to have to do it again without more practice so I remember better .
in the case of very big routing table (~5M ripv4 prefixes), in winbox when you open the window “ip route” to search a perfix,
the route print command never stops, also after showing the searched prefix, saturates indefinitely one cpu core, like it never stops to fetch the routing table. The cpu core remain at 100% also if you close the ip route window or even when you close winbox.
This cause a very slow bgp advertisment process and routing table update.
Instead of winbox ip route, if you use console, the command is executed and closed correctly, and one cpu core go to 100% just for the time it needs to seatch the prefix. So be very carefull to use winbox ip route.
SUP-133971 tracks this issue.
regards
Yes, this is an old issue with big routing tables. There are also some other issues as searching by a community or blackhole routes or whatever. Not all routes are displayed. Same behaviour in CLI or in Winbox.
They are already working on it.
That’s why you using 16MB flash, later you regretting it. 
Why not use internal M2/USB port for storage in all products? (as other vendors doing it)
I have one issue with my cap ax wifi which is controlled by my capsman controller on my hex s.
Some devices aren’t placed in the correct vlan. In this screenshot you can see two devices which are connected to the same interface / ssid:
One device got placed into the correct vlan-id and the other got no vlan-id.
Just WPA2-PSK without any dynamic vlan assignment.
This issue only happens on my cap ax, my hap ax2 fine.
Also this only happens on exactly this ssid, the two other ssids are not affected.
Start new thread with export of your config on hex and cap ax.
heavy memory leak on the rc2 on rb450gx4. within 4 hours, 1gb ram became 450MB available (from typical 920MB available)