--- title: "Configuring inline proxy mode using the Web UI" slug: "configuring-inline-proxy-mode-using-the-web-ui" tags: ["Network Security (NX)"] updated: 2026-08-24T22:01:11Z published: 2026-08-24T22:01:11Z canonical: "docs.trellix.com/configuring-inline-proxy-mode-using-the-web-ui" stale: true --- > ## 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 inline proxy mode using the Web UI Inline proxy deployment requires two network port pairs. This can be accomplished using a Network Security appliance with two port pairs, or one port pair from each of two Network Security appliances. For details about inline proxy deployment, refer to the *Hardware Administration Guide* for your appliance model. > [!NOTE] > Note > > Starting with version 7.1.0, the Network Security appliances bypass packets larger than 1650 bytes rather than dropping them. Prerequisites - Operator or Admin access ##### Configuring inline proxy mode with one Network Security appliance Use the **Policy Settings** page for inline proxy mode to configure a deployment with one Network Security appliance with two network port pairs. Interface A connects the LAN-facing switch or router (A1) to the proxy server (A2). Interface B connects the LAN-facing switch or router (B1) to the Internet-facing switch or router (B2). ![NX_Inline_WebUI_2pp_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-21f6705c-91df-4e6d-669c-3c633b070f7c.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A53%3A50Z&se=2026-11-20T07%3A53%3A50Z&sr=c&sp=r&sig=LIVYDXwC%2FHx4nB6ig34ulNExGmbVfhQS2PFJs2dqphM%3D) Operational modes for inline deployment are described in the following table. | Mode | Description | | --- | --- | | Block | Blocks malicious traffic (recommended). - FS Open—In case of failure, all traffic passes through (recommended). - FS Close—In case of failure, all traffic is blocked. (Use this setting only if the device is actively monitored). | | Monitor | Monitors the traffic and generates alerts on malicious events. | | Bypass | Forced bypass wherein the Network Security appliance neither blocks nor analyzes traffic. | Use the **Settings: Interfaces - Whitelists** page for inline whitelists to configure interface A2 to allow incoming traffic from the proxy server to pass through unblocked. ![NX_InlineWhitelist_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-bdd52abb-24bf-740b-5f4f-5c7a8de6d085.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A53%3A50Z&se=2026-11-20T07%3A53%3A50Z&sr=c&sp=r&sig=LIVYDXwC%2FHx4nB6ig34ulNExGmbVfhQS2PFJs2dqphM%3D)To configure interface A and interface B: 1. Click the **Settings** tab. 2. Click **Inline Operational Modes** on the sidebar. 3. Select a blocking option for pair A and pair B. (Inline Block FS Open is recommended). 4. Click **Update: Operational Modes**. 5. Select **Inline Whitelists** on the sidebar. Enter the information for the proxy server and then click **Add Whitelist**. ##### Configuring inline proxy mode with two Network Security appliances Use the **Policy Settings** page for inline proxy mode to configure a deployment with two Network Security appliances with one network port pair each. NX Appliance1 connects to the proxy offline, and NX Appliance2 is between a LAN-facing switch or router and an Internet-facing switch or router. ![NX_InlineWebUI_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-f92bbc24-f069-55a9-4e3b-9995a0aa6d7a.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A53%3A50Z&se=2026-11-20T07%3A53%3A50Z&sr=c&sp=r&sig=LIVYDXwC%2FHx4nB6ig34ulNExGmbVfhQS2PFJs2dqphM%3D) Operational modes for inline deployment are described in the following table. | Mode | Description | | --- | --- | | Block | Blocks malicious traffic (recommended). - FS Open—In case of failure, all traffic passes through (recommended). - FS Close—In case of failure, all traffic is blocked. (Use this setting only if the device is actively monitored). | | Monitor | Monitors the traffic and generates alerts on malicious events. | | Bypass | Forced bypass wherein the Network Security appliance neither blocks nor analyzes traffic. | Use the **Policy Settings** page for inline whitelists to configure interface A2 to allow incoming traffic from the proxy server to pass through unblocked. ![NX_InlineWhitelist_scap.png](https://cdn.us.document360.io/0d453a50-e1da-4d4a-9409-fea7959614d8/Images/Documentation/uuid-bdd52abb-24bf-740b-5f4f-5c7a8de6d085.png?sv=2026-02-06&spr=https&st=2026-11-20T06%3A53%3A50Z&se=2026-11-20T07%3A53%3A50Z&sr=c&sp=r&sig=LIVYDXwC%2FHx4nB6ig34ulNExGmbVfhQS2PFJs2dqphM%3D)To configure NX Appliance1: 1. Click the **Settings** tab. 2. Click **Inline Operational Modes** on the sidebar. 3. Select a blocking option for pair A. (Inline Block FS Open is recommended). 4. Click **Update: Operational Modes**. 5. Select **Inline Whitelists** on the sidebar. Enter the information for the proxy server and then click **Add Whitelist**. To configure NX Appliance2: 1. Click the **Settings** tab. 2. Click **Inline Operational Modes** on the sidebar. 3. Select a blocking option for pair A. (Inline Block FS Open is recommended). 4. Click **Update: Operational Modes**.