SwOS VLAN mode inconsistent documentation CSS106 (aka RB260) vs CSS326

[Buckeye]

The VLAN mode documentation for the CSS106 and at least CSS326 are not consistent. Specifically on the CSS106 it says vlan mode applies to ingress port, but the CSS326 it says the vlan mode is relevant to egress ports. The CSS106 has a separate VLAN header setting but it isn't clear to me if this is applied on ingress or egress. Also different is the documentation for the vlan mode disabled.

SwOS doesn't seem to have a global setting to turn vlan-aware mode on and off, unlike the ROS bridge does with the vlan-filtering option. Instead it is configured per port.

Here is what the RB260 (CSS106) "manual" says:

And here is what the CSS326 "manual" says:

When reading Pfsense to CSS326-24G-2S+ to CSS326-24G-2S+ Vlan problems on 2nd switch - #29 by comet424 I don't know if there is a way to make the CSS326 operate like a "dumb" switch and just pass frames as-is without processing vlan tags. Not that it is something that you would want to do given the ability for the switch to process vlan tags.

[pe1chl]

There are different things called SwOS. The SwOS for one switch is not the same as for another. Check the version: is it 1.xx or 2.xx.

(unlike RouterOS, which has essentially the same functionality for all different devices)

[Buckeye]

Yes, it seems SwOS is basically a way to configure the switch chip registers, and eac switch chip has its own set of capabilities as registers.

[Buckeye]

Here is something that looks wrong in the RB260 (CSS106) documentation.

RSTP - CSS106 (RB260) series Manual - SwOS - MikroTik Documentation

This "manual" section shows this screen (not correct for v2.18)

Here's what my CSS106 (with SwOS v2.18) RSTP screen looks like: (red box added by me)

The text of the manual does describe the Forward Reserved Multicast functionality.

I haven't tested it, but if it does what it says it does, then it may fix @chechito's complaint here RSTP not working properly on CSS106-5G-1S - #4 by chechito but it does not seem to allow setting this on a port by port basis.

Here's what the text says as of 2026-02-16

The reason I was looking at this was because I just switched to ATT Fiber 300 (from Spectrum cable) and wanted to put a tap to watch traffic on the "WAN" side of the router (between my home router and the ATT BGW320 LAN) but I don't want RSTP or LLDP stuff being tranmitted from the switch ports connected to the ISP side. I have the ATT BGW320-505 in passthrough mode, but that's a "hack" which evidently masquerades all traffic to the BGW320's LAN, and then reapplies source NAT to make it appear to the home router as if it is the global ip address, and bypasses the BGW320's firewall.

[chechito]

thanks for the heads up !!