-
-
-
Blocking Traffic on Internal Ports
-
Configure to source NetScaler FreeBSD data traffic from a SNIP address
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!
Blocking Traffic on Internal Ports
By default, a NetScaler appliance does not block some type of internal traffic even using ACL rules.
The following table lists the internal traffic types that a NetScaler appliance does not block even using ACL rules:
NetScaler Setup | Protocol | Destination Port | Destination IP address |
---|---|---|---|
All | TCP | 3008–3011 | NSIP or SNIP |
All | TCP | 179 | NSIP or SNIP |
All | UDP | 520 | NSIP or SNIP |
High availability | UDP | 3003 | NSIP |
High availability | TCP | 22 | NSIP |
Cluster | UDP | 7000 | NSIP |
This feature of not blocking the earlier mentioned types of traffic is specified by the default setting of the global Layer-3 Implicit ACL Allow
(implicitACLAllow
) parameter.
You can disable this parameter if you want to block the earlier mentioned traffic types using the ACL rules. An appliance in a high availability setup makes an exception for its partner (primary or secondary) node. It does not block traffic from that node.
To disable or enable this parameter by using the CLI:
At the command prompt, type:
-
set l3param -implicitACLAllow [ENABLED DISABLED] - sh l3param
Note: The parameter implicitACLAllow is enabled by default.
Example:
> set l3param -implicitACLAllow DISABLED
Done
<!--NeedCopy-->
Share
Share
In this article
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.