From: "Rene Nielsen" <rbn@vitesse.com>
To: <ecos-discuss@sourceware.org>
Subject: [ECOS] BSD TCP/IP Stack & SYN Flooding
Date: Mon, 25 May 2009 08:15:00 -0000 [thread overview]
Message-ID: <376637F07F8A9242AD11921B15FA17DC924ACF@mx-dk.vsc.vitesse.com> (raw)
Hi folks,
I have a question regarding TCP SYN Flooding attacks.
To my understanding these attacks come in two flavors:
1) The attacker sends SYN packets only, leaving the connection
half-open.
2) The attacker sends SYN packets and ACKs the SYN-ACK from the server,
effectively opening the connection (this is probably not a real SYN
flood attack, but nevertheless it takes server-side resources...).
Are there any remedies in the eCos' BSD TCP/IP stack to overcome such
attacks (e.g. SYN cache/cookies as suggested by RFC4987 to remedy attack
type #1, timeouts, etc.)?
Regards,
Rene Schipp von Branitz Nielsen
Vitesse Semiconductors
--
Before posting, please read the FAQ: http://ecos.sourceware.org/fom/ecos
and search the list archive: http://ecos.sourceware.org/ml/ecos-discuss
reply other threads:[~2009-05-25 8:15 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=376637F07F8A9242AD11921B15FA17DC924ACF@mx-dk.vsc.vitesse.com \
--to=rbn@vitesse.com \
--cc=ecos-discuss@sourceware.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).