Capsman manager running on RB2011, but no CAP on it

As the title goes, I have successfully set up CAPSMAN on RB2011 plus 2 CAPs (RB4011 is CAP1 and RB952 is CAP2).

All is perfect, except I cannot make RB2011 act as CAP3 - it has wi-fi, but only the guest wi-fi…and in CAPSMAN settings only cap interfaces for remote CAPs are shown, no RB2011 wi-fi there.

I will try to upload some printscreens to make clearer the issue, but basically what I need is to have my CAPSMAN manger (RB2011) act as a CAP at the same time as being manager.

Interfases on RB2011, my capsman manager. It shows wlan1 as being managed by capsman, but when I go to capsman, I have there only cap interfaces of my 2 remote caps.
InterfaceList.jpg

when I check wireless Tab on my RB2011, CAP is enabled on RB2011…

I am at total lost on what else to check to make it work…could it be that when I reset the RB2011 I chose a quick setting of “Home Mesh”?..maybe the problem lies there?
wireless2011.jpg

In your local CAP settings, remove discovery interface and add 127.0.0.1 as CAPsMAN address.
-Chris

Many thanks Chris for your suggestion

Like so? Remove discovery interface - I just closed that line in CAP settings, or you mean I need to find a list of interfaces where Discovery interface is like an entry ina list and select “remove” option?

With the changes made on the printscreen, I still have no changes that I can see.
Andy
rmDI.jpg

could it be that the main fault is in my initial setting of CapsMan manager RB2011 - I have used quick set option of “Home Mesh” - is this correct?
quickset.jpg

Are there any other suggestions? I cannot solve the problem yet

the solution offered above did not work, so the problem still persists :frowning:

The problem is in the firewall: you need to add a rule to the input chain that will allow src-address-type=local

Thank you for this solution, I will give it a try. If it is not too much to ask, can you please tell me the command for this? Sorry to ask this, but I am very new to this, will probably do it wrong otherwise

/ip firewall filter action=accept chain=input src-address-type=local

Thank you so much! But I tried this (even with the guidance from wiki manual) can’t make it work. Could there be a mistake in the syntax? It seems in line with the wiki manual..but the commands are not accepted.
Screenshot from 2019-11-12 21-40-36.png

by the way, these are the rules which were previously on the router:
Screenshot from 2019-11-12 22-51-52.png

I missed the “add”.
Sorry about that :slight_smile:

/ip firewall filter add action=accept chain=input src-address-type=local

And don’t forget to place it higher than the last “drop” rule.

I noticed that “add” was missing (from the wiki manual), so I tried it with “add” as well. It does not work, but I think the problem is I add it after the “drop” rule. I don’t know how to add it above the last rule (which is “drop” on my router).

Shall I disable the “drop” rule, add the rule you suggested and then enable the “drop” rule again?

Just drag it higher in the GUI :slight_smile:

wow!!! U-N-B-E-I-L-I-V-A-B-L-E!!!

YOU are the man, you actually did it!!!. To be honest with you I thought I shall live with this as it is, because everything was so complicated and every step I tried did not improve things, but you actually knew what you are talking about!


THANK YOU! спасибо огромное!

Now with capsman working as it should, I can focus on channels selection, signal tweaking etc (Wiki manual, here I come :smiley: )

wow!!! U-N-B-E-I-L-I-V-A-B-L-E!!!

YOU are the man, you actually did it!!!. To be honest with you I thought I shall live with this as it is, because everything was so complicated and every step I tried did not improve things, but you actually knew what you are talking about!


THANK YOU! Vielen Dank!

Now with capsman working as it should, I can focus on channels selection, signal tweaking etc (Wiki manual, here I come :smiley: )

Thank you very much to this wonderful community for the support offered!

You really made my day!

You are welcome! :smiley: