Hi,
I’m installing an RB 2011iL using the Webfig GUI.
On some of the RouterBoard ports, I want to present one VLAN tagged (802.1Q), and one VLAN untagged. Is that supported?
Everything looks good on my untagged VLANs, but my tagged VLANs don’t pass any traffic to my switches 
Is there an example config somewhere that I could start from?
Many thanks!
on 2011, hybrid vlan config is only supported on ports 1-5
I suggest you to start with this tutorial. It is done using the new style VLAN-aware bridge, which works very fine. However it comes with penalty that it’s done in software and RB2011 with its relatively weak CPU will struggle. But when you get things running, you can convert the config to HW-offloaded one.
When it comes to that: there’s an urban legend running wild that AR8227 switch chip can’t do hybrid configuration (tagged and untagged on same port). 100Mbps ports (ether6-ether10) on RB2011 are hooked to such chip. This doesn’t affect the SW way mentioned at the begining of this post.
I don’t see him mention he uses the software way.
When using the switch chip config available in Webfig as well, indeed it is only possible on ports 1-5 to do a hybrid port.
He didn’t mention the way he’s doing it at all.
The tutorial is nice and IMHO helps to understand how things could/should be setup (many people don’t understand the basics when first trying to setup VLANs and thrn things go haywire … I was in the same boat once as well). So I suggested an easier way of getting things done … with the ceveat I also mentioned. If OP is more experienced in ROS (I may well underestimate his abilities and if this is the case, I appologise), then my second part should help (indeed @CZfan was quicker posting that information).
Thanks guys! You’re right, I have no experience with ROS… More with Cisco, pfSense, etc.
Maybe WebFig is a little confusing, so the CLI may be best.
Thanks for the link to the tutorial - nice to have some complete examples!
I also found a Wiki section about hybrid ports: https://wiki.mikrotik.com/wiki/Manual:Interface/Bridge#VLAN_Example_.232_.28Trunk_and_Hybrid_Ports.29
So I have enough info to go on with now 
All 3 UI variants available (CLI, WebFig and WinBox) are complete functionality wise … so you can use the one which is the most natural to you. They all more or less follow the same config layout so it’s not hard to follow CLI example while clicking through GUI.
CLI has one big advantage when it comes to this forum: it’s a convenient way to show config (either existing config or command to add or fix something) while GUIs lack the needed compactness …
Well but indeed (contrary to some other platforms) there is no need at all to remain within a single config UI.
You can use webfig or winbox when you like, then use CLI to export the config in CLI form and show it here.
There is no advantage to use CLI all the time. It has advantages like compact export and easy copy/paste of blocks of config,
but GUI is usually easier to use.
What matters is not the config UI that you used, but the method you used to add the VLAN. There are several method to do
that (VLAN subinterface on an ethernet port or bridge, switch config, bridge VLAN config) just as in Cisco routers with builtin switch.
Different methods have different properties and advantages.
We cannot tell you much until you explain us what you did.