seemingly untagged packets on bridge, but my own simplification covers that variant just the same.Īnyhow, I'll stop bitching about this.

I guess this is the origin of explanation about what happens on the bridge.īut then again, setting bridge's pvid to some other value and setting member interfaces' pvid to the same value re-instate the same behaviour. to keep (broken) bridge port behaviour the same as it was before 6.42. This might explain why pvid=1 is default setting. in previous times, when bridge was sort of a dumb switch, bridge interface happily utilized packets belonging to VLAN ID 1 just the same as explicitly untagged while one had to use VLAN interface for the rest of VLANs. Perhaps things slightly changed with event of bridge vlan-filtering. If you change bridge's own pvid to something else than 1, VID 1 starts behaving normally.

I used to think the same until I've found out that it is not VLAN ID 1 which is always handled untagged but it's actually 'the VLAN ID which is configured as bridge's own pvid parameter' which is treated as untagged on the bridge.

This is, fortunately or unfortunately, not true. Mikrotik uses VLAN ID 1 as synonym for untagged

MyPublicWiFi 30.1 for android download