--- title: "Switching to single-port or dual-port communication in a NAT deployment" slug: "switching-to-single-port-or-dual-port-communication-in-a-nat-deployment-4" tags: ["Malware Analysis (AX)", "AX 10.x", "Product Usage"] updated: 2026-10-01T20:36:14Z published: 2026-10-01T20:36:14Z canonical: "docs.trellix.com/switching-to-single-port-or-dual-port-communication-in-a-nat-deployment-4" --- > ## 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. # Switching to single-port or dual-port communication in a NAT deployment Managed Malware Analysis appliances can communicate with the Central Management System appliance over a single port or using two ports. (For details, see [About changing the address type for DTI network service requests](/network-and-platform/docs/about-changing-the-address-type-for-dti-network-service-requests-5) .) In the dual-port configuration, if the Central Management System appliance is in an internal network behind a NAT gateway, a custom DTI source address must be configured. The custom address allows the managed appliance to access the HTTPS port on the Central Management System appliance to request software updates from the DTI network. (For details, see [Configuring and activating an accessible DTI server address](/network-and-platform/docs/configuring-and-activating-an-accessible-dti-server-address-4) .) To configure the custom address, you must set a flag to prevent the Central Management System appliance from overriding the custom address settings. If you switch from dual-port to single-port communication, you must remove this flag so the Central Management System appliance can push the single-port settings to the Malware Analysis appliance. To switch from dual-port to single-port communication: 1. Log in to the Malware Analysis CLI. 2. Go to CLI configuration mode. ```plaintext appl-hostname > enable appl-hostname # configure terminal ``` 3. Allow the Central Management System appliance to push the single-port settings: ```plaintext appl-hostname (config) # fenet dti source override enable appl-hostname (config) # fenet dti upload destination override enable appl-hostname (config) # fenet dti mil service override enable appl-hostname (config) # fenet dti avsuite service override enable ``` 4. Verify your changes: ```plaintext appl-hostname (config) # show fenet ``` 5. Save your changes. ```plaintext appl-hostname (config) # write memory ``` To switch from single-port to dual-port communication: 1. Perform the procedure in [Configuring dual-port Communication using the CLI](/network-and-platform/docs/configuring-dual-port-communication-using-the-cli-4) . 2. If the Central Management System appliance is behind a NAT gateway, perform the procedure in [Configuring and activating an accessible DTI server address using the CLI](/network-and-platform/docs/configuring-and-activating-an-accessible-dti-server-address-using-the-cli-3) . ### Example The following example allows the Central Management System appliance to push the single-port settings to the Malware Analysis appliance, after the address type was changed from dual-port to single-port. ```plaintext appl-hostname (config) # fenet dti source override enable appl-hostname (config) # fenet dti upload destination override enable appl-hostname (config) # fenet dti mil service override enable appl-hostname (config) # fenet dti avsuite service override enable appl-hostname (config) # write memory appl-hostname (config) # show fenet dti configuration DTI CLIENT CONFIGURATION:  Download source    :  CMS (DTIUser@10.2.0.0 : singleport) - Managed by CMS  Upload destination :  CMS (DTIUser@10.2.0.0 : singleport) - Managed by CMS  Mil service        :  CMS (DTIUser@10.2.0.0 : singleport) - Managed by CMS     ... ``` ```plaintext AVSuite service    : CMS (DTIUser@10.2.0.0 : singleport)  - Managed by CMS ```