I don't know exactly what are you asking in this post. One port can be 'tagged' and 'untagged' at the same time for different VLAN-id. Hybrid port is the name. BUT not for the SAME VLAN-ID
A hybrid port can be useful in a construction where you have several nodes connected in a dumb switch (not vlan aware) and you need to use it for trunking and for access at the same time. In my opinion, finding it on a network is more a workaround or a patch that should be avoided.
Consider this scenario: R1 ether5 <-> ether4 R2 ether5 <-> dumb switch <-> ether4 R3
R1:
- ether1 as acess port for VLAN10
- ether2 as acess port for VLAN20
- ether3 as acess port for VLAN30
- ether4 and ether5 trunk port for VLAN 10. 20 and 30
R2:
- ether1 as acess port for VLAN10
- ether2 as acess port for VLAN20
- ether4 trunk port for VLAN 10. 20 and 30
- ether5 trunk port for VLAN 10, 20 and access port for VLAN 30 (hybrid port)
R3:
- ether1 as acess port for VLAN10
- ether2 as acess port for VLAN20
- ether3 as acess port for VLAN30
- ether4 and ether5 trunk port for VLAN 10. 20 and 30
Here you have the export for each router:
/system identity set name=R1
/interface bridge
add name=bridge1 vlan-filtering=yes
/interface bridge port
add bridge=bridge1 interface=ether1 pvid=10
add bridge=bridge1 interface=ether2 pvid=20
add bridge=bridge1 interface=ether3 pvid=30
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5
/interface bridge vlan
add bridge=bridge1 tagged=ether4,ether5 untagged=ether1 vlan-ids=10
add bridge=bridge1 tagged=ether4,ether5 untagged=ether2 vlan-ids=20
add bridge=bridge1 tagged=ether4,ether5 untagged=ether3 vlan-ids=30
Export for R2:
/system identity set name=R2
/interface bridge
add name=bridge1 vlan-filtering=yes
/interface bridge port
add bridge=bridge1 interface=ether1 pvid=10
add bridge=bridge1 interface=ether2 pvid=20
add bridge=bridge1 interface=ether4
add bridge=bridge1 interface=ether5 pvid=30
/interface bridge vlan
add bridge=bridge1 tagged=ether4,ether5 untagged=ether1 vlan-ids=10
add bridge=bridge1 tagged=ether4,ether5 untagged=ether2 vlan-ids=20
add bridge=bridge1 tagged=ether4 untagged=ether5 vlan-ids=30
Export for R3:
/system identity set name=R3
/interface bridge
add name=bridge1 vlan-filtering=yes
/interface bridge port
add bridge=bridge1 interface=ether1 pvid=10
add bridge=bridge1 interface=ether2 pvid=20
add bridge=bridge1 interface=ether3 pvid=30
add bridge=bridge1 interface=ether4
/interface bridge vlan
add bridge=bridge1 tagged=ether4,ether5 untagged=ether1 vlan-ids=10
add bridge=bridge1 tagged=ether4,ether5 untagged=ether2 vlan-ids=20
add bridge=bridge1 tagged=ether3 untagged=ether4,ether5 vlan-ids=30
If you connect a computer in dumb switch, it will be able to ping the computer connected on R1-ether3 BUT won't be able to ping the computer connected on R3-ether3. R3 can't receive tagged packets for vlan-id 30 because traffic egressing from R2 that belongs to vlan-id30 is untagged in ether5.
A port can't be at the same time tagged and untagged for the same vlan-id. For this scenario to 'work' it should be possible to do this on R2 (but it is not possible):
[admin@R2] > interface bridge vlan add bridge=bridge1 vlan-ids=30 tagged=ether4,ether5 untagged=ether5
failure: interface cannot be in tagged and untagged at the same time
So quoting what you asked:
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).
I agree with Anav when he said... "you should explain what are you trying to get"... or maybe better, you can TRY it on a mikrotik so you would realise that "failure: interface cannot be in tagged and untagged at the same time"