Project

General

Profile

Actions

Correction #11139

open

Bridges and VLANs

Added by Steve Wheeler over 3 years ago. Updated over 1 year ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
VLANs
Target version:
-
Start date:
12/07/2020
Due date:
% Done:

0%

Estimated time:

Description

When you add an interface to a bridge you can no longer use VLANs on that interface. This is the expected behaviour since a bridge on the parent interface carries the tagged traffic before it can be untagged and passed to the VLAN interface. However it requires further documentation since it's not clear in many situations, such as OpenVPN TAP, and resulting failure can be difficult to diagnose.

If you need to bridge an interface that is carrying VLANs the untagged traffic must be moved to an additional VLAN on it and bridged to that instead. That does then require a managed switch between that interface and any hosts but that is almost always the case since it's already carrying VLANs.

Another good reason to avoid tagged and untagged traffic on the same interface where possible.

Actions #1

Updated by Jim Pingle over 3 years ago

  • Target version deleted (2.5.0)
Actions #2

Updated by Jim Pingle over 1 year ago

  • Tracker changed from Documentation to Correction
  • Project changed from pfSense to pfSense Docs
  • Category changed from Interfaces to VLANs
  • Affected Version deleted (All)
Actions

Also available in: Atom PDF