All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Ric Messier" <kilroy@WasHere.COM>
To: "'R. DuFresne'" <dufresne@sysinfo.com>, 'Bgs' <bgs@bgs.hu>
Cc: netfilter@lists.netfilter.org
Subject: RE: syn DDoS attack solution
Date: Mon, 4 Jun 2007 08:22:05 -0600	[thread overview]
Message-ID: <00f101c7a6b3$bac44450$304cccf0$@COM> (raw)
In-Reply-To: <Pine.LNX.4.64.0706021446290.18235@darkstar.sysinfo.com>


R. DuFresne writes:
> There have been and will continue to be some
> rather decently funded companies with some fairly decent pipes wiped
> out
> of business or their internet presence closed up due to some of these
> kinds of attacks over extended periods of time.  Goverments across the
> globe have had internet services disrupted for extended periods.
> Microsoft has had to relocate servers to new net/ip addresses to divert
> the flow from such attacks and stay somewhat online...
> 

I won't even tell you what we ended up having to do to get the first large,
commercial DDoS targets back online (Stacheldraht, anyone). The great thing
about DoS attacks is that they tend to be self-propagating. In order to get
them to go away, you generally end up doing things that kills legitimate
connections. Just a casualty of war. Either that or you ride them out.
Invariably, you have to go upstream to get help in stopping them if they are
worth noticing.

Ric




  reply	other threads:[~2007-06-04 14:22 UTC|newest]

Thread overview: 34+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-05-31 16:19 syn DDoS attack solution Bgs
2007-05-31 19:57 ` 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 [this message]
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='00f101c7a6b3$bac44450$304cccf0$@COM' \
    --to=kilroy@washere.com \
    --cc=bgs@bgs.hu \
    --cc=dufresne@sysinfo.com \
    --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.