I`m using a CRS125-24G to switch my network.But i seem to have some issues with assigment of vlans 
\
- ether1 is the master interface
- ether2-24 are slave interfaces of the master interface
I have a Cisco router which gives me a IPTV vlan (vlan4) so i created a vlan 4 on the switch and connected the router to Ether08 of the switch.
VLAN4 is only assigned to ports ether01/02/04/05/08/13
VLAN110 is assigned to all other ports
Why do i still see vlan110 on port ether08 because this is giving me strange network issues
The following config is used on a Cisco 2940 switch which is also connected to the CRS. This config is working fine to get the IPTV vlan on a client connected to the CRS. However when i connect the Cisco router directly to the CRS i cannot get vlan 4 to pass the port.
interface FastEthernet0/5
description "VLAN4 vanaf Cisco877VA"
switchport access vlan 404
switchport trunk native vlan 404
switchport trunk allowed vlan 4
switchport mode trunk
mdix auto
spanning-tree portfast trunk
end
Note: VLAN404 is used do get rid of the untagged traffic which i do not want to use. I only want to allow tagged vlan 4 traffic to enter the network
I think i found a bug..
Switch --> VLAN --> In. VLAN Tran
I have one rule to set all the untagged traffic to bogus vlan 400
Ports: Ether8
Service VLAN Lookup for: any
Customer VLAN Lookup for: any
Customer VID: 0
New Customer VID: 400
And the IPTV is not working but a soon as i add the following rule it is working fine
Ports: Ether8
Service VLAN Lookup for: any
Customer VLAN Lookup for: any
Customer VID: 4
New Customer VID: 4
And as soon as i disable this rule the signal stopsā¦
This is not a bugā¦see example 2 (Trunk and Hybrid Ports) which is exactly the type of link you are trying to use. Make sure you are properly setting egress VLAN tagging as well.
http://wiki.mikrotik.com/wiki/Manual:CRS_examples
I think i made the setup correctly 
[admin@sw04] /interface ethernet> print
Flags: X - disabled, R - running, S - slave
# NAME MTU MAC-ADDRESS ARP MASTER-PORT SWITCH
0 R ether01-Trunk crs1.kmp1 1500 xxxxx:AE enabled none switch1
1 ether02-Trunk crs2.kmp1 1500 xxxxx:AF enabled ether01-Trunk crs1.kmp1 switch1
2 RS ether03-PP18-FreeNAS 1500 xxxxx:B0 enabled ether01-Trunk crs1.kmp1 switch1
3 RS ether04-Cisco2940 1500 xxxxx:B1 enabled ether01-Trunk crs1.kmp1 switch1
4 RS ether05-PP04-CAP02-Slaapkamer 1500 xxxxx:B2 enabled ether01-Trunk crs1.kmp1 switch1
5 RS ether06-CAP01-Woonkamer 1500 xxxxx:B3 enabled ether01-Trunk crs1.kmp1 switch1
6 S ether07-PP08-Onbekend 1500 xxxxx:B4 enabled ether01-Trunk crs1.kmp1 switch1
7 RS ether08-TVVLAN-877VA-Fa2 1500 xxxxx:B5 enabled ether01-Trunk crs1.kmp1 switch1
ports=ether08-TVVLAN-877VA-Fa2 service-vlan-format=any customer-vlan-format=any customer-vid=0 new-customer-vid=400 pcp-propagation=no sa-learning=yes
[admin@sw04] /interface ethernet switch egress-vlan-tag> print
4 4 ether04-Cisco2940
ether05-PP04-CAP02-Slaapkamer
ether08-TVVLAN-877VA-Fa2
ether13-PP13-Dune Kantoor
But it only works after adding this one
ports=ether08-TVVLAN-877VA-Fa2 service-vlan-format=any customer-vlan-format=any customer-vid=4 new-customer-vid=4 pcp-propagation=no sa-learning=yes
If VLAN 4 is coming in tagged then you would need that config in order to distinguish between tagged and untagged traffic, so that is correct.
We did a presentation on the CRS and VLAN rewrites at the 2015 USA MUM in Miamiā¦you might find it helpful.
http://www.mikrotik.com/download/share/Mikrotik_VLAN_Rewrites_MUM_2015_KevinMyers_4_by_3.pdf
The data should be coming in as tagged vlan 4, this is also the rule that is matching.
āIf traffic comes in tagged with vlan 4 then tagged the traffic with vlan 4ā
For now it is working for me and i will put the issue in the refrigerator. I will now wait for IGMP Snooping on the CRS platform.
Glad itās working for youā¦I guess iām still trying to figure out what the āissueā you are having is exactly if it is functioning.
One thing that may help clear things up for you is to realize that Cisco switches deal with VLAN tags the way most enterprise switches do and that is by building a trunk and allowing VLANs across it with a native VLAN defined.
The CRS handles VLANs more like a Metro Ethernet switch where every VLAN is matched and re-tagged according to a policy (even if it is not translating or otherwise altering the integer value of the tag) - itās more complicated, but it also provides more flexibility.