Getting Started with Citrix ADC
Deploy a Citrix ADC VPX instance
Optimize Citrix ADC VPX performance on VMware ESX, Linux KVM, and Citrix Hypervisors
Apply Citrix ADC VPX configurations at the first boot of the Citrix ADC appliance in cloud
Install a Citrix ADC VPX instance on Microsoft Hyper-V servers
Install a Citrix ADC VPX instance on Linux-KVM platform
Prerequisites for Installing Citrix ADC VPX Virtual Appliances on Linux-KVM Platform
Provisioning the Citrix ADC Virtual Appliance by using OpenStack
Provisioning the Citrix ADC Virtual Appliance by using the Virtual Machine Manager
Configuring Citrix ADC Virtual Appliances to Use SR-IOV Network Interface
Configuring Citrix ADC Virtual Appliances to use PCI Passthrough Network Interface
Provisioning the Citrix ADC Virtual Appliance by using the virsh Program
Provisioning the Citrix ADC Virtual Appliance with SR-IOV, on OpenStack
Configuring a Citrix ADC VPX Instance on KVM to Use OVS DPDK-Based Host Interfaces
Deploy a Citrix ADC VPX instance on Microsoft Azure
Network architecture for Citrix ADC VPX instances on Microsoft Azure
Configure multiple IP addresses for a Citrix ADC VPX standalone instance
Configure a high-availability setup with multiple IP addresses and NICs
Configure a high-availability setup with multiple IP addresses and NICs by using PowerShell commands
Configure a Citrix ADC VPX instance to use Azure accelerated networking
Configure HA-INC nodes by using the Citrix high availability template with Azure ILB
Configure a high-availability setup with Azure external and internal load balancers simultaneously
Configure address pools (IIP) for a Citrix Gateway appliance
Upgrade and downgrade a Citrix ADC appliance
Authentication, authorization, and auditing application traffic
Basic components of authentication, authorization, and auditing configuration
On-premises Citrix Gateway as an identity provider to Citrix Cloud
Authentication, authorization, and auditing configuration for commonly used protocols
Troubleshoot authentication and authorization related issues
-
-
-
-
-
-
Persistence and persistent connections
Advanced load balancing settings
Gradually stepping up the load on a new service with virtual server–level slow start
Protect applications on protected servers against traffic surges
Retrieve location details from user IP address using geolocation database
Use source IP address of the client when connecting to the server
Use client source IP address for backend communication in a v4-v6 load balancing configuration
Set a limit on number of requests per connection to the server
Configure automatic state transition based on percentage health of bound services
Use case 2: Configure rule based persistence based on a name-value pair in a TCP byte stream
Use case 3: Configure load balancing in direct server return mode
Use case 6: Configure load balancing in DSR mode for IPv6 networks by using the TOS field
Use case 7: Configure load balancing in DSR mode by using IP Over IP
Use case 10: Load balancing of intrusion detection system servers
Use case 11: Isolating network traffic using listen policies
Use case 12: Configure Citrix Virtual Desktops for load balancing
Use case 13: Configure Citrix Virtual Apps for load balancing
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
Use case 15: Configure layer 4 load balancing on the Citrix ADC appliance
-
-
-
Configure content filtering for a commonly used deployment scenario
-
-
Authentication and authorization for System Users
-
Configuring a CloudBridge Connector Tunnel between two Datacenters
Configuring CloudBridge Connector between Datacenter and AWS Cloud
Configuring a CloudBridge Connector Tunnel Between a Datacenter and Azure Cloud
Configuring CloudBridge Connector Tunnel between Datacenter and SoftLayer Enterprise Cloud
Configuring a CloudBridge Connector Tunnel Between a Citrix ADC Appliance and Cisco IOS Device
CloudBridge Connector Tunnel Diagnostics and Troubleshooting
This content has been machine translated dynamically.
Dieser Inhalt ist eine maschinelle Übersetzung, die dynamisch erstellt wurde.(Haftungsausschluss)
Cet article a été traduit automatiquement de manière dynamique.(Clause de non responsabilité)
Este artículo lo ha traducido una máquina de forma dinámica.(Aviso legal)
此内容已经过机器动态翻译。放弃
このコンテンツは動的に機械翻訳されています。免責事項
이 콘텐츠는 동적으로 기계 번역되었습니다.책임 부인
Este texto foi traduzido automaticamente.(Aviso legal)
Questo contenuto è stato tradotto dinamicamente con traduzione automatica.(Esclusione di responsabilità))
This article has been machine translated.
Dieser Artikel wurde maschinell übersetzt.(Haftungsausschluss)
Ce article a été traduit automatiquement.(Clause de non responsabilité)
Este artículo ha sido traducido automáticamente.(Aviso legal)
この記事は機械翻訳されています.免責事項
이 기사는 기계 번역되었습니다.책임 부인
Este artigo foi traduzido automaticamente.(Aviso legal)
这篇文章已经过机器翻译.放弃
Questo articolo è stato tradotto automaticamente.(Esclusione di responsabilità))
Translation failed!
Configuring content filtering for a commonly used deployment scenario
This example provides instructions for using the configuration utility to implement a content filtering policy in which, if a requested URL contains root.exe or cmd.exe, the content filtering policyfilter-CF-nimda
is evaluated and the connection is reset.
To configure this content filtering policy, you must do the following:
- Enable content filtering
- Configure content filtering policy
- Bind content filtering policy globally or to a virtual server
- Verify the configuration
Note: Since this example uses a default content filtering action, you do not need to create a separate content filtering action.
Enable content filtering
- In the navigation pane, expand System, and click Settings.
- In the details pane, under Modes & Features, click Change Basic Features.
- In the Configure Basic Features dialog box, select the Content Filtering check box, and then click OK.
- In the Enable/Disable feature(s) dialog box, click Yes. A message appears in the status bar, stating that the selected feature is enabled.
Configure the content filtering policyfilter-CF-nimda
- Navigate to Security > Protection Features > Filter.
- In the details pane, click Add. The Create Filter Policy dialog box appears.
- In the Create Filter Policy dialog box, in the Filter Name text box, type the name
filter-CF-nimda
. - Select the Request Action option, and in the drop-down list, select RESET.
- In the Expression frame, select Match Any Expression from the drop-down list, and then click Add.
- In the Add Expression dialog box, Expression Type drop-down list, select General.
- In the Flow Type drop-down list, select REQ.
- In the Protocol drop-down list, select HTTP.
- In the Qualifier drop-down list, select URL.
- In the Operator drop-down list, select CONTAINS.
- In the Value text box, type cmd.exe, and then click OK. The expression is added in the Expression text box.
- To create another expression, repeat Steps 7 through 11, but in the Value text box, type root.exe. Then click OK, and finally click Close.
- Click Create on the Create Filter Policy dialog box. The filter policy
filter-CF-nimda
appears in the Filter list. - Click Close.
Globally bind the content filtering policy
- Navigate to Security > Protection Features > Filter. The Filter page appears in the right pane.
- In the details pane, Policies tab, select the policy that you want to bind and click Global Bindings. The Bind/Unbind Filter Policies dialog box appears.
- In the Bind/Unbind Filter Policies dialog box, in the Policy Name drop-down list, select the policy
filter-CF-nimda
, and click Add. The policy is added to the Configured list. - Click OK, and then click Close. The policy you have bound displays a check mark and Yes in the Globally Bound column of the Policies tab.
Bind the content filtering policy to a virtual server
- Navigate to Traffic Management > Load Balancing > Virtual Servers.
- In the details pane virtual servers list, select vserver-CF-1 to which you want to bind the content filtering policy and click Open.
- In the Configure Virtual Server (Load Balancing) dialog box, select the Policies tab.
- In the Active column, select the check box for the policy
filter-CF-nimda
, and then click OK. Your content filtering policy is now active, and must be filtering requests. If it is functioning correctly, the select counter is incremented every time there is a request for a URL containing either root.exe or cmd.exe. This allows you to confirm that your content filtering policy is working. The content filtering policy is bound to the virtual server.
Verify the content filtering configuration by using the command line interface
At the command prompt, type the following command to verify the content filtering configuration:
show filter policy filter-CF-nimda
Example:
sh filter policy filter-CF-nimda Name: filter-CF-nimda Rule: REQ.HTTP.URL CONTAINS cmd.exe || REQ.HTTP.URL CONTAINS root.exe Request action: RESET Response action: Hits: 0 Done
Note
The select counter displays an integer that denotes the number of times the
filter-CF-nimda
policy is evaluated. In the preceding steps, the select counter is set to zero because no requests for a URL containing either cmd.exe or root.exe has been made yet. If you want to see the counter increment in real time, you can simply request a URL that contains either of these strings.
Verify the content filtering configuration by using the GUI
Navigate toSecurity > Protection Features > Filter.
In the details pane, select the filter policy
filter-CF-nimda
. The bottom of the pane must display the following:
**Request Action:** RESET **Rule:** REQ.HTTP.URL CONTAINS cmd.exe || REQ.HTTP.URL CONTAINS root.exe **Hits:** 0
Share
Share
In this article
- Enable content filtering
- Configure the content filtering policy filter-CF-nimda
- Globally bind the content filtering policy
- Bind the content filtering policy to a virtual server
- Verify the content filtering configuration by using the command line interface
- Verify the content filtering configuration by using the GUI
This Preview product documentation is Citrix Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Citrix Beta/Tech Preview Agreement.
The development, release and timing of any features or functionality described in the Preview documentation remains at our sole discretion and are subject to change without notice or consultation.
The documentation is for informational purposes only and is not a commitment, promise or legal obligation to deliver any material, code or functionality and should not be relied upon in making Citrix product purchase decisions.
If you do not agree, select Do Not Agree to exit.