I have a router connected to the uplink port, with vlan 10,20 and 99. I can ping and ssh the router on all gateways 192.168.10.1, 192.168.20.1 and 192.168.99.1 from the serial console on CRS326-24G-2S+, but if I connect a pc to another interface with untagged vlan, I cannot get a ip from dhcp server on router, or if I set ip manually with gateway address 10.1 or 20.1 I cannot ping the gateway.
Two pc on each untagged vlan port on the same vlan seems to work though, so something as worked.
I have even tested with adding static routes /ip route add distance=1 gateway 192.168.20.1, without any luck.
I have created a interface on the router without vlan. When I connect to this interface with a pc I can both ping and ssh to the switch that is connected to the uplink interface on the rounter. So the routing from native vlan to vlan 99 seems to work as well as traffic from one interface to another. For some reason the other way is not working though.
A Mikrotik bridge has two roles, one is like a switch connecting a number of interface ports together and the other like an interface port connecting traffic between the switch and serives running on the CPU, see http://forum.mikrotik.com/t/routeros-bridge-mysteries-explained/147832/1 for an in-depth explanation.
Generally on a Mikrotik which is being used as a switch you do not require multiple /interface vlan entries, typically you would have one for remote management access to the Mikrotik, they are not required for VLANs which are being switched between the external interface ports.
As ever, post the output of /export hide-sensitive from a terminal window in a code block (the icon above the message box when posting).
You need the to tag the other VLANs on the bridge trunk ports too
/interface bridge vlan
add bridge=bridge1 tagged=ether24,sfp-sfpplus2 vlan-ids=10
add bridge=bridge1 tagged=ether24,sfp-sfpplus2 vlan-ids=20
add bridge=bridge1 tagged=bridge1,ether24,sfp-sfpplus2 vlan-ids=99