as @mkx already said, unless we see your configuration we can only guess...
Other than that, @anav Capsman is really great
Caps-man... Absolutely awesome in concept. In form and moving how express and admirable! In action how like an angel, in apprehension how like a god!
Got carried away there.
But ANAV is right about the complaints. Until Mikrotik can get wifi down... An incredibly powerful and elegant control system... Doesn't really matter.
Or as my cohorts say when they watch me grind my teeth over Mikrotik wireless problems on our jobs...
(Looking at caps-man over my shoulder)
"Holy S--t. Can that control a good radio?"
Sadly the wifi wave 2 drivers I used on the Audience that made it work so much better... Are not compatible with this.
"Well what about our other WAPs?"
Nope it's Mikrotik access point control only.
(It wasn't a completely unreasonable question. We do have things that bring together control or configurations of multiple manufactures.)
We moved back to using Ruckus for our wireless exclusively. And the bleeding stopped.
We keep bringing in other manufactures to make sure we are staying on top of things... But I stare over at my stack of cap ACs... It's they have been reduced to "this is why you have to Test devices that only have 2.4 radios in busy environments."
But back to how too.
Put the IPs and DHCP severs on VLANs on the bridge. Use the tag on the SSID.
That's usually all you need to connect those things.
Well using local-forwarding and client to client forwarding.
"It ain't what you don't know that gets you into trouble. It's what you know for sure that just ain't so."