Skip to contentSkip to conversation

Size of Tasks during ddos

DISCUSSION Andi Kleen 1 participant 1 message Sep 11, 2003 11 messages not in the archive

lore
Share & tools
lore

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

A message that is not in the archive (sent off-list or not yet received): [email protected]

Andi Kleen

author
#11 lore raw
Quoted 11 lines · Alan Cox

Syn cookies accept the SYN frame and encode sufficient information into the reply that they can avoid storing any data until the next packet arrives from the other end completing the connection.

That means squashing all the information we track (mss, window, etc) into very few bits. A modern TCP will offer large windows, selective ack and other features which we can't fit into a syn cookie so with this off a burst of traffic will cause pauses while the socket queue clears and negotiate fully featured TCP, with syncookies enabled many of the connections on the burst will not have the extra features so many not perform as well.

Another side effect of syncookies is that flow control for new connections breaks: when you have a client that is connecting to a overloaded server it will only notice this after a long timeout. With syncookies off you get actually useful errnos back on connect().

(overloaded here doesn't necessarily mean DoS, just e.g. a single threaded service that is taking a long time to do some job and expresses this with a small argument to listen())

-Andi