--- title: "Configuring multiple network interfaces" slug: "configuring-multiple-network-interfaces" tags: ["Endpoint Security (HX)", "Product Usage"] updated: 2026-10-01T12:34:10Z published: 2026-10-01T12:34:10Z canonical: "docs.trellix.com/configuring-multiple-network-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. # Configuring multiple network interfaces The ether1 interface on the Email Security — Server AWS instance is the only interface that is created by default. You can create multiple network interfaces (ether2, ether3, and so on) and attach them to your Email Security — Server AWS instance. The following table shows the default Email Security — Server interfaces and their purpose. | Email Security — Server Interface | Purpose | | --- | --- | | ether1 | Management interface | | pether3 | Network monitoring interface | ### Creating network interfaces This section describes how to create a network interface for your Email Security — Server instance. To create a network interface: 1. Open the Amazon EC2 console. 2. In the left pane, select **Network & Security** > **Network Interfaces**. 3. Click **Create Network Interface**. ![AWS_CreateNetworkInterface_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-1c246fad-a2e0-bc5d-99a6-086180951a12.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A34%3A13Z&se=2026-11-20T11%3A34%3A13Z&sr=c&sp=r&sig=CYdHUWT8um9Ojr2Zc9oMA%2FCQDgTavrmcvN6IhbVcl%2Fc%3D) 4. Enter information that uniquely identifies the interface in the **Description** field. 5. Select the subnet for the interface in the **Subnet** drop-down list. ### Important Each interface must be in a separate subnet. 6. Select **Custom** to manually configure a static IPv4 address. 7. Enter the custom static IPv4 address in the **IPv4 address** field. 8. Complete the **Elastic Fabric Adapter** and **Security groups** fields as directed by your AWS administrator. 9. Click **Create**. 10. Repeat this procedure for each network interface. 11. Continue to [Attaching Network Interfaces](/network-and-platform/docs/configuring-multiple-network-interfaces#attaching_network_interfaces). ### Attaching network interfaces This section describes how to attach a network interface to your Email Security — Server instance. To attach a network interface: 1. Open the EC2 console. 2. Select **Instances** > **Instances** in the left pane. 3. Right-click the instance and then select **Networking** > **Attach Network Interface**. The **Attach Network Interface** dialog box opens. ![AWS_AttachInterface_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-174f4880-b7b0-6e69-7b9b-8158cad70715.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A34%3A13Z&se=2026-11-20T11%3A34%3A13Z&sr=c&sp=r&sig=CYdHUWT8um9Ojr2Zc9oMA%2FCQDgTavrmcvN6IhbVcl%2Fc%3D) 4. Select the interface with the lowest number in the **Network Interface** drop-down list (for example, ether2) and then click **Attach**. 5. Repeat the previous step for each network interface. ### Important Attach the interfaces in numeric order. For example, attach pether3 before pether4. 6. Disable source and destination checks on each monitor interface. 1. Select the interface. 2. Right-click and select **Change Source/Dest. Check**. The **Source/Dest. Check** dialog box opens. 3. Select **Disabled** and then click **Save**. ![AWS_SourceDestCheck_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-639db0ef-9d07-4624-b215-9a1d58925149.png?sv=2026-02-06&spr=https&st=2026-11-20T10%3A34%3A13Z&se=2026-11-20T11%3A34%3A13Z&sr=c&sp=r&sig=CYdHUWT8um9Ojr2Zc9oMA%2FCQDgTavrmcvN6IhbVcl%2Fc%3D) 7. Stop the instance: 1. Select **Instances** in the navigation pane. 2. Select the instance, right-click, and then select **Instance State** > **Stop**. 8. Restart the instance: - Select the instance, right-click, and then select **Instance State** > **Start**. ### Important Do not perform this step if you plan to perform the following optional procedure ([Configuring the Activation Code and Initial Admin Password](/network-and-platform/docs/configuring-the-activation-code-and-initial-admin-password-manual-method-only)). ### Configuring the interface for email analysis 1. Enable the interface: ```plaintext hostname (config) # no interface shutdown ``` Ignore the error that may be displayed; it doesn't hinder the operation. 2. Set the IP address for the interface manually: ```plaintext hostname (config) # ip address / ``` 3. (Optional) Enable other interfaces in a similar manner. 4. Configure the interface for email analysis: ```plaintext hostname (config) # email-analysis interface ``` 5. (Optional) If the Destination MTA is not on the same subnet as the newly configured interface, you need to add a static route to reach the destination MTA (next-hop) IP for the solution to work. In this example, the default gateway (172.16.1.1) will be on ether1, but a different gateway will be on pether3 for SMTP traffic. As shown below, a static IP route is configured for the next-hop MTA (10.2.74.131) to use a different gateway (10.2.75.254). ```plaintext hostname (config) # interface ether1 ip address 172.16.216.60 /12 hostname (config) # interface pether3 ip address 10.2.75.13 /24 hostname (config) # ip default-gateway 172.16.1.1 hostname (config) # ip route 10.2.74.130 255.255.255.255 10.2.75.254 hostname (config) # ip route 10.2.74.131 255.255.255.255 10.2.75.254 ``` ### Configuring advanced URL defense 1. To set up Advanced URL Defense on the interface to separate the live traffic: ```plaintext hostname (config) # analysis live live-interface ``` 2. Configure the IP address of the live analysis data interface. Make sure to use the IP address of the new interface that was configured for email analysis. ```plaintext hostname (config) # analysis live external ip ``` 3. Check the live analysis configuration: ```plaintext hostname (config) # analysis live check-connection ``` :