--- title: "Create sub-interfaces" slug: "create-sub-interfaces" tags: ["Product Usage", "IPS 10.1.10"] updated: 2026-10-05T15:40:13Z published: 2026-10-05T15:40:13Z canonical: "docs.trellix.com/create-sub-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. # Create sub-interfaces If there is VLAN,Bridge VLAN or CIDR traffic transmitting across a monitored segment, you can create one or more sub-interfaces. Before creating a sub-interface, the "Interface Type" must be set to VLAN or CIDR in Managing an interface, and you must have already entered VLAN or CIDR IDs. > [!NOTE] > Note > > If you entered IDs that do not flow in the monitored link, the parent interface's policy protects all traffic. > [!NOTE] > Note > > Before creating sub-interfaces, it is important to note that you will not be able to perform the **Manage DoS IDs** action at the interface level once a sub-interface is created. If you create a sub-interface, then you must utilize **Manage DoS IDs** at the sub-interface level. If you added more than one VLAN or CIDR ID to an interface, you can create a sub-interface with one or multiple IDs or you can create multiple sub-interfaces. To create more than one sub-interface, you must repeat the steps that follow. ## Task 1. For a standalone Sensor, select **Devices** → **** → **Devices** → **** → **IPS Interfaces** → **** → **Sub-interfaces**. For Sensors in a stack, select **Devices** → **** → **Devices** → **** → **IPS Interfaces** → **** → **** → **Sub-interfaces**. Manage Sub-Interface ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-14205506-C7F6-4116-8B66-C59E896B51DA-low.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A28%3A23Z&se=2026-11-20T12%3A28%3A23Z&sr=c&sp=r&sig=%2BDf8bfYp%2B%2B4we3Nctzc4F4SldPUrdhB%2FBseCoU2KaV0%3D) 2. Click ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-A6ACF06E-8B7C-4F33-9335-99E4B1FDEB3D-low(2).png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A28%3A23Z&se=2026-11-20T12%3A28%3A23Z&sr=c&sp=r&sig=%2BDf8bfYp%2B%2B4we3Nctzc4F4SldPUrdhB%2FBseCoU2KaV0%3D). > [!NOTE] > Note > > To edit an existing sub-interface, select the sub-interface and 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-20T11%3A28%3A23Z&se=2026-11-20T12%3A28%3A23Z&sr=c&sp=r&sig=%2BDf8bfYp%2B%2B4we3Nctzc4F4SldPUrdhB%2FBseCoU2KaV0%3D) > > ; then follow the steps below. To delete a sub-interface, select the sub-interface and click > > ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-B13A6E00-0610-4794-A2FF-1EE7614AD1D3-low(2).png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A28%3A23Z&se=2026-11-20T12%3A28%3A23Z&sr=c&sp=r&sig=%2BDf8bfYp%2B%2B4we3Nctzc4F4SldPUrdhB%2FBseCoU2KaV0%3D) > > ; then confirm the deletion. 3. Type a **Sub-interface Name**. 4. Select a policy (**Policy Name**) to be enforced on the sub-interface(s). Create Sub-Interface - CIDR ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-D63DC589-345C-4DDF-A80E-D64CA1A0C85C-low.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A28%3A23Z&se=2026-11-20T12%3A28%3A23Z&sr=c&sp=r&sig=%2BDf8bfYp%2B%2B4we3Nctzc4F4SldPUrdhB%2FBseCoU2KaV0%3D) 5. Do one of the following: - For *VLAN* and Bridge VLAN move an ID from "Available" to "Allocated" by selecting the ID and clicking the ![](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/GUID-25318FEC-82B6-4B6F-A813-D8BB83A05190-low.png?sv=2026-02-06&spr=https&st=2026-11-20T11%3A28%3A23Z&se=2026-11-20T12%3A28%3A23Z&sr=c&sp=r&sig=%2BDf8bfYp%2B%2B4we3Nctzc4F4SldPUrdhB%2FBseCoU2KaV0%3D) button. - For *CIDR*, type the **IP Address** and **Mask Length** and click **Add to List**. A valid CIDR can be from the list you entered on clicking ![](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-20T11%3A28%3A23Z&se=2026-11-20T12%3A28%3A23Z&sr=c&sp=r&sig=%2BDf8bfYp%2B%2B4we3Nctzc4F4SldPUrdhB%2FBseCoU2KaV0%3D) at **IPS Interface** → **Interface_Name** (For Sensors in stack, **IPS Interface** → **** → **Interface_Name**), or a CIDR host(s) within a network in your entered list. For example, if you had entered 192.168.3.0/24, you can enter 192.168.3.1/32 and 192.168.3.2/32 here for sub-interface creation. > [!NOTE] > Note > > The CIDR IP address field now enables you to enter IPv4 addresses in 4 different fields separated with dots. You can now enter the IP address value in the corresponding fields. > [!NOTE] > Note > > The maximum value in each field is 255. If you enter ".", you are tabbed to next field. > [!NOTE] > Note > > Only numerical values between 0—9 are allowed. Special characters are not allowed. Pressing tab after the last field tabs you to select mask field. > [!NOTE] > Note > > If you are creating another sub-interface from a CIDR address that has not been allocated, you can check to see which have already been allocated by clicking **List of Allocated CIDRs**. 6. Click **Save**. The new sub-interface appears in the **Sub-Interface List** table as well as under IPS Interfaces as a node under the interface node within which it was created. 7. Download the changes to your Sensor by clicking **Deploy Pending Changes**.