summaryrefslogtreecommitdiffstats
path: root/README
diff options
context:
space:
mode:
authorjesper <jesper@FreeBSD.org>2001-06-06 19:41:51 +0000
committerjesper <jesper@FreeBSD.org>2001-06-06 19:41:51 +0000
commit9d59cfc3ee87b6d49e394d8c495a0f2ace1603b1 (patch)
tree84d5c3add837da8f6ba159e80c9b7365a6f0713a /README
parent27fe392810ba2ac168eda24e720e547fb5e35f72 (diff)
downloadFreeBSD-src-9d59cfc3ee87b6d49e394d8c495a0f2ace1603b1.zip
FreeBSD-src-9d59cfc3ee87b6d49e394d8c495a0f2ace1603b1.tar.gz
Silby's take one on increasing FreeBSD's resistance to SYN floods:
One way we can reduce the amount of traffic we send in response to a SYN flood is to eliminate the RST we send when removing a connection from the listen queue. Since we are being flooded, we can assume that the majority of connections in the queue are bogus. Our RST is unwanted by these hosts, just as our SYN-ACK was. Genuine connection attempts will result in hosts responding to our SYN-ACK with an ACK packet. We will automatically return a RST response to their ACK when it gets to us if the connection has been dropped, so the early RST doesn't serve the genuine class of connections much. In summary, we can reduce the number of packets we send by a factor of two without any loss in functionality by ensuring that RST packets are not sent when dropping a connection from the listen queue. Submitted by: Mike Silbersack <silby@silby.com> Reviewed by: jesper MFC after: 2 weeks
Diffstat (limited to 'README')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud