-
Getting Started with NetScaler
-
Solutions for Telecom Service Providers
-
Load Balance Control-Plane Traffic that is based on Diameter, SIP, and SMPP Protocols
-
Provide Subscriber Load Distribution Using GSLB Across Core-Networks of a Telecom Service Provider
-
Authentication, authorization, and auditing application traffic
-
Basic components of authentication, authorization, and auditing configuration
-
-
Web proxy support for outbound calls to IDP or third party endpoints
-
Web Application Firewall protection for VPN virtual servers and authentication virtual servers
-
On-premises NetScaler Gateway as an identity provider to Citrix Cloud™
-
Authentication, authorization, and auditing configuration for commonly used protocols
-
Troubleshoot authentication and authorization related issues
-
Troubleshoot authentication, authorization and auditing issues
-
Configure EULA as an authentication factor in NetScaler nFactor system
-
Configure periodic Endpoint Analysis scan as a factor in nFactor authentication
-
Configure post-authentication Endpoint Analysis scan as a factor in NetScaler nFactor authentication
-
Configure pre-authentication Endpoint Analysis scan as a factor in nFactor authentication
-
Configure pre-auth and post-auth EPA scan as a factor in nFactor authentication
-
Configure prefill user name from certificate in NetScaler nFactor authentication
-
Configure protected user as an authentication factor in NetScaler nFactor authentication
-
Localize error messages generated by NetScaler nFactor system
-
Configure NetScaler Gateway preauthentication EPA scan for the domain check
-
-
-
-
-
-
-
Configure DNS resource records
-
Configure NetScaler as a non-validating security aware stub-resolver
-
Jumbo frames support for DNS to handle responses of large sizes
-
Caching of EDNS0 client subnet data when the NetScaler appliance is in proxy mode
-
Use case - configure the automatic DNSSEC key management feature
-
Use Case - configure the automatic DNSSEC key management on GSLB deployment
-
-
-
Source IP address whitelisting for GSLB communication channels
-
Use case: Deployment of domain name based autoscale service group
-
Use case: Deployment of IP address based autoscale service group
-
-
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 and Desktops for load balancing
-
Use case 14: ShareFile wizard for load balancing Citrix ShareFile
-
Use case 15: Configure layer 4 load balancing on the NetScaler appliance
-
-
-
-
Support for hybrid Post Quantum cryptography on the frontend
-
-
Create a certificate signing request and use SSL certificates on a NetScaler appliance
-
Configure SSL acceleration with HTTP on the front end and SSL on the back end
-
Export certificates used on a NetScaler appliance as PFX file
-
Configure SSL monitoring when client authentication is enabled on the back-end service
-
Configure SSL action to forward client traffic if a cipher is not supported on the ADC
-
Configure synchronization of files in a high availability setup
-
-
-
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 NetScaler 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!
Simple ACLs and Simple ACL6s
A simple ACL or simple ACL6 uses few parameters and can be configured only to drop IP packets. Packets can be dropped based on their source IP address and, optionally, their protocol, destination port, or traffic domain.
When creating a simple ACL or simple ACL6, you can specify a time to live (TTL), in seconds, after which the ACL expires. ACLs with TTLs are not saved when you save the configuration. You can display simple ACLs and simple ACL6s to verify their configuration, and you can display their statistics.
Configuring Simple ACLs and Simple ACL6s
Configuring a simple ACL or simple ACL6 on a NetScaler can include the following tasks.
- Create simple ACLs or simple ACL6s. Creating simple ACLs or simple ACL6s to drop (deny) packets based on their source IP address and, optionally, their protocol, destination port, or traffic domain.
- Remove simple ACLs or simple ACL6s. These ACLs cannot be modified once created. If you must modify a simple ACL or simple ACL6, you must remove it and create a one.
CLI procedures
To create a simple ACL by using the CLI:
At the command prompt, type:
add ns simpleacl <aclname> <aclaction> [-td <positive_integer>] -srcIP <ip_addr> [-destPort <port> -protocol (TCP | UDP)] [-TTL <positive_integer>]
show ns simpleacl [<aclname>]
<!--NeedCopy-->
Example:
add ns simpleacl rule1 DENY -srcIP 10.102.29.5 -TTL 600
Done
<!--NeedCopy-->
To create a simple ACL6 by using the CLI:
At the command prompt, type:
add ns simpleacl6 <aclname> <aclaction> -srcIPv6 <ipv6_addr|null> [-destPort <port> -protocol ( TCP | UDP )] [-TTL <positive_integer>]
show ns simpleacl6 [<aclname>]
<!--NeedCopy-->
Example:
add ns simpleacl6 rule1 DENY –srcIPv6 3ffe:192:168:215::82 -destPort 80 -Protocol TCP -TTL 9000
Done
<!--NeedCopy-->
To remove a single simple ACL by using the CLI:
At the command prompt, type:
- rm ns simpleacl <aclname>
- show ns simpleacl
To remove a single simple ACL6 by using the CLI:
At the command prompt, type:
- rm ns simpleacl6<aclname>
- show ns simpleacl6
To remove all simple ACLs by using the CLI:
At the command prompt, type:
-
clear ns simpleacl
-
show ns simpleacl
To remove all simple ACL6s by using the CLI:
At the command prompt, type:
-
clear ns simpleacl6
-
show ns simpleacl6
GUI procedures
To create a simple ACL by using the GUI:
Navigate to System > Network > ACLs and, on the Simple ACLs tab, add a new simple ACL.
To create a simple ACL6 by using the GUI:
Navigate to System > Network > ACLs and, on the Simple ACL6s tab, add a new simple ACL6.
To remove a single simple ACL by using the GUI:
Navigate to System > Network > ACLs and, on the Simple ACLs tab, delete the simple ACL.
To remove a single simple ACL6 by using the GUI:
Navigate to System > Network > ACLs and, on the Simple ACL6s tab, delete the simple ACL6.
To remove all simple ACLs by using the GUI:
- Navigate to System > Network > ACLs.
- On the Simple ACLs tab, in the Action list, click Clear.
To remove all simple ACL6s by using the GUI:
- Navigate to System > Network > ACLs.
- On the Simple ACL6s tab, in the Action list, click Clear.
Displaying Simple ACL and Simple ACL6 Statistics
You can display the simple ACL (or simple ACL6) statistics, which include the number of matches, the number of misses, and the number of simple ACLs configured.
The following table describes the statistics that you can display for simple ACLs and simple ACL6s.
| Statistics | Indicates |
|---|---|
| ACL match | Packets matching an ACL |
| ACL misses | Packets not matching any ACL |
| ACL count | Number of ACLs that are configured |
CLI procedures
To display simple ACL statistics by using the CLI:
At the command prompt, type:
- stat ns simpleacl
Example:
> stat ns simpleacl
SimpleACL Statistics
Rate (/s) Total
SimpleACL hits 0 0
SimpleACL misses 0 51872
SimpleACLs count -- 2
Done
<!--NeedCopy-->
To display simple ACL6 statistics by using the CLI:
At the command prompt, type:
- stat ns simpleacl6
GUI procedures
To display simple ACL statistics by using the GUI:
Navigate to System > Network > ACLs and, on the Simple ACLs tab, select the ACL and click Statistics.
To display simple ACL6 statistics by using the GUI:
Navigate to System > Network > ACLs and, on the Simple ACL6s tab, select the simple ACL6 and click Statistics.
Terminating Established Connections
For a simple ACL or simple ACL6, the NetScaler blocks any new connections that match the conditions specified in the ACL. Packets related to existing connections that were established before the ACL was created are not blocked. To terminate previously established connections that match an existing ACL, you can run a flush operation from the CLI or the GUI.
Flush can be useful in the following cases:
- You receive a list of blacklisted IP addresses and want to completely block those IP addresses from accessing the NetScaler. In this case, you create simple ACLs or simple ACL6s to block any new connections from these IP addresses, and then flush any existing connections associated with those addresses.
- You want to terminate many connections from a particular network without taking the time to terminate them one by one.
Before you begin
-
When you run flush, the NetScaler searches through all of its established connections and terminates the connections that match the conditions specified in any of the simple ACLs configured on the ADC.
-
If you plan to create more than one simple ACL and flush existing connections that match any of them, you can minimize the effect on performance by first creating all simple ACLs and then running flush only once.
CLI procedures
To terminate all established IPv4 connections that match any of your configured simple ACLs by using the CLI:
At the command prompt, type:
- flush simpleacl -estSessions
To terminate all established IPv6 connections that match any of your configured simple ACL6s by using the CLI:
At the command prompt, type:
- flush simpleacl6 -estSessions
GUI procedures
To terminate all established IPv4 connections that match any of your configured simple ACLs by using the GUI:
- Navigate to System > Network > ACLs.
- On the Simple ACLs tab, in the Action list, click Flush.
To terminate all established IPv6 connections that match any of your configured simple ACL6s by using the GUI:
- Navigate to System > Network > ACLs.
- On the Simple ACL6s tab, in the Action list, click Flush.
Share
Share
This Preview product documentation is Cloud Software Group Confidential.
You agree to hold this documentation confidential pursuant to the terms of your Cloud Software Group 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 Cloud Software Group product purchase decisions.
If you do not agree, select I DO NOT AGREE to exit.