So in the latter case, receiver would have to know how to deal with 802.1q frames (or blindly strip them which would become a problem in the other direction if switch/router actually expected 802.1q frames with VID set to 1) while in the former case it really is about truly untagged, plain ethernet. The former has ethertype value 0x0800 (or, if it's not about IPv4 packet, appropriate ethertype value), the later has (outer) ether type 0x8100 with additional header (3 bits PCP - priority code point 1 bit DEI - drop eligible indicator and 12 bits VID with value of 1 in this particular case) followed by usual ethertype 0x0800 (or, if it's not IPv4 packet, appropriate ethertype value). There's a distinction between untagged frame and frame tagged with VLAN ID=1. Will the CapAC remove vlanID1 from packets going to the WLAN? and the packets will have vlanid0 and if so how will that affect devices connecting?Īs you can surmize I am still not sure how to handle the bridge vlan for my capAC for ether1 another one and unless some MT developer explains the way it's really implemented in ROS it's all just guessing.Īdd bridge=bridgeHallway comment=defconf interface=ether1 (pvid=1)Īdd bridge=bridgeHallway comment=defconf interface=DevicesHallway pvid=45īridge=homebridge untagged=ether1 vlanid=1 is correct as it is consistent with the other interfacesīut what does that mean. 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
0 kommentar(er)
