Troubleshooting connection limit, Connection limit rules with overlapping segments – H3C Technologies H3C SecPath F1000-E User Manual
Page 121
111
Troubleshooting connection limit
Connection limit rules with overlapping segments
1.
Symptom
On the SecPath, create a connection limit policy and configure two rules for the policy. One limits
connections from each host on segment 192.168.0.0/24 with the upper connection limit 10, and another
limits connections from 192.168.0.100 with the upper connection limit 100.
[SecPath-connection-limit-policy-0] limit 0 source ip 192.168.0.0 24 destination ip any
protocol ip max-connections 10 per-source
[SecPath-connection-limit-policy-0] limit 1 source ip 192.168.0.100 32 destination ip any
protocol ip max-connections 100 per-source
With the configuration, the host 192.168.0.100 can only initiate up to 10 connections to the external
network.
2.
Analysis
Both rules limit 0 and limit 1 contain the IP address 192.168.0.100, and the rule with a smaller ID is
matched first. Rule 0 is used for connections from 192.168.0.100.
3.
Solution
Rearrange the two connection limit rules by exchanging their rule IDs so that the rule for the host is
matched first.
Connection limit rules with overlapping protocol types
1.
Symptom
Internal server 192.168.0.100 provides both Web and FTP services for external users. On the SecPath,
create a connection limit policy and configure two rules, one limiting TCP connections to the server with
the upper limit 100 and the second limiting HTTP connections to the server with the upper limit 10000.
[SecPath-connection-limit-policy-0] limit 0 source ip any destination ip 192.168.0.100
protocol tcp max-connections 100
[SecPath-connection-limit-policy-0] limit 1 source ip any destination ip 192.168.0.100
protocol http max-connections 10000
With the configuration, 100 HTTP connections to the server can be established at most.
2.
Analysis
Both rules limit 0 and limit 1 involve HTTP connections, and the rule with a smaller ID is matched first.
Rule 0 is used for HTTP connections.
3.
Solution
Rearrange the two connection limit rules by exchanging their rule IDs so that the rule for HTTP
connections is matched first.