You want to have your cake AND eat it too ? 
It would not be too difficult to make an external program (in a language like Perl or Python) that reads a /export file made when the wireless package was still used, and generates the proper commands to be pasted into a device to migrate the config to the new WiFi after the qcom-ac package has been installed instead. At least for “trivial” access point and station configurations with PSK authentication.
It could even be done as a RouterOS script, although that would be a bit more difficult due to the string handling limitations and error handling in the scripting language.
Laziness is the source of innovation my friend. Lets all of us have a nice 2024!
Thank you Mikrotik
Long waiting features ISIS on the way.
.
Update to all, very interesting changelog entry from v7.14beta4:
*) dns - do not add new entries to cache if “cache-size” is reached;
When launching export file=“$[system identity get name]” commands ROS is adding in underscores for any spaces in the name.
So a device called “this is a test” would generate a file “this_is_a_test.rsc”. Is this expected behaviour?
I should think so. Having spaces in file names calls for trouble in many many places.
Totally agree. Spaces in file names can be a real problem if used (any white-space character, for that matter).
So to be avoided when possible.
I don’t disagree with you, it is however, new behaviour.
Maybe make a call to Redmond about that! It has been a nuisance ever since 1995 but they keep doing it…
Well, it's not universal. So MT (and everybody else) are free not to endorse spaces in file names. And even MS doesn't force anybody to use spaces in file names, they simply allow them (so does linux, but as I wrote before, it causes problems). It's up to you to either try to use spaces everywhere (and live with problems) or use something else (like underscores) instead of spaces on MS as well.
Maybe there was a security issue that can be triggered by creating certain file names with spaces (or other special characters?) that has been remedied by replacing them with underscores? Usually there are those “improved stability when using …” release note lines that point to that, but this time I don’t see any. So much for the often made claim that “all changes are in the release notes”…
On MS systems you do not HAVE to use spaces in your own files, but your HAVE to live with their decisions to use spaces in commonly used directory names. So now we have "C:\Program Files (x86)" and all the time you have to be careful to use quotes. I well remember the error messages like “C:\Program not found” and maybe MikroTik wanted to cut-off that path.
Just read, and understand what are the reserved characters...
*) console - replace reserved characters in file and script names with underscores;
As already pointed out… This has been in changelog. There are other characters, that are handled the same, like dollar sign. And I think the changelog is incomplete, IIRC the same goes for scheduler names, and possibly more.
Yes, I overlooked it but indeed it is in the change notes.
I have also sometimes had problems when people used special characters in interface names, and some SNMP software would not be able to handle it.
So maybe there it would have to be done as well…
Just a quick question before saying happy new year…
If i am gonna move to new wifi drivers for my hap ac2 and create all the configuration from scratch, does anyone know if vlans are working on the wifi interfaces with the new drivers?
Only CAPsMAN needs a manual trick to make it work. Not sure if you are using that, or if it is just a single hAP ac with VLAN? In case of the latter, just do VLAN filtering on the bridge (which is very well supported with the new driver).
VLAN filtering:
http://forum.mikrotik.com/t/using-routeros-to-vlan-your-network/126489/1
CAPsMAN with VLAN:
https://help.mikrotik.com/docs/display/ROS/WiFi#WiFi-CAPsMAN-CAPVLANconfigurationexample:
wifi-qcom-ac driver doesn’t support VLANs natively, but you can configure wifi intetfaces as access ports of vlan-enabled bridge. In many cases this is fine as well.
I have ended with this mess in radios - how can I clean this?
Also I have multiple items in “Remote CAP” which I can’t remove. I have disabled CAPSMAN and still unable to clean all this items…
My setup is RB5009 (Capsman controller) and three ax2s as CAPs. Upgraded RB5009 to 7.13 and my wi-fi network went down. Connected to RB5009 with ethernet cable and added qcom package. Dodn’t help. I still cannot connect to my APs and I cannot ping them even if they are connected as before. What should I do?