Hi guys,
Appreciate if you could help on the following issue:
I have a trunked link from a DGS-1210-16.
The link contains VLAN 1/20/50.
I have enabled tagging on port 11 for the above VLANs on the DGS.
This is in turn connected to port 5 of the RB250GS - i’ve created the necessary VLANS on the mikrotik with port 5:
(Under VLANs) - 1/20/50 all checked.
Under VLAN tab, Ingress is enabled / default VLAN ID 1. Egress set to “Add if missing”
Now comes the issue:
I have got a TP Link WA901ND on OpenWRT running on 2 SSIDs (VLAN 1 / 50)
This is connected to port 4 - For some odd reason I cannot link the AP to RB250GS - it either works on either VLAN 1 or 50 but not both.
Under VLANs tab - VLAN 1 & 50 are checked for port 4.
I’m not sure what else to try/do after this.
Config of this AP works fine when connected to the DGS - I can link to either SSID without issue - linking to 2 different subnets.
Appreciate your input as I’m truly stumped.
The current RB switches can only output tagged OR untagged traffic.
Your vlan 1 is tagged, while the AP probably expects vlan 1 to be untagged.
Hey! Thanks for the prompt reply!
I can’t afford to put 2 APs - its gonna look damn silly 
Any workaround for this situation? Would appreciate some solution.
Hello,
openwrt can be configured to use tagged vlan1 and additional vlans, i have it working flawlessly on my 1043ND TP-Link with a vlan trunk to a RB250GS
I can not help you directly, as you use a different hardware, here is my /etc/config/network file for the vlans. As far as i remember, port 0 ist the wan port, which i use for the trunk. (and 5 is the trunk port internally connected to the cpu).
BUT Please, check carefully, i do not waranty anything 
Ronny
config switch
option reset '1'
option enable_vlan '1'
option enable_vlan4k '1'
option name 'switch0'
config switch_vlan
option vlan '6'
option ports '0t 5t'
option device 'switch0'
config switch_vlan
option vlan '1'
option ports '0t 1 2 3 4 5t'
option device 'switch0'
Thanks for the config.
Unfortunately it doesn’t work on my WA901ND.
Will have to look for another solution - found another thread that highlighted a similar issue as mine.
Its generally a switch chip limitation. 