--- title: "Define bridge VLAN interfaces" slug: "define-bridge-vlan-interfaces" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-10-05T15:40:08Z published: 2026-10-05T15:40:08Z canonical: "docs.trellix.com/define-bridge-vlan-interfaces" --- > ## Documentation Index > Fetch the complete documentation index at: https://docs.trellix.com/llms.txt > Use this file to discover all available pages before exploring further. # Define bridge VLAN interfaces Configuring a Sensor to act as a VLAN Bridge. ## Task 1. Defining Bridge VLAN Interfaces: You need to change the Interface Type to Bridge VLAN. 1. Go to **Devices** → **** → **Devices** → **** → **IPS Interfaces** → **** → **Properties**. The **Properties** page displays. 2. In the **Properties** page, change the **Interface Type** to **Bridge VLAN** and click **OK** to confirm. > [!NOTE] > Caution > > When you change the Interface Type, the configurations relevant to the earlier Interface Type is lost. For example, if the Interface was of type VLAN earlier with VLAN ID list configured, the list is lost when you change this interface to Bridge VLAN. 2. Specifying the VLAN pairs: At the Interface level, you need to specify the VLANs that are to be bridged as a pair. For example, if you want to bridge VLANs 10 and 11, you need to specify them as a pair. Then, the Sensor tags VLAN 10 traffic as VLAN 11 before forwarding it through the peer port. Similarly, it tags VLAN 11 traffic as VLAN 10. You can define all the VLANs that you want the Sensor to bridge now. Then, you can assign all or some of them to the Sub-Interfaces. For each VLAN pair that you want to specify: 1. From the **Properties** page, click ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-6E2D5582-3868-4FBA-BA20-20A3995E8669-low(1).png?sv=2026-02-06&spr=https&st=2026-11-20T14%3A34%3A43Z&se=2026-11-20T15%3A34%3A43Z&sr=c&sp=r&sig=vuOtKk%2FwKlFTwWEZiIgtQnOkjoxrFT16UbX%2FvzHRcjY%3D). The **Properties** page appears. 2. Enter the **VLAN ID** and **Peer VLAN ID** in the corresponding fields and click **Save**. 3. Repeat the steps a and b to add more VLAN pairs. > [!NOTE] > Note > > To delete a VLAN pair, select it in the **Properties** page and click > > ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-377572A5-33EB-43F9-A828-202101E436DC-low(1).png?sv=2026-02-06&spr=https&st=2026-11-20T14%3A34%3A43Z&se=2026-11-20T15%3A34%3A43Z&sr=c&sp=r&sig=vuOtKk%2FwKlFTwWEZiIgtQnOkjoxrFT16UbX%2FvzHRcjY%3D) > > . > [!NOTE] > Note > > At a given point in time, up to 127 pairs of VLANs can be defined per VIDS. When you reach 127 VLAN pairs at the interface level, you can assign some or all of them to a Sub-Interface to be able to define more at the interface level. > [!NOTE] > Note > > The VLANs should be unique within an Interface. For example, you cannot configure 20-21 and 22-21 as two VLAN pairs for one Interface. > [!NOTE] > Note > > The VLAN pairs are symmetric; the VLANs are mapped with their peer IDs regardless of the Sensor port in which they are seen. The switch port connecting to the Sensor port must be configured to receive the corresponding VLAN traffic. 3. Updating the Sensor: After you define the Bridge VLAN interface, you must update the Sensor about this configuration change.