Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Next revision
Previous revision
Next revisionBoth sides next revision
playground:arinc9:bridge-vlan-filtering [2021/09/22 21:46] – created arinc9playground:arinc9:bridge-vlan-filtering [2022/05/31 19:48] – [Egress untagged and PVID (Primary VLAN ID)] Improve explanation arinc9
Line 12: Line 12:
  
 ===== Local ===== ===== Local =====
-Local option will make the specified VLAN traffic available locally. So the router can use a subinterface of the bridge to be involved in that VLAN. 
  
-If you don't want to tag the router for a VLAN, you can disable this option and run ''service network restart'' for the changes to take effect.+Local option will automatically assign the specified VLAN ID to the bridge interface and create a VLAN interface of the bridge interface. So the router can use the VLAN interface to be involved in that VLAN.
  
 +If you don't want the router to be involved in that VLAN, you can disable this option and run ''service network restart'' for this change to take effect.
  
-===== Egress untagged and PVID (Port VLAN ID) ===== + 
-//Disclaimer: LuCI calls PVID: Primary VLAN ID. This is incorrect and it should be renamed as Port VLAN ID.//+===== Egress untagged and PVID =====
  
 **Untagged Traffic**: Traffic between devices where there's no VLAN ID in the frames. Computers, printers, etc. send and receive untagged traffic by default. **Untagged Traffic**: Traffic between devices where there's no VLAN ID in the frames. Computers, printers, etc. send and receive untagged traffic by default.
  
-**Ingress**: Traffic coming in to the bridge through an interface +**Ingress**: Traffic coming in to the bridge through an interface on the bridge 
- +  * **PVID**: Primary VLAN ID makes the specified VLAN ID assigned to the interface the primary one. Untagged ingress will be assigned to the specified VLAN ID. There can be multiple VLAN IDs assigned to the interface. This is not useful if only a single VLAN ID with egress set to untagged is assigned to the interface. 
-  * **PVID**: Bridge will assign the specified VLAN ID to the untagged traffic coming in to the bridge through the specified interface. +**Egress**: Traffic going out of the bridge through an interface on the bridge 
- +  * **Egress untagged**: Frames will leave the bridge through the specified interface as untagged. Untagged ingress will be assigned to the specified VLAN ID unless PVID is set to a different VLAN ID on the interface. Tagged ingress is discarded. 
-**Egress**: Traffic going out of the bridge through an interface +  * **Egress tagged**: Frames will leave the bridge through the specified interface as tagged with the specified VLAN IDUntagged ingress is discarded unless PVID is set to a VLAN ID on the interface. Tagged ingress is discarded if the VLAN ID on the tag doesn't match the VLAN ID(s) assigned to the interface.
- +
-  * **Egress untagged**: Bridge will forward the specified VLAN ID traffic going out of the bridge through the specified interface as untagged. +
- +
-To be able to transmit and receive packets on the same VLAN, have the PVID and egress untagged on the same VLAN ID for an interface.+
  
 [[https://developers.redhat.com/blog/2017/09/14/vlan-filter-support-on-bridge|VLAN filter support on bridge | Red Hat Developer]] [[https://developers.redhat.com/blog/2017/09/14/vlan-filter-support-on-bridge|VLAN filter support on bridge | Red Hat Developer]]
  • Last modified: 2022/05/31 20:31
  • by arinc9