Disabling Wi-Fi Management via CAPsMAN on MikroTik: A Complete Disassembly

Manage wireless networks via CAPsMAN (Controlled Access Point system Manager) in MikroTik — a powerful tool for centralized access point administration. However, in some scenarios, it is necessary to restore autonomous Wi-Fi operation, for example, when switching to alternative management systems, testing new configurations, or resolving conflicts. Disabling CAPsMAN is not an obvious process, especially if the access points (CAPs) are already tied to the controller and do not want to work independently.

In this article, we'll cover all methods for disabling CAPsMAN: from simply disabling the service on the controller to forcing a reset on client devices. We'll pay special attention to common errors (for example, when access points get stuck in controller standby mode) and how to work around them. This article is relevant for RouterOS versions 6.43+ and 7.x, but the key principles apply to older firmware as well.

Why you might want to disable CAPsMAN

Centralized Wi-Fi management via CAPsMAN is convenient for large networks, but it's not always practical for home or small office environments. Here are the most common reasons for disabling it:

• 🔄 Switching to offline mode: If the network is simplified and no longer requires synchronization of settings between access points.
• 🛠️ Problem diagnosis: CAPsMAN may conflict with other services (e.g. hotspot or user-manager).
• 📡 Testing alternatives: Before migrating to solutions like Unifi, Ruckus or cloud controllers.
• ⚡ Performance issues: In some cases CAPsMAN adds delays when roaming or authenticating clients.

It's important to understand that disabling CAPsMAN doesn't always mean a complete reset of Wi-Fi settings. In most cases, access points retain their default settings (e.g., SSID And security-profile), but lose their connection to the controller. However, if the configuration was initially created only through CAPsMAN, autonomous operation may require manual configuration.

Preparing for a Shutdown: What to Check

Before disabling CAPsMAN, audit your current configuration to avoid losing critical settings. Here are the key points:

1. List of managed access points: Make sure everything is CAPs (client devices) are taken into account. You can view them in CAPsMAN → Registration Table.
2. Security profiles: Write or export settings security And datapath, if they are unique to your network.
3. Local Wi-Fi settings: Check if your access points have offline profiles (in Wireless → Security Profiles). If not, they will have to be created again.

Pay special attention operating mode access points. If they are configured as caps-mode=managedAfter disabling CAPsMAN, they may stop distributing Wi-Fi altogether. In this case, a manual reset will be required via Winbox or SSH.

Back up your configuration|Write down your Wi-Fi SSIDs and passwords|Check for offline security profiles|Ensure access to access points via Ethernet/IP|Disconnect clients from the network while making changes-->

⚠️ Attention: If the access points are connected to the controller via wireless (and not via cable), their settings may be reset if the connection to CAPsMAN is lost. In this case, operation can only be restored through physical access to the device.

Method 1: Disabling CAPsMAN on the controller

The most obvious method is to deactivate the CAPsMAN service on the main device (usually this is RouterBoard (with the controller role). This will not delete the settings, but will stop managing access points.

Run the following commands in Terminal:

/caps-man manager set enabled=no
/caps-man datapath disable [find]
/caps-man security disable [find]

After that:

1. Reboot the controller: /system reboot.
2. Check the status of access points in Wireless → Registration TableThey should disappear from the CAPsMAN list.

If the access points do not return to autonomous mode, they will need to be configured manually (see section on manual configuration).

Method 2: Force reset of access points

If after disabling CAPsMAN on the controller the access points remain in the mode caps-mode=managed and aren't distributing Wi-Fi, they need to be forced into offline mode. This can be done in two ways:

Option A: Via Winbox/WebFig

1. Connect to the access point via MAC-Telnet or IP (if available).
2. Go to Wireless → Interfaces.
3. Select the Wi-Fi interface, click Advanced Mode and change Mode on ap bridge (or another desired mode).
4. Remove or edit the parameter master-interface, if it refers to CAPsMAN.

Option B: Via the command line

Connect via SSH and run:

/interface wireless set [find] master-interface=none caps-mode=none mode=ap-bridge

If Wi-Fi still doesn't work after these steps, check:

• 🔌 Availability of a security profile (security-profile) in the interface settings.
• 📶 Correctness of the indication SSID And frequency.
• 🔄 Radio interface status (running=yes V /interface wireless print).

⚠️ Attention: On some models (eg, MikroTik cAP or wAP) After resetting CAPsMAN, a full reset of settings may be required (/system reset-configuration no-defaults=yes). This will delete all user data, including IP addresses and routes!

Method 3: Manual Wi-Fi setup after CAPsMAN

If there are no standalone profiles on the access points, you'll have to create them from scratch. Here's the bare minimum set of commands to restore Wi-Fi operation:

# 1. Create a security profile (example for WPA2-PSK)
/interface wireless security-profiles add name=my_wifi_sec mode=dynamic-keys authentication-types=wpa2-psk unicast-ciphers=aes-ccm group-ciphers=aes-ccm wpa2-pre-shared-key=your_password

2. Configure the radio interface
/interface wireless set [find default-name=wlan1] band=2ghz-onlyn channel-width=20/40mhz-Ce country=russia frequency=auto mode=ap-bridge security-profile=my_wifi_sec ssid=MyWiFi wireless-protocol=802.11

3. Activate the interface
/interface wireless enable [find]

For dual-band points (e.g. MikroTik hAP ac²) repeat the setup for the interface wlan2 (5 GHz), specifying the appropriate parameters band And frequency.

If Wi-Fi doesn't appear in the network list after applying the settings, check the regulatory restrictions (country parameter). An incorrect value may block broadcasting.

Common mistakes and their solutions

When disabling CAPsMAN, users often encounter the following problems:

• 🚫 Access points are not responding: If you can't ping devices after disabling CAPsMAN, check if their IP addresses have been reset. Connect via MAC-Telnet and assign a static IP manually.
• 🔄 Constant reboots: On some firmware (RouterOS 6.45.9 and below) there were bugs with freezing after the change caps-modeThe solution is to update the software.
• 📡 Wi-Fi turns on, but clients don't connect.: Most often this is due to the lack of security-profile or incorrect authentication-types (for example, only wpa-psk without wpa2-psk).

Another common mistake is trying to disable CAPsMAN via Quick Set V WinboxThis section does not display all options, so always use Terminal or Wireless → CAPsMAN.

What to do if the access point "forgot" all the settings?

If after disabling CAPsMAN the device was reset to factory settings (for example, MikroTik RB4011 in the CAP role), you can restore the configuration via Netinstall:

1. Download the Netinstall utility from the MikroTik website.

2. Connect the device via Ethernet to a PC (without other network connections).

3. Press and hold the Reset button on the device, apply power and hold for 10 seconds.

4. In Netinstall, select the firmware and download it to the device.

After this, you will have to set up Wi-Fi from scratch.

Alternatives to CAPsMAN for Wi-Fi Management

If you are abandoning CAPsMAN in favor of other solutions, consider the following options:

For small networks (up to 5 access points), standalone mode is often optimal. However, if roaming or centralized monitoring is required, it's worth considering Unifi or Omada from TP-Link.

FAQ: Frequently asked questions about disabling CAPsMAN

Is it possible to disable CAPsMAN for only one access point?

Yes, but not through the controller. You need to connect to the access point itself and change the setting manually. caps-mode=none in its settings (/interface wireless set [find] caps-mode=none). After this, it will stop registering in CAPsMAN, but will remain online.

Why did my Wi-Fi speed drop after disabling CAPsMAN?

This may be due to:

1. Automatic channel selection: CAPsMAN often optimizes frequencies better than standalone APs.
2. Absence datapath: If the central one was used before datapath for load balancing, its absence may reduce performance.
3. Resetting the parameters tx-power or distance to default values.

Please check these settings manually and adjust them if necessary.

How do I get CAPsMAN back if something goes wrong?

If you saved the configuration export (using the command /caps-man export), you can restore the settings like this:

1. Import the saved file: /import file-name=backup_capsman.rsc.
2. Enable CAPsMAN: /caps-man manager set enabled=yes.
3. Reboot the controller and access points.

If there is no backup, you will have to configure CAPsMAN again, including security profiles and datapath.

Does this tutorial work for MikroTik with RouterOS v7?

Yes, the basic principles have not changed, but in RouterOS 7 new parameters have appeared, for example:

• caps-man v2 — improved version of the protocol;
• support 802.11ax (Wi-Fi 6) in CAPsMAN;
• The syntax of some commands has been changed (for example, /caps-man interface instead of /caps-man remote-cap).

For v7, please use the latest documentation or check the commands via ? V Terminal.

Is it possible to control MikroTik CAPsMAN via the cloud?

No, MikroTik does not provide a cloud service for CAPsMAN. However, you can:

• Place the controller on a VPS with a public IP and connect access points to it via the Internet (not secure without a VPN!).
• Use The Dude for monitoring, but not for control.
• Tune IPsec or WireGuard for secure remote access to the local controller.