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

This post has the complete config this question was spawned from, and this post 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

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

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 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?