CAPsMAN only provisions wireless interface ... and userman only sets VID for a oartivular usrr (much like static ACLs would). So I would expect that you have to configure uplink ethernet port as tagged member of a number of VLANs (all that might be used by userman), but likewise the wireless interface. Which is the problem since CAPsMAN can't do it entirely.
Some guesswork hence forth ... in provisioning rules, use action=create-enabled ... after a radio is provisioned, you can change settings, in particular you want to add (the created cap) interface as tagged member port to all necessary VLANs under bridge config (capsman may add it to single VLAN). And having action as indicated (versus create-dynamic-enabled) may allow for your custom config to survive reboots or other events (which otherwise affect cap configuration).
The above config has to be either done on CAPsMAN device (if capsman-forwarding is used) or on each CAP device (if local forwarding is used).
Some guesswork hence forth ... in provisioning rules, use action=create-enabled ... after a radio is provisioned, you can change settings, in particular you want to add (the created cap) interface as tagged member port to all necessary VLANs under bridge config (capsman may add it to single VLAN). And having action as indicated (versus create-dynamic-enabled) may allow for your custom config to survive reboots or other events (which otherwise affect cap configuration).
The above config has to be either done on CAPsMAN device (if capsman-forwarding is used) or on each CAP device (if local forwarding is used).
Statistics: Posted by mkx — Sun Mar 10, 2024 12:46 pm