您不能将会话数限制为策略 - 无法从“坏”会话中确定“好”会话。
根据服务(假设是 Web 服务器),您可以简单地限制它将在服务器上接受的连接数 - 这可以在 Apache、NGINX、IIS 等中完成 - 您甚至应该能够应用限制基于源是在防火墙内部还是外部。
另一种选择可能是将速率限制应用于 SRX 上的特定策略 - 这样,如果它是吸引最多流量的特定服务,您可以对其提供的带宽量设置硬限制。
这可以通过客户端到服务器或服务器到客户端来完成。
为此,请设置应用程序流量控制配置文件,然后在允许后在您的策略中引用它,例如:
set security policies from-zone INTERNET to-zone DMZ policy PERMIT-SERVER1 match source-address any
set security policies from-zone INTERNET to-zone DMZ policy PERMIT-SERVER1 match destination-address SERVER1
set security policies from-zone INTERNET to-zone DMZ policy PERMIT-SERVER1 match application junos-http
set security policies from-zone INTERNET to-zone DMZ policy PERMIT-SERVER1 match application junos-https
set security policies from-zone INTERNET to-zone DMZ policy PERMIT-SERVER1 then permit application-services application-traffic-control rule-set INTERNET-LIMITS
set security policies from-zone INTERNET to-zone DMZ policy PERMIT-SERVER1 then log session-init
set security policies from-zone INTERNET to-zone DMZ policy PERMIT-SERVER1 then log session-close
set security policies from-zone INTERNET to-zone DMZ policy PERMIT-SERVER1 then count
set class-of-service application-traffic-control rate-limiters 10M bandwidth-limit 10485760
set class-of-service application-traffic-control rate-limiters 10M burst-size-limit 524288
set class-of-service application-traffic-control rule-sets INTERNET-LIMITS rule WEB-10M match application junos-http
set class-of-service application-traffic-control rule-sets INTERNET-LIMITS rule WEB-10M match application junos-https
set class-of-service application-traffic-control rule-sets INTERNET-LIMITS rule WEB-10M then rate-limit server-to-client 10M
这会将从 SERVER1 到客户端的所有流量限制为 10M,这不会限制会话,而是减慢它们的速度,以免它们使用您的所有上游带宽。