I have no experience with "the new CAPsMAN" but for sure what you wrote is wrong for the original CAPsMAN... I tried it to see what it could do and it configured a situation with 3 SSIDs on untagged and 2VLANs (configured on the router) correctly.
I don't follow here...
We are talking about wap ax.
So " new" capsman.
I can create a much slave ssid as I want and all in different vlan.
So what's wrong ?
@fermat suggested that he could not have his wAP or cAP completely configured by CAPsMAN, and you @holvoetn seemed to agree with that, but in my experience with the old CAPsMAN that isn't the case. You can just reset the AP to CAP mode and be done with it, configure it with CAPsMAN on the router only. Or not?
1 Like
Hi, I did a reset with the call
/system reset-configuration caps-mode=yes keep-users=yes skip-
backup=yes
And now it works!!!
I disabled dhcp client again and gave the bridge a static IP. Seems still to work! 
Thank you so much!
Yes, that is another way of doing it. I gave the method with the reset button above.
1 Like
This is what I responded to.