3 ms·
FreeBSD had a more fun SYN cookie bug in 2015 (fixed here [1], and I think this is the diff where it was introduced [2]; determining which releases it touched i
by toast0 7y ago
FreeBSD had a more fun SYN cookie bug in 2015 (fixed here [1], and I think this is the diff where it was introduced [2]; determining which releases it touched is an exercise for the reader); the initial sequence of the sender had been left out.
I guess you would have a similar lack of dogs, but also, if a connection was opened and closed quickly, a re-transmitted packet from the client would satisfy the SYN cookie calculation, and the server would re-open the connection, but at it's original sequence number.
The details are a bit hazy, but the client would get an ACK with SEQ behind where it had ACKed, and would send an ACK probe with it's latest values. The server would see an ACK ahead of where it had sent, and send an ACK probe. If the hosts had low enough round trip times, the number of ACK probes sent could be tremendous. For those unfamiliar with FreeBSD, the localhost interface on FreeBSD runs full TCP, and under high load can drop packets and retransmit. We ran into this on localhost first, but then later across the internet with external clients.
[1] https://github.com/freebsd/freebsd/commit/56ba0a68edde7b38323f81f9d56998b10668dd9e https://github.com/freebsd/freebsd/commit/56ba0a68edde7b3832...
[2] https://github.com/freebsd/freebsd/commit/fc2be30b217171175bae209edb4f697cc0cb542d https://github.com/freebsd/freebsd/commit/fc2be30b217171175b...