Remove wireless package and install wifi-qcom-ac-7.13-arm.npk from all_packages-arm-7.13.zip
Everything is in the documentation:https://help.mikrotik.com/docs/display/ROS/WiFi#WiFi-Replacing’wireless’package
You did install wifi-qcom-ac package as well ? This is a manual action to be done afterwards and then you completely need to reconfigure the wifi part.
https://help.mikrotik.com/docs/display/ROS/WiFi#WiFi-Replacing’wireless’package
EDIT: someone hit the button a bit faster then I did 
Well, as mentioned, it’s not booting any longer, so no chance to get the supout anymore.
CCR1016 after updating to 7.13 not show lte interface anymore.
But in USB list it showing.
wireless already installed
At 7.12 all ok.
Does not happen on default config of “RB1100AHx4 Dude Edition” with 7.13. Ensure that there is no netwatch or something else that is rebooting it. Try to generate supout.rif and send it to support@mikrotik.com
DHCP served over a VLAN trunk is still a problem on x86. Rolled back to 7.11.2.
See here, and here (post 99) and SUP-134483.
Same router, all working ok for me, no issue.
Works so far:
But for clarification regarding “Wireless” and “WiFi”:
- Can I uninstall the old “Wireless” package on devices without WLAN-interface (like Switches), or will this break something (like CAPsMAN-management traffic or something)?
WiFi is always there, but useless?
- On devices like the mAP lite, I have now a WiFi button plus a Wireless button. But nothing in the “WiFi” menu.
There is no additional driver in the MIPSBE-Extra-package. Means WiFi is always there, but useless?
- Devices without the additional driver ( ‘wifi-qcom-ac’ or ‘wifi-qcom’) have to run everything WLAN-related under the old Wireless-Menu?
Means WiFi is always there, but useless?
Have upgraded:
1 x RB3011-iUAS
2 x hAPac2’s
All were on 7.12 and all are working perfectly after upgrade, havent tried swapping out the wifi packages yet, using the old wireless one for now.
Loaded 7.13 on a few AX2 units. Fetch from scripts is currently the only one item that stands out with errors compared to 7.12.1.
We have a script that triggers on boot and fetches a few files from our provisioning servers (Basic auth and HTTPS).
On 7.12.1 works every time.
Using 7.13 the first file is saved without issues, but we observe different errors for subsequent files:
script error: failure: Idle timeout - waiting data
script error: failure: connection timeout
script error: failure: remote disconnected while in HTTP exchange
The entire job is a single script.
Edit the delay does not fix the issue
To my understanding:
1- yes.
2- correct, consequence from having (wave2) wifi in base package now.
3- yes. See also 2.
@Mikrotik, please update the Menu-Name from WiFi Menu to WiFi NOT Wireless!!!
This is totally confusing o_O
Thanks!
fetch - require “ftp” user policy;
Is there any wiki for using NEW driver packages for “OLD” devices ? And if so, when I will use NEW drivers from NEW package, can I use just ONE capsman (section) ? For new and also for old devices ?
Or it is just how I thing and there will be always TWO capsmans ( if I have non EX devices also ) in my network… ?
It’s not useless, it can be used as Capsman to manage devices using new wifi driver.
It’s confusing, if device A doesn’t have wireless chip/features, then “Capsman” should be seperate menu altogether, not “wifi” or “wireless” or “wifiwave2”, capsman is just a control plane protocol.
Like on 1 out of 100 devices its useful and on 99 useless? Useless codestuff imho…
With wifi(wave2) capsman configuration is no longer separate from local wifi configuration. It’s only confusing because it used to be different.
*) wifi - create first interface without number when using “name-format” provisioning setting;
Is there any way to restore default behaviour, where all CAP interfaces would have number appended?
This is super annoying, do I really have to downgrade to, as my only option, make it work properly again? 
I really don’t want to switch to static interfaces and overcomplicate things.