The system default is 500 SYNs/sec. You can manually change that Threshold per SPP down to 0 but I would not recommend it unless testing. Make sure SPP Settings > General Tab has SYN Flood Mitigation direction inbound enabled and SPP Settings > TCP Tab has SYN Validation enabled.
Make sure SPP Settings > General Tab has SYN Flood Mitigation direction inbound enabled and SPP Settings > TCP Tab has SYN Validation enabled.
Even 500 SYNs/sec should not have much impact on your servers. If small numbers of SYNs are affecting your servers, it might be slow attacks where you need to see if SPP Settings > Aggressive Aging Feature Control > Track Slow Connections is enabled and in the Global Settings > Settings > Settings > Slow Connections is set to something other than "none" - "Moderate" is a good start.
I'm assuming here you are asking how low you can set the detection of bad SYNs. When the number of SYNs crosses the threshold the system attempts to validate the Sources of those SYNs using the algorithm defined in SPP Settings > SPP settings > General: SYN Cookie (recommended), ACK Cookie or SYN retransmission. If the SYN is real, the Source IP is added to a legitimate IP table but the first SYN is lost and the browser or client needs to send another SYN to start the connection.
If you can explain the actual problem, it might be easier to find an answer.
The system default is 500 SYNs/sec. You can manually change that Threshold per SPP down to 0 but I would not recommend it unless testing. Make sure SPP Settings > General Tab has SYN Flood Mitigation direction inbound enabled and SPP Settings > TCP Tab has SYN Validation enabled.
Make sure SPP Settings > General Tab has SYN Flood Mitigation direction inbound enabled and SPP Settings > TCP Tab has SYN Validation enabled.
Even 500 SYNs/sec should not have much impact on your servers. If small numbers of SYNs are affecting your servers, it might be slow attacks where you need to see if SPP Settings > Aggressive Aging Feature Control > Track Slow Connections is enabled and in the Global Settings > Settings > Settings > Slow Connections is set to something other than "none" - "Moderate" is a good start.
I'm assuming here you are asking how low you can set the detection of bad SYNs. When the number of SYNs crosses the threshold the system attempts to validate the Sources of those SYNs using the algorithm defined in SPP Settings > SPP settings > General: SYN Cookie (recommended), ACK Cookie or SYN retransmission. If the SYN is real, the Source IP is added to a legitimate IP table but the first SYN is lost and the browser or client needs to send another SYN to start the connection.
If you can explain the actual problem, it might be easier to find an answer.
Select Forum Responses to become Knowledge Articles!
Select the “Nominate to Knowledge Base” button to recommend a forum post to become a knowledge article.
User | Count |
---|---|
1742 | |
1113 | |
759 | |
447 | |
241 |
The Fortinet Security Fabric brings together the concepts of convergence and consolidation to provide comprehensive cybersecurity protection for all users, devices, and applications and across all network edges.
Copyright 2025 Fortinet, Inc. All Rights Reserved.