Remote CAP in 7.13 using CAPsMan 1 and 2

RouterOS Wireless Networking
21

New capsman explicitly doesn’t support provisioning local devices (MT is very clear on that). Old capsman apparently did[*] support that but MT (AFAIK) never really advertised this as a feature … so it might be an unsupported glitch they just let working all these years.

[*] MT probably had to touch the old capsman code in order to allow old and new capsman coexist on same device. Which may have broken the previously undocumented “feature”. Anyone concerned by this “breakage” should open a support ticket with mikrotik support and their responses should then clear these dilemmas. Either MT will fix the legacy capsman or they’ll say it wasn’t supposed to work like this in the first place.

22

This was actually very much unclear to me when I was setting up new CAPsMAN for the first time. I can’t even find a mention of local interfaces with regards to CAPsMAN in the docs.


MikroTik may have never advertised this as a feature, but they did put a firewall entry into default config seemingly just for local CAPsMAN to work, the one with the comment “defconf: accept to local loopback (for CAPsMAN)”. They may have done this to dissuade unwary forum users from just turning off “drop all input not from LAN” rule. But still.

23

I found this table helpful when trying to figure out the situation with new/old CAPsMANs..

http://forum.mikrotik.com/t/7-13-wireless-package-split-question/172049/1

24

Unfortunately I have got the same like issue:
setup:

  • RB4011iGS+5HacQ2HnD with wireless package for old 2.4Gz
  • CAP AC with qcom-ac
  • CAP AX.

During the setup adjustments old capsman (127.0.0.1) was switched off and new CAPsMAN worked well and even CAP AX was provisioned, then old was switched on, and at certain point of new capsman adjustments something broke.

Now both CAPs (AC and AX) report that their interfaces are managed by new CAPsMAN, new CAPsMAN lists CAPs correctly via L2, but the “Wifi” for new wave2 CAPs view at RB4011iGS+5HacQ2HnD says “no connection to CAPsMAN” and provisioning does not work anymore , although all information about Radio and other settings displayed correctly.

More than that, if I touch new CAPsMAn configuration the old stops provisioning and I have to change something in settings of old capsman in order to make it working again.
Both CAPsMans have certificates, and I tried to lock CAPs to corresponding CAPsMANs - it does not help.

Do both CAPsMANs have conflict somewhere? Any idea how to check if needed services are running correctly?

25

After some months, I still cannot make it work.

Any successful story to share? Remote CAP means CAP is connected via internet/WAN not LAN

26

Remote CAP means “CAP is other device”. “Local CAP” = CAPsMan and CAP on same device.

27

Remote CAP means outside LAN and connects via internet.

CAP in other devices connected via LAN works in CAPsMan 2

In legacy CAPsMan, I have made it work but never shows up as remote radio

28

Your CAPS that can’t connect try to reach your CAPsMAN server via WAN? Then check your firewall rules?

29

I try two routerOS device on the same network - one with legacy wifi; connect and work with CAPsMan 1; the other is a AX3 could not connect

Both point to the same IP address and I open up UDP ports 5246 and 5247

30

If issue persists while 7.14.2 is installed on CAPs and CAPsMAN, please create supout.rif files on involved devices and share the files with us support@mikrotik.com
This issue should be resolved in latest versions.

31

I use both 7.15.beta9 in my x86 as CAPsMan 1 + 2 and AX3 as CAP. From the AX3 log, it shows timeout. Firewall allows both UDP ports 5246 and 5247 in and out.

In the same remote network, another CAP connecting to x86 CAPsMan 1 works. I just put one device in the remote network

32

An update,

I brought the AX3 back and installed in the LAN, it worked with the x86 device that has both CAPsMAN 1 and 2. Configuration was not that difficult.

Now wait to see if the same AX3 works again in remote site

33

Now at remote side, AX3 reports timeout or No suitable CAPsMan found

34

How is connection from remote site to network where capsman controller is located ?
Ideally it should be in the same L2-segment. If that’s not the case, you need to specify the IP address where it needs to look for the controller.

If IP connection is possible, have you tried to specify controller ip directly in that cap device ?
You could also try to put an EOIP connection over remote/local environments, connect that EOIP on both bridges and hence mimicking an L2 connection.

35

What I do is on different public IPs for CAPsMan and CAP

In CAPsMan 1, it can be done as specifying the CAPsMan public IP in the CAP menu of AP and the firewall of CAPsMan allows UDP 5246, 5247. It works well all along including in the same city and overseas via internet.

In my case, CAPsMan 2, I prepare the same information in the CAP menu of the AX3 AP. What I can see in AX3 log, it can locate the CAPsMan via public IP, but error in connection due to timeout.

Anyway, I raise a support ticket as suggested by Guntis

36

I am now able to create a EOIP bridge to link up two devices via internet. CAPsMAN v2 can position the CAP which is a AX3 but I could never get an ip address from CAPsMAN device DHCP server

I have been using 7.19.2 firmware and wonder if anyone has successful story