# Bridge VLANS hEX S v7.2rc4 /interface bridge vlan print

**URL:** <https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544>\
**Category:** Beginner Basics\
**Created:** [March 15, 2022, 2:18am UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544 "2022-03-15T02:18:56Z")\
**Posts on this page:** 12\
**Page:** 1

<div class="post-metadata">

**Author:** ![Buckeye](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/buckeye/32/2242_2.png) [@Buckeye](https://forum.mikrotik.com/u/Buckeye)\
**Post date:** [March 15, 2022, 2:18am UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/1 "2022-03-15T02:18:56Z")

</div>

I don’t understand why Bridge VLANS hEX S v7.2rc4 **/interface bridge vlan print** is not showing all vlans that are displayed by export.

Specifically this portion of export

/interface bridge vlan  
add bridge=BR-SW \*\*tagged=\*\*BR-SW, **ether4-BR-SW\_U10\_T241** untagged=ether3-BR-SW-U241 **vlan-ids=241**  
add bridge=BR-SW tagged=BR-SW **untagged=ether4-BR-SW\_U10\_T241 vlan-ids=10**

![export and print.png](https://data-discourse.cdn.mikrotik.com/original/3X/6/b/6bf01a50c028c1a5f7adc29028de06bd0655dc99.png)  
Why doesn’t the bridge vlan display in winbox show **ether4-BR-SW\_U10\_T241** in either tagged or untagged?

Does anyone see what I am doing wrong?

```plaintext
[demo@MikroTik] > /interface export compact
# mar/14/2022 20:23:17 by RouterOS 7.2rc4
# software id = ***********
#
# model = RB760iGS
# serial number = *********
/interface bridge
add admin-mac=DC:2C:6E:CA:FE:F2 auto-mac=no comment=defconf name=BR-SW vlan-filtering=yes
/interface ethernet
set [find default-name=ether1] name=ether1-WAN
set [find default-name=ether2] name=ether2-BR-SW-Base-U1
set [find default-name=ether3] name=ether3-BR-SW-U241
set [find default-name=ether4] name=ether4-BR-SW_U10_T241
set [find default-name=ether5] name=ether5-off_bridge_wrk
/interface vlan
add interface=BR-SW name=vlan10 vlan-id=10
add interface=BR-SW name=vlan241 vlan-id=241
/interface list
add comment=defconf name=WAN
add comment=defconf name=LAN
/interface wireless security-profiles
set [find default=yes] supplicant-identity=MikroTik
/interface bridge port
add bridge=BR-SW comment=defconf interface=ether2-BR-SW-Base-U1
add bridge=BR-SW comment=defconf frame-types=admit-only-untagged-and-priority-tagged interface=ether3-BR-SW-U241 pvid=241
add bridge=BR-SW comment=defconf interface=ether4-BR-SW_U10_T241 pvid=10
add bridge=BR-SW comment=defconf interface=sfp1
/interface bridge vlan
add bridge=BR-SW tagged=BR-SW,ether4-BR-SW_U10_T241 untagged=ether3-BR-SW-U241 vlan-ids=241
add bridge=BR-SW tagged=BR-SW untagged=ether4-BR-SW_U10_T241 vlan-ids=10
/interface list member
add comment=defconf interface=BR-SW list=LAN
add comment=defconf interface=ether1-WAN list=WAN
add interface=ether5-off_bridge_wrk list=LAN
add interface=vlan10 list=LAN
add interface=vlan241 list=LAN
[demo@MikroTik] >

[demo@MikroTik] > /interface/bridge/print 
Flags: X - disabled, R - running 
 0 R ;;; defconf
     name="BR-SW" mtu=auto actual-mtu=1500 l2mtu=1596 arp=enabled arp-timeout=auto mac-address=DC:2C:6E:7B:10:F2 
     protocol-mode=rstp fast-forward=yes igmp-snooping=no auto-mac=no admin-mac=DC:2C:6E:CA:FE:F2 ageing-time=5m 
     priority=0x8000 max-message-age=20s forward-delay=15s transmit-hold-count=6 vlan-filtering=yes ether-type=0x8100 
     pvid=1 frame-types=admit-all ingress-filtering=yes dhcp-snooping=no 
[demo@MikroTik] > /interface/bridge/port/print
Flags: I - INACTIVE; H - HW-OFFLOAD
Columns: INTERFACE, BRIDGE, HW, PVID, PRIORITY, PATH-COST, INTERNAL-PATH-COST, HORIZON
# INTERFACE BRIDGE HW PVID PRIORITY PATH-COST INTERNAL-PATH-COST HORIZON
;;; defconf
0 H ether2-BR-SW-Base-U1 BR-SW yes 1 0x80 10 10 none   
;;; defconf
1 H ether3-BR-SW-U241 BR-SW yes 241 0x80 10 10 none   
;;; defconf
2 IH ether4-BR-SW_U10_T241 BR-SW yes 10 0x80 10 10 none   
;;; defconf
3 I sfp1 BR-SW yes 1 0x80 10 10 none   
[demo@MikroTik] > /interface/bridge/vlan/print
Flags: D - DYNAMIC
Columns: BRIDGE, VLAN-IDS, CURRENT-TAGGED, CURRENT-UNTAGGED
# BRIDGE VLAN-IDS CURRENT-TAGGED CURRENT-UNTAGGED    
0 BR-SW 241 BR-SW ether3-BR-SW-U241   
1 BR-SW 10 BR-SW                               
2 D BR-SW 1 BR-SW               
                                      ether2-BR-SW-Base-U1
[demo@MikroTik] > /interface/vlan print
Flags: R - RUNNING
Columns: NAME, MTU, ARP, VLAN-ID, INTERFACE
# NAME MTU ARP VLAN-ID INTERFACE
0 R vlan10 1500 enabled 10 BR-SW    
1 R vlan241 1500 enabled 241 BR-SW    
[demo@MikroTik] >

```

---

<div class="post-metadata">

**Author:** ![Buckeye](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/buckeye/32/2242_2.png) [@Buckeye](https://forum.mikrotik.com/u/Buckeye)\
**Post date:** [March 15, 2022, 2:37am UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/2 "2022-03-15T02:37:11Z")

</div>

One thing I noticed was that **ether4-BR-SW\_U10\_T241** is 21 characters long, and the longest name that is displayed **ether2-BR-SW-Base-U1** is 20 characters, so I renamed to the 19 character **eth4-BR-SW\_U10\_T241** , but it didn’t change the behavior, so I backed up and rebooted. Still no change. So it does not appear to be a name too long issue.

```plaintext
ether2-BR-SW-Base-U1
ether4-BR-SW_U10_T241
eth4-BR-SW_U10_T241

```

![renamed_21_char_to_19_no_change.png](https://data-discourse.cdn.mikrotik.com/original/3X/9/2/928278d3f86a17e397482e89ff60aa096578d15a.png)

---

<div class="post-metadata">

**Author:** ![Sob](https://forum.mikrotik.com/letter_avatar/sob/32/6_449c533f586939b6e5f246632a46421f.png) [@Sob](https://forum.mikrotik.com/u/Sob)\
**Post date:** [March 15, 2022, 2:52am UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/3 "2022-03-15T02:52:30Z")

</div>

There are four columns:

Tagged  
Untagged  
Current Tagged  
Current Untagged

First two (you have them hidden) show what you configured. Other two show current active config. It seems that non-active ports are not included there.

---

<div class="post-metadata">

**Author:** ![Buckeye](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/buckeye/32/2242_2.png) [@Buckeye](https://forum.mikrotik.com/u/Buckeye)\
**Post date:** [March 15, 2022, 4:09am UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/4 "2022-03-15T04:09:34Z")

</div>

Plugging a cable into ether4 made the winbox display the things like I expected them to be displayed. But I don’t see any way to select what columns are displayed by winbox.

Is there a winbox setting to unhide the tagged and untagged? There aren’t any columns I see even expanding the screen

But I did find that **/interfaces bridge vlan print detail** does show the info, at least for non-dynamic interfaces.

Thanks  
 ![With cable plugged into ether4 detail.png](https://data-discourse.cdn.mikrotik.com/original/3X/e/f/efdd317ccd81938b4e2d39334fac3ceea425d409.png)  
 ![With cable ether4 unplugged detail.png](https://data-discourse.cdn.mikrotik.com/original/3X/c/9/c9fb93d8555413e57cc891923d673c57d341db1f.png)

---

<div class="post-metadata">

**Author:** ![tdw](https://forum.mikrotik.com/letter_avatar/tdw/32/6_449c533f586939b6e5f246632a46421f.png) [@tdw](https://forum.mikrotik.com/u/tdw)\
**Post date:** [March 15, 2022, 12:00pm UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/5 "2022-03-15T12:00:53Z")

</div>

> [@](#):
>
> Is there a winbox setting to unhide the tagged and untagged? There aren’t any columns I see even expanding the screen

Right-click within any of the child windows, the context menu has _Show Columns…_

I normally have all excepting _Untagged_ selected as there are no untagged= entries in the /interface bridge vlan settings, all of the untagged memberships are generated automatically from the pvid= settings in /interface bridge port when a port is up.

---

<div class="post-metadata">

**Author:** ![anav](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/anav/32/2112_2.png) [@anav](https://forum.mikrotik.com/u/anav)\
**Post date:** [March 15, 2022, 4:55pm UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/6 "2022-03-15T16:55:08Z")

</div>

As per ANY post I have made in the past what seems like 40 years.  
For new admins, I highly recommend always to include the /interface bridge vlans be entered manually  
SO THAT they are visible in configs and for cross matching their config visually with /interface bridge ports…

---

<div class="post-metadata">

**Author:** ![Buckeye](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/buckeye/32/2242_2.png) [@Buckeye](https://forum.mikrotik.com/u/Buckeye)\
**Post date:** [March 16, 2022, 1:00am UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/7 "2022-03-16T01:00:36Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > Is there a winbox setting to unhide the tagged and untagged? There aren’t any columns I see even expanding the screen
> 
> Right-click within any of the child windows, the context menu has _Show Columns…_
> 
> I normally have all excepting _Untagged_ selected as there are no untagged= entries in the /interface bridge vlan settings, all of the untagged memberships are generated automatically from the pvid= settings in /interface bridge port when a port is up.

@tdw Thanks for the hint. Even with the hint it took we a while to figure out what I needed to do. I was clicking on an empty section of the title area (based on the way the Windows 10 Task bar works to bring up context menu with Task Manager, task bar settings, etc.)  
 ![Context Menu active area.png](https://data-discourse.cdn.mikrotik.com/original/3X/a/7/a70cb42cbb3d1874e4ad4e9773172e4abb078e9a.png)

---

<div class="post-metadata">

**Author:** ![Buckeye](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/buckeye/32/2242_2.png) [@Buckeye](https://forum.mikrotik.com/u/Buckeye)\
**Post date:** [March 16, 2022, 2:33am UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/8 "2022-03-16T02:33:50Z")

</div>

> [@](#):
>
> As per ANY post I have made in the past what seems like 40 years.  
> For new admins, I highly recommend always to include the /interface bridge vlans be entered manually  
> SO THAT they are visible in configs and for cross matching their config visually with /interface bridge ports…

This [post](http://forum.mikrotik.com/t/2-ways-to-associate-bridge-and-vlan/156212/1) has the complete config this question was spawned from, and this [post](http://forum.mikrotik.com/t/2-ways-to-associate-bridge-and-vlan/156212/1) has my annotated export of the relevant parts.

I am not understanding if your comment was pertaining to my example, or in general. But I also am not sure I understand what you mean by “entered manually”. Do you mean explicitly specify everything that RouterOS will apply defaults to? For example, when using  
/interface bridge interface=ether3-BR-SW-U241 pvid=241  
and not explicitly stating the frame-types admitted, it will default to frame-types=admit-all, and when frame-types is admit-all, my understanding is that it will then automatically treat the egress for vlan 241 on ether3-BR-SW-U241 as untagged (implicitly). Is your note suggesting that these should be added explicitly so there is not doubt when looking at the config?

references:

From [VLAN Example - Trunk and Access Ports](https://help.mikrotik.com/docs/display/ROS/Bridge#Bridge-VLANExample-TrunkandAccessPorts)

Add Bridge VLAN entries and specify tagged ports in them. **Bridge ports with frame-types set to admit-only-untagged-and-priority-tagged will be automatically added as untagged ports for the pvid VLAN.**

From [VLAN Example - Trunk and Hybrid Ports](https://help.mikrotik.com/docs/display/ROS/Bridge#Bridge-VLANExample-TrunkandHybridPorts)

Add Bridge VLAN entries and specify tagged ports in them. In this example egress VLAN tagging is done on ether6,ether7,ether8 ports too, making them into hybrid ports. **Bridge ports with frame-types set to admit-all will be automatically added as untagged ports for the pvid VLAN.**

@anav what is the best way to suggest additions/clarifications to your [NEW USER PATHWAY TO CONFIG SUCCESS](https://forum.mikrotik.com/viewtopic.php?t=182373) thread? I don’t want to pollute the thread; it is relatively clean at this point. And if people start asking questions or making comments about how to improve the content, it makes it harder to find the posts with the focused info in them. It’s like hijacking the thread.  
p.s. for @anav you mention llama several times in your profile, but your avatar looks more like a fire breathing donkey than a llama. What is the story behind your avatar?

---

<div class="post-metadata">

**Author:** ![mkx](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/mkx/32/1611_2.png) [@mkx](https://forum.mikrotik.com/u/mkx)\
**Post date:** [March 16, 2022, 5:18am UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/9 "2022-03-16T05:18:28Z")

</div>

> [@](#):
>
> For example, when using  
> /interface bridge interface=ether3-BR-SW-U241 pvid=241  
> and not explicitly stating the frame-types admitted, it will default to frame-types=admit-all, and when frame-types is admit-all, my understanding is that it will then automatically treat the egress for vlan 241 on ether3-BR-SW-U241 as untagged (implicitly).

Property _frame-types_ is about ingress filtering and thus has nothing to do with untagging on egress. Property _pvid_ does though … when set, it this setting that implicitly adds port as untagged to VLAN used and will untag frames on egress. BTW, implicit default is _pvid=1_ on all bridge ports without exception - bridge _interface_ included … so you can imagine all the consequences of it (combined with various settings of _frame-types_).

---

<div class="post-metadata">

**Author:** ![tdw](https://forum.mikrotik.com/letter_avatar/tdw/32/6_449c533f586939b6e5f246632a46421f.png) [@tdw](https://forum.mikrotik.com/u/tdw)\
**Post date:** [March 16, 2022, 12:14pm UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/10 "2022-03-16T12:14:56Z")

</div>

> [@](#):
>
> Property _frame-types_ is about ingress filtering and thus has nothing to do with untagging on egress. Property _pvid_ does though … when set, it this setting that implicitly adds port as untagged to VLAN used and will untag frames on egress.

However _frame-types_ does modify untagged membership, when set to _admit-only-vlan-tagged_ the _pvid=_ setting is ignored completely and the port is not added as an untagged member of any VLAN.

---

<div class="post-metadata">

**Author:** ![mkx](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/mkx/32/1611_2.png) [@mkx](https://forum.mikrotik.com/u/mkx)\
**Post date:** [March 16, 2022, 3:37pm UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/11 "2022-03-16T15:37:52Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > Property _frame-types_ is about ingress filtering and thus has nothing to do with untagging on egress. Property _pvid_ does though … when set, it this setting that implicitly adds port as untagged to VLAN used and will untag frames on egress.
> 
> However _frame-types_ does modify untagged membership, when set to _admit-only-vlan-tagged_ the _pvid=_ setting is ignored completely and the port is not added as an untagged member of any VLAN.

Which is purely cosmetics … port will first drop all untagged frames and then process the rest. Even if it wouldn’t skip the “tag the untagged frames with pvid” code path, it wouldn’t trigger as no untagged frames would pass by.

We can guess more or less wildly how the automagic of setting pvid without explicit VLAN port membership setting works. Your guess is good as mine … and my guess is that when configuring things port either gets added to untagged port list or not (depending on some settings).

However when things are set up (either by hand or by automagic), frame-types doesn’t affect handling of egress frames at all. Which IMO is backed up by a fact that if you explicitly set untagged membership of a port, frames belonging to untagged VLANs get untagged regardless of pvid or frame-types settings. And you can set single port as untagged member of multiple VLANs and all get untagged whereas port can only have one pvid.

As the crazy Llama once said: this automagic (of adding port with pvid set to list of untagged ports of that VLAN) is handy, but ruins the educational process because it hides some essential knowledge from innocent student.

---

<div class="post-metadata">

**Author:** ![anav](https://forum.mikrotik.com/user_avatar/forum.mikrotik.com/anav/32/2112_2.png) [@anav](https://forum.mikrotik.com/u/anav)\
**Post date:** [March 16, 2022, 3:43pm UTC](https://forum.mikrotik.com/t/bridge-vlans-hex-s-v7-2rc4-interface-bridge-vlan-print/156544/12 "2022-03-16T15:43:27Z")

</div>

> [@](#):
>
> > [@](#):
> >
> > However _frame-types_ does modify untagged membership, when set to _admit-only-vlan-tagged_ the _pvid=_ setting is ignored completely and the port is not added as an untagged member of any VLAN.
> 
> We can guess more or less wildly how the automagic of setting pvid without explicit VLAN port membership setting works. Your guess is good as mine … and my guess is that when configuring things port either gets added to untagged port list or not (depending on some settings).
> 
> However when things are set up (either by hand or by automagic), frame-types doesn’t affect handling of egress frames at all. Which IMO is backed up by a fact that if you explicitly set untagged membership of a port, frames belonging to untagged VLANs get untagged regardless of pvid or frame-types settings. And you can set single port as untagged member of multiple VLANs and all get untagged whereas port can only have one pvid.
> 
> As the genius Llama once said: this automagic (of adding port with pvid set to list of untagged ports of that VLAN) is handy, but ruins the educational process because it hides some essential knowledge from innocent student.

Fixed it for ya !!

Okay perhaps an exaggeration how bout, “knows what beginners need” Llama!
