From: Bgs <bgs@bgs.hu>
To: netfilter@lists.netfilter.org
Subject: syn DDoS attack solution
Date: Thu, 31 May 2007 18:19:14 +0200 [thread overview]
Message-ID: <465EF582.4070904@bgs.hu> (raw)
Hi all,
We recently got under a low traffic botnet DDoS attack. All attacker
nodes opened a single tcp session (just SYN part) and then did nothing.
This rules out rate limiting solutions and syncookie doesn't help
either. (Thousands of attacking nodes).
I'd like to know you thoughts about two possible approaches in solving
this:
- syn proxy: already used for example by Cisco. The router handles the
first part of the connection and only routes packets to the client if
the connection seems good. (Good against single/spoofed incoming SYNs
but may be used to wait for the first packet with actual data as well).
- Implement a conntrack solution that gives a timestamp to the
connection. Then this timestamp could be used to drop the connection if
no data arrives within a configured time limit (good for open inactive
connections only). Of course appropriate close toward the local client
has to be done as well.
What's your opinion?
Bye
Bgs
next reply other threads:[~2007-05-31 16:19 UTC|newest]
Thread overview: 34+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-31 16:19 Bgs [this message]
2007-05-31 19:57 ` syn DDoS attack solution R. DuFresne
2007-06-01 9:45 ` Bgs
2007-05-31 20:08 ` Ric Messier
2007-06-01 1:20 ` Tony.Ho
2007-06-01 9:44 ` Bgs
2007-06-01 15:01 ` Ric Messier
2007-06-01 15:37 ` Bgs
2007-06-02 19:07 ` R. DuFresne
2007-06-04 14:22 ` Ric Messier
2007-06-04 17:24 ` Martin McKeay
2007-06-04 23:16 ` R. DuFresne
2007-06-05 8:29 ` Bgs
2007-06-05 14:16 ` Steven M Campbell
2007-06-05 15:22 ` ..prevention, was: " Arnt Karlsen
2007-06-05 15:40 ` Steven M Campbell
2007-06-05 15:40 ` Steven M Campbell
2007-06-05 18:34 ` Arnt Karlsen
2007-06-07 18:41 ` Martin McKeay
2007-06-08 1:40 ` Arnt Karlsen
2007-06-12 18:10 ` Martin McKeay
2007-06-12 22:44 ` R. DuFresne
2007-06-13 14:24 ` Martin McKeay
2007-06-13 17:26 ` Arnt Karlsen
2007-06-13 17:44 ` Martin McKeay
2007-06-14 19:43 ` R. DuFresne
2007-06-14 20:13 ` supportnew
2007-06-01 21:34 ` Martijn Lievaart
2007-06-01 21:37 ` Martijn Lievaart
2007-06-01 21:38 ` Ric Messier
2007-06-01 23:09 ` Ethy H. Brito
2007-06-19 18:22 ` R. DuFresne
2007-06-19 22:19 ` Robert Nichols
2007-06-19 23:02 ` Pascal Hambourg
2007-06-21 18:26 ` R. DuFresne
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=465EF582.4070904@bgs.hu \
--to=bgs@bgs.hu \
--cc=netfilter@lists.netfilter.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.