Hello!
I have one question. Im using RouterOS v6.43.12. I want to send out (egress) both untaged and taged traffic to the same interface (in bridge vlans section) by the same VLAN. So, I can then in other physical switch join this traffic to 2 different vlan groups. Can I do this? For ingress I anyway can use unlimited vlan (to send them all forward to destination untaged).
Have you read the links provided from the other post?
The examples show how to setup a single bridge.
create vlans with the bridge as the interface and all required subnet type info (ip address, ip pool, dhcp server and dhcp-server network)
How to setup bridge ports
How to setup interface bridge vlans
Which device are you using and can you post your config so far what you have setup?
/export hide-sensitive file-yourconfigfeb27
You dont get what I asked. I try to explain: Bridge → VLANs —> double click to some VLAN → now there is screen where is written “Taged” and “Untaged”. My question was - can I set there to both “taged” and “untaged” fields the same interface? …You can answer - Yes or No. (Yes, I can set there the same interface / No, I cant set).
The reason why I want to do this is to send out the same source traffic with taged and untaged, so in other physical switch I can join the same traffic with two different VLAN group.
With usual hardware switches I cant do this. There I can choose taged or untaged, but not both. But in RouterOS I find there is possibility to choose the same interface for both taged and untaged. I wasnt tried it in working system, in any case. But I see this possibility is there, I only wasnt pushed apply button right now. So, it looks like traffic switching not only between interfaces but also in the same interface. The same packets flow in the same interface doubled, separated by VLAN. Later, in other switch I can do with it what I want or separate them again.
Well without a diagram and without a config to look at its hard to understand what you want.
Thus I can only tell you my configuration.
I have two etheports for my LAN, eth2 and eth3,
Since eth2 goes to a managed switch and eth3 goes to a managed switch they are both trunk ports.
All the vlans running through these ports are tagged /interface bridge vlans…
the only thing untagged by default is the default pvid of 1.
If I used etherport 4 attached diretly to a device that was on vlanX, then I would
use the bridgeport setting to identify the ingress behaviour pvid=X accept only untagged frames
Use the interface bridge vlan to identify egress behaviour
tagged=bridge untagged=eth3 vlan-id=X
Therefore you need to know what a trunk port is and what an access port is and manage those appropriately for the MT unit and for any managed switches.
I have TP-Link managed switch (my central communication point). Behind it I have many ESXi hosts, physical firewalls, other computers. I set up my VLAN in a way where every single device have its own VLAN id. And also VM-s in ESXi-s. In ESXi I have NSX network and Mikrotik RouterOS VM. All traffic comes first through RouterOS and then goes through RouterOS virtual interfaces to special VM (through vDS, DLR bridge and logical switches). So, I can exactly control who can communicate with who, without matter of VLAN. All VLAN that interest me, RouterOS sends to VM-s untaged. Now every VM-s have also its own VLAN id and RouterOS send them out with taged. When VM communicate with other VM in the same ESXi host, RouterOS sends traffic to its virtual interface untaged (virtual interface have its own VLAN that dont influence at all with global VLANs, and ends untaged in both ends, other end is vDS portgroup). So, now I have even more specific need. When VM egress from ESXi host have its own VLAN id, I can resend traffic in my central physical switch to any port. To other ESXi host with taged and to some physical device untaged. But problem is now, still all physical switch ports dont have unique VLAN id, some still overlap. When I now send traffic to some port, the port becomes this VLAN member and other traffic in the same VLAN can now also send traffic to this port. This I dont want to let happen. But when I can send some VM traffic out from ESXi host with 2 different VLANs (taged and untaged and untaged becomes some VLAN through PVID), then I dont need to touch existing VLAN and dont need to add extra port to VLAN group. Instead I can use second VLAN and send it to required port in physical switch. Nobody else cant send traffic to this port. …So, its for me huge possibility enlargement by Mikrotik. No any other my known switch cant do this…Thats why I ask, “can I send from the same source, taged and untaged traffic to the same output/egress interface”.
So, seems you still dont know the answer to my question. First you told I must read manuals, but seems you havent readed it either.
Do you have a diagram to provide and also if available a config?
Why you interested about my diagram or config? Question is not at all about me and my configuration. Question is about RouterOS and its configuration. Imagine yourself as Mikrotik programmer and boss wants you to write manual for your programmed GUI. There is window, one field name is “taged” and other field name is “untaged”. Now you write manual, describe what is “taged” and what is “untaged”…but, dont forget, maybe someone want to use both and set them the same interface name. So, what then happens? Is it bug or is it normal behaviour. Person who write manual must see all possible combinations.
Oh okay this is a theoretical discussion and you do not have a MT router and dont have a configuration and dont have a network.
Well then, ask your professor at school 
I have tagged and untagged vlans on ports on my MT
What you wont find is a single port serving a device which has to be on a vlan but is unable to tag traffic (ie a PC or printer) and thus is an access port. On this access port will not be any tagged traffic. mixed with the tagging of the PC traffic, otherwise it would no longer be an access port.
If I have a mix of untagged traffic and tagged traffic, that is done on a trunk port
MT does not do hybrid ports.
Showing a diagram and posting a config are forms of communication so as to better understand the problem.
Unfortunately due to my lack of experience I do not have a clue of what kind of functionality you are trying to config the router to do…
So I ask for things that will help communicate your requirements.
My professor dont work in Mikrotik.
No, trunk port means any VLAN. Its different thing.
Are you at all seen this bridge vlans windows? Look into it - there is possibility to set into taged and untaged egress the same interface.
But you suggested me to read documentation. I expect you have readed it. And also I expect you have seen real RouterOS management web interface, bridge—> vlans window. I like myself documentations and I like when in documentation is also written about product, what is what. So, there is “taged” and “untaged” fields. I can set boths to the same interface. So, what it means?
Mikrotik is made this software, not I. I just asking what now happens. There is possibility to set them both to the same interface and I ask what now happens. Is this bug? Is this normal behaviour? Or RouterOS now makes BOOM and I must buy new RouterOS? What happens now?
Hopefully you can find a mikrotik forum in your own country that speaks your language and/or find a trained person in your country and they can assist.
I quite frankly have not understood much of what your saying and without a diagram and a config I cannot help further
I am in Mikrotik forum right now. btw Mikrotik is not Canadian company, as I see you are from Canadia. Do you know from what country is Mikrotik? Its from Latvia and in Latvia dont speaked english. From Canada I dont know any brand except PolarisMail service (its very good).
Well Im sure Latvia and Canada are very similar except your schnapps is way better whereas our Rye Whiskey is only to dream about in Latvia.
In that case you can probably visit MT and get better answers directly!!
Latvia is better, they have Mikrotik. First time I seen you are from Canada…Mikrotik forum admin from Canada, impossible.
My title says Guru, not Admin. Simple lesson in literacy.
Latvia I am sure is a beautiful country with friendly and warm people.
However, when the Russian Tanks come rolling over the horizon that will be gone in a flash, I am afraid and the world will lose another friend!
On a positive note, my driveway is big enough to accommodate a red car and I have a half bottle of Icelandic Schnapps I need help finishing. 
You are not guru. Guru know what happens when you send same source taged and untaged to the same interface. What is “guru” at all? What benefit “guru” can give me? Nothing…as I see in forum. But point is not even in there. The most important is logic (not hacking at all), stability, operative graphical overview and perfect documentation. I know Mikrotik documentation is not perfect. There almost not at all pictures of web GUI and no “tips” inside GUI. We dont live in past anymore. But no problems, surely they make it in future, it all takes time. I talk it because you suggested me to read documentation. There is no such talk in documentation, nothing about taged and untaged to the same interface. Surely I test this sometimes myselt. I just now dont have such requirement, but very soon I have. And I hope Mikrotik still allow me to send taged and untaged to the same interface. Because I dont see there any logical restrictions. And its huge technical possibilities enlargement, compared with all other brands switches. Its power feature.
I can refer here some Mikrotik unique features, not possible with other switches:
- VLAN ID translation from one id number to ther (natural feature in SwOS by ACL and in RouterOS there it can be implemented with two bridges)
- SNAT and DNAT for MAC addresses
- this taged and untaged to the same interface
- ingress filter for VLANs (this is implemented also by other brands but not in all) But example SwOS is very dynamic possibilities and all is implemented with GUI.
- modular desing in L2 and L3, almost all can be completed by yourself fit, “out from one and in to other”
- EoIP
…of course there is much more to write here, only all you dont use in the same time
I did not say I was a Guru in the definition sense, its what shows up next to my nick/avatar and I have no choice.
If they let me configure that or provide choices it would be KETBD “Knows enough to be Dangerous”
Why you want to be “dangerous”? I example dont. I believe you know enough …only except to send taged and untaged to the same interface, this you dont know, all others…yes.