Unknown interface in CAPsMAN Access list

RouterOS General
1

Hello,

I have very annoying issue with CAPsMAN’s access list. Every reboot of cap devices, or some disturbance to it when the interface is added again, the rule on access list shows interface “unknown”. The rule needs to be fixed manually to work as expected. Is there a way to make it permanent?

Thanks

2

Have you tried? :

A. “Open” this Interface in Winbox for editing
B. Make copy of it with “Copy” button
C. Name this copy of interface and save.

3

The issue is not with the interface but access-list. Rule which I made:

 mac-address=A0:20:A6:15:D7:C1 interface=ap_piwnica-1-1 ssid-regexp="" action=accept

After restarting remote cap, the rule is now:

 mac-address=A0:20:A6:15:D7:C1 interface=*29 ssid-regexp="" action=accept

So It will not work of course until I fix the rule to have “interface=ap_piwnica-1-1”.

4

Seems that name of the interface is not remebered.
Do you have “piwnica-1-1” interface made with steps A, B, C ?

5

The interface is created thru provisioning:

 0   radio-mac=00:00:00:00:00:00 hw-supported-modes="" identity-regexp="" common-name-regexp="" ip-address-ranges="" action=create-dynamic-enabled master-configuration=eap-config
     slave-configurations=appliance-config,guest-config name-format=prefix-identity name-prefix=""
6

I am having the exact same problem with my access list.
This most be a bug we need to report to Mikrotik
I haven’t tried setting the interfaces so they aren’t created dynamically to see if the issue persist…
But any time i restart my router the field for the interface, inside an access list will say “unknown” as if Capsman isn’t remembering the interfaces for the access list records

7

Can something be done with this issue? Maybe I can help with collecting some logs. This issue causes the Access List functionality to be complettely useless.

8

I have same issue. After each reboot I need change ACL from unknown to right interface. Anybody found any solution?

9

As a workaround I am just running this script every minute that checks if my device have correct rule in access-list:

:if ( [/caps-man access-list get [find mac-address=XX:XX:XX:XX:XX:XX] interface] != "ap_name" ) do={ /caps-man access-list set [find mac-address=XX:XX:XX:XX:XX:XX] interface=ap_name  }

Dont know if nobody uses access lists or just I am doing something so wrong that there is so little feedback about this.

10

This is to be expected with dynamic provisioning (/caps-man provisioning action=create-dynamic-enabled).

Use action=create-enabled instead.