CAPsMAN and dynamic interface names

[sputniki]

Is there any way to have CAPsMAN controlled interfaces with static interface names?
It’s difficult to monitor wireless traffic of wireless interfaces with snmp because if.index changes every time an CAPS-AP reconnects to CAPsMAN… :-/

[uldis]

We already have such option, from:

http://wiki.mikrotik.com/wiki/Manual:CAPs_Manager#Radio_Provisioning

create-disabled - create disabled static interfaces for radio. I.e., the interfaces will be bound to the radio, but the radio will not be operational until the interface is manually enabled;
create-enabled - create enabled static interfaces. I.e., the interfaces will be bound to the radio and the radio will be operational;
create-dynamic-enabled - create enabled dynamic interfaces. I.e., the interfaces will be bound to the radio, and the radio will be operational;
none - do nothing, leaves radio in non-provisioned state;

[mdkberry]

@uldis

create-enabled - create enabled static interfaces. I.e., the interfaces will be bound to the radio and the radio will be operational;
create-dynamic-enabled - create enabled dynamic interfaces. I.e., the interfaces will be bound to the radio, and the radio will be operational;

and the difference between these settings is…?

[bajodel]

@mdkberry

@uldis

create-enabled - create enabled static interfaces. I.e., the interfaces will be bound to the radio and the radio will be operational;
create-dynamic-enabled - create enabled dynamic interfaces. I.e., the interfaces will be bound to the radio, and the radio will be operational;

and the difference between these settings is…?

Static/dynamic ..here is the difference

Static interfaces will not be auto provisioned again (only manual intervention)
Dynamic ones are provisioned at every boot/connection