--- title: "Enabling HTTP proxy settings on a dual-port managed appliance using the CLI" slug: "enabling-http-proxy-settings-on-a-dual-port-managed-appliance-using-the-cli-2" tags: ["Product Usage", "CMS 11.x", "EX 11.x", "FX 11.x", "AX 11.x", "NX 11.x", "IVX 11.x", "Network Security"] updated: 2026-08-24T20:40:08Z published: 2026-08-24T20:40:08Z canonical: "docs.trellix.com/enabling-http-proxy-settings-on-a-dual-port-managed-appliance-using-the-cli-2" 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. # Enabling HTTP proxy settings on a dual-port managed appliance using the CLI Use the commands in this topic to enable a managed appliance that uses dual-port communication to send DTI service requests through an HTTP proxy server. > [!NOTE] > Note > > When the appliance uses dual-port communication, requests can either be sent directly to the HTTP proxy, or through the Central Management System appliance to the HTTP proxy (the default behavior). **To enable HTTP proxy settings for a DTI service:** 1. Go to CLI configuration mode: ``` hostname > enable hostname # configure terminal ``` 2. View the current DTI service configuration: ``` hostname (config) # show fenet dti configuration brief ``` 3. *To send DTI service requests directly to the HTTP proxy (optional)*: Move control of the DTI service to the managed appliance. - For the `download` service: ``` hostname (config) # no fenet dti source override enable ``` - For the `enrollment`, `faude`, `mil`, or `virtual` service: ``` hostname (config) # no fenet dti service override enable ``` - For the `upload destination` service: ``` hostname (config) # no fenet dti upload destination override enable ``` 4. View the current DTI service configuration: ``` hostname (config) # show fenet dti configuration brief ``` 5. If the value for the service in the `ACTIVE SETTINGS FOR HTTP PROXY` section is `no`, enable proxy settings for the service. - For the `source` service: ``` hostname (config) # fenet dti source proxy enable ``` - For the `enrollment`, `faude`, or `virtual` service: ``` hostname (config) # fenet dti service proxy enable ``` - For the `upload destination` service: ``` hostname (config) # fenet dti upload destination proxy enable ``` 6. Verify your changes: ``` hostname (config) # show fenet dti configuration brief ``` 7. Save your changes: ``` hostname (config) # write memory ``` ### Examples The following example moves control of the `source` service to the managed appliance. This allows the managed appliance to bypass the Central Management System appliance and send requests for software updates directly to the HTTP proxy server. ``` hostname (config) # show fenet dti configuration brief DTI CLIENT CONFIGURATIONS:  ACTIVE SETTINGS:        Mode               : online    Download source    : CMS (User8@10.4.5.6) - Managed by CMS    ...  ACTIVE SETTINGS FOR HTTP PROXY:    Http proxy         : @myproxy.mycompany.com:8080 (user agent:)    Download source    : yes    ... hostname (config) # no fenet dti source override enable hostname (config) # show fenet dti configuration brief DTI CLIENT CONFIGURATIONS:  ACTIVE SETTINGS:        Mode               : online    Download source    : DTI (User8@staticcloud.fireeye.com) - Managed by Appliance    ...  ACTIVE SETTINGS FOR HTTP PROXY:    Http proxy         : @myproxy.mycompany.com:8080 (user agent:)    Download source    : yes    ... ``` The following example re-enables HTTP proxy settings for the `faude` service. In this example, the Central Management System appliance controls the DTI services, so DTI requests are sent to the HTTP proxy through the Central Management System appliance. ``` hostname (config) # show fenet dti configuration brief DTI CLIENT CONFIGURATIONS:  ACTIVE SETTINGS:        Mode               : online    Download source    : CMS (User8@10.4.5.6) - Managed by CMS    Upload destination : CMS (User8@10.4.5.6) - Managed by CMS    Mil service        : CMS (User8@10.4.5.6) - Managed by CMS    Faude service      : CMS (User8@10.4.5.6) - Managed by CMS    ...  ACTIVE SETTINGS FOR HTTP PROXY:    Http proxy         : @myproxy.mycompany.com:8080 (user agent:)    Download source    : yes    Upload destination : yes    Mil service        : yes    Faude service      : no (reason: administratively disabled)      ... hostname (config) # fenet dti faude service proxy enable hostname (config) # show fenet dti configuration brief DTI CLIENT CONFIGURATIONS:  ACTIVE SETTINGS:        Mode               : online    Download source    : CMS (User8@10.4.5.6) - Managed by CMS    Upload destination : CMS (User8@10.4.5.6) - Managed by CMS    Mil service        : CMS (User8@10.4.5.6) - Managed by CMS    Faude service      : CMS (User8@10.4.5.6) - Managed by CMS    ...  ACTIVE SETTINGS FOR HTTP PROXY:    Http proxy         : @myproxy.mycompany.com:8080 (user agent:)    Download source    : yes    Upload destination : yes    Mil service        : yes    Faude service      : yes    ... ```