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.
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.
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.
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.
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…
@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.)
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?
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.
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?
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).
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.
