Linux Netfilter discussions
 help / color / mirror / Atom feed
From: Steven M Campbell <Netfilter@SCampbell.net>
To: Bgs <bgs@bgs.hu>
Cc: Ric Messier <kilroy@WasHere.COM>, netfilter@lists.netfilter.org
Subject: Re: syn DDoS attack solution
Date: Tue, 05 Jun 2007 10:16:40 -0400	[thread overview]
Message-ID: <46657048.4040600@SCampbell.net> (raw)
In-Reply-To: <46651F04.9020709@bgs.hu>

And, most important for folks here, do egress filtering on your 
firewall!    Help prevent zombie machines on your own networks from 
being a problem, you can't stop your end users from bringing infections 
into your network but you can control their spread.

Bgs wrote:
>  You can have defense against many kind of ddos attacks but victory is 
> not sure at all. Take the case for example when a very large number of 
> distributed bots issues many but slow SYN/ACK bounce attacks or plain 
> protocol connections to your site. If they do it 'right' you will end 
> up with up to millions of sources doing 'ordinary' things with random 
> sources. No source will ever trigger anything above an average user. 
> One important step in taking ddos seriously was when the first ISP 
> went broke because it was a target.
>
>  So take up the fight when it happens. Most attackers are not 
> resourceful enough (either by available hw/bots or technical 
> knowledge), so on the long term you can usually win. But loosing the 
> war is always a possibility no matter how good you are...
>
> Martin McKeay wrote:



  reply	other threads:[~2007-06-05 14:16 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
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 [this message]
2007-06-05 15:22                 ` ..prevention, was: " Arnt Karlsen
     [not found]                   ` <466583F4.8080107@SCampbell.net>
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=46657048.4040600@SCampbell.net \
    --to=netfilter@scampbell.net \
    --cc=bgs@bgs.hu \
    --cc=kilroy@WasHere.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox