1

It seems that with MikroTik RouterOS 6.43.4 setting a device to CAP mode is not persistent across reboots.

More detailed, steps I took that reproduce the problem:

  • Connected the wAP AC to my CAPsMAN router's POE port while holding the reset button for ten seconds, until the AP/CAP led starts blinking.
  • Verified that the wAP device went into CAP mode.
  • Verified the connection in the CAPsMAN Remote CAP list, and connected over wifi with the SSID set in the CAPsMAN config to the device.
  • Verified my connection in the registration table.
    So far all good.
  • unplugged the wAP device, and plugged it back.
    The device has reset itself, it broadcasts the default wifi SSID, and did not set a persistent CAP mode.

RouterOS 6.43.2 with the same setup worked fine.
Can anyone confirm this as a bug in this version?

Király István
  • 599
  • 5
  • 24

1 Answers1

1

After consulting with MikroTik support, it seems that this is a kind of new security feature. So here are all the steps to set a routerOS device to a permanent CAP client.

  • Connect to the default MikroTik-MAC based wireless network
  • Access WebFig under 192.168.88.1 or use any other access method
  • under System -> Packages, Check for Updates
  • Update to the latest version.
  • Poweroff, the hold reset while powering on.
  • The 2Ghz 5Ghz LED's will be blinking, and after about 10 seconds, when the AP/CAP LED starts blinking instead, release the reset button.
  • The device is now in a temporary CAP mode when the boot process completes.
  • Log in to your router running the DHCP server on your network, and find out what IP address the device has.
  • Either use a native Terminal, or the web based terminal next to the WebFig button, and connect to the device via shell.
  • The login banner will contain the current configuration set to CAP mode, and it will stop for a dialoge-question, to remove configuration with keypress of r or to continue with conforming configuration with any other key. Press enter.

With version 6.48.3 the step to confirm CAP mode became obsolete. New it is enough to set CAP mode via reset button after the update of packages.

Király István
  • 599
  • 5
  • 24