QUOTE(rioven @ Feb 18 2017, 05:46 PM)
I'm still out of idea why the traffic stops when bridge wlan and ether1 (so im leave this part until i got better idea..sorry). anyway let me know if any progress of wlan, did use tag solve the problem or not

Hi rioven, the problem with the bridge traffic stopping seems to be due to STP changes in 6.38. I'm using 6.38.1. Quite a few posts on the Mikrotik forums about it. I think 6.39RC solves it but I haven't tried yet.
QUOTE(rioven @ Feb 16 2017, 02:42 AM)
Might not best solutions, but it may work (this is at wlan1 setting, wireless tab)
change "vlan mode=use tag, vlan-id=50"
I have to keep wlan1 untagged. If I tag it as 50, it doesn't work. If No Tag then it works. wlan1 is a port in bridge-vlan50.
QUOTE
/ip dhcp-client
add default-route-distance=0 dhcp-options=hostname,clientid disabled=no interface=ether1<--not sure will grab ip from ether1, if change to vlan50..maybe
I removed this. I don't need an IP address on the RB#2 anyway. Before I removed it, I did some testing, the DHCP client works only on ether1 and not on bridge-vlan50 nor on vlan50.
QUOTE
/interface bridge add name=bridge1
/interface bridge port
add bridge=bridge1 interface=wlan1
add bridge=bridge1 interface=ether1
# switch1-cpu
set 11 default-vlan-id=50 vlan-mode=secure<--this config, im not that sure, i maybe change vlan-mode=check and remove default-vlan-id
edit: change to better answer, twice

Haven't tested the switch1-cpu but current config switch1-cpu is working so I just leave it be for now.