On 7.13.1 wifi capsman seems not to match Audience radios by band-supported
Audience and cAP ax are on newest 7.13.1.
Capsman is running on cAP ax, Audience is CAP.
Capsman matches local radios by band-supported.
If band-supported is specified no provisioning is done from Audience. Interfaces are created and disabled, and not provisioned. Once band-supported is removed provisioning is working.
I believe the ‘supported-bands’ are AND-gated. Meaning that, with how you configured it, the radio will be provisioned with cfg5 configuration if, and only if, it supports 5GHz-A band AND 5GHz-N band AND 5GHz-AC band AND 5GHz-AX band. It needs to support all of them to get provisioned. Audience does NOT support AX.
Try and change it to ‘supported-bands=5ghz-a’. It’s the oldest 5GHz standard. If you have ax devices on the network, you might want to set up a second rule and place it before this one to catch them with ‘supported-bands=5ghz-ax’. But that probably makes more sense for ‘action=create-dynamic-enabled’ rather than for ‘action=create-enabled’.
Yes, I have several cAP AX and also wAP AC (arm) and for ax devices I select AX and for ac devices I select 5GHz-AC.
This mean you have to build different configuration and provision based on MAC address.