Linux Netfilter discussions
 help / color / mirror / Atom feed
From: "Taylor, Grant" <gtaylor@riverviewtech.net>
To: "R. DuFresne" <dufresne@sysinfo.com>
Cc: Vic N <vic778@hotmail.com>, netfilter@lists.netfilter.org
Subject: Re: ddos / no connection tracking / tarpitting
Date: Fri, 22 Apr 2005 17:28:55 -0500	[thread overview]
Message-ID: <42697AA7.7030802@riverviewtech.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0504221707050.15167@darkstar.sysinfo.com>

> the only way to really survive a ddos without affecting connectivity in 
> any shapoe or form is to have a bigger pipe then the other end<s> does. 
> idiots trying to ddos from a cable connection or dialup are not a 
> problem and sufferable.  Those a tad higher in technical advancement 
> with a bot net and tousands of zomies to attack from are likely to bring 
> even the biggest pipes to a dead halt, at least getting in and our of 
> the firewall gateway is impossible.  Traffic on the inside should be 
> unaffected.

One thing that I (personally) am trying to do (sort of) along these lines is to host a co-lo box at my ISP's facility and establish a GRE tunnel between my home system and this box and ultimately use an endpoint on this CO-LOed box as my default gateway.  This way I can set up QoS and specify what traffic is important to me and what has priority on what comes down my DSL pipe in a round about way.  Fortunetly I have an EXCELLENT working relationship, both professionally and personally, with my ISP and they would be willing to do such as well as drop any traffic that is destined to my DSL connection that did not come from the CO-LOed box.  This round about way would give me sufficient control over what traffic did flow down the DSL pipe to my house and thus mitigate DDoSing my DSL.  However seeing as my ISP only has 16 Mbps connection to the net it would not take much to DDoS them if it r
 eally came down to it.  But my DSL would not be DDoSed, just my ISP's upstream connection
.  I know that this is not a real elegant solution, but I never did say that it was, just something that might work.  ;)



Grant. . . .


  parent reply	other threads:[~2005-04-22 22:28 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-04-22  4:19 ddos / no connection tracking / tarpitting Vic N
2005-04-22  4:32 ` Jason Opperisano
2005-04-22  4:45   ` Taylor Grant
2005-04-22  5:01     ` Jason Opperisano
2005-04-22  5:22 ` Taylor Grant
2005-04-22  6:50   ` Jozsef Kadlecsik
2005-04-22  6:52     ` Taylor Grant
2005-04-22 21:13   ` R. DuFresne
2005-04-22 22:12     ` Seferovic Edvin
     [not found]     ` <42697714.011dd32f.69e7.219fSMTPIN_ADDED@mx.gmail.com>
2005-04-22 22:18       ` Fabien Germain
2005-04-22 22:28     ` Taylor, Grant [this message]
2005-04-22 23:05     ` Daniel Lopes
  -- strict thread matches above, loose matches on Subject: below --
2005-04-22  7:01 Gary W. Smith
2005-04-22  7:05 Gary W. Smith
2005-04-22  7:10 ` Taylor Grant
2005-04-22  7:32 ` Jozsef Kadlecsik

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=42697AA7.7030802@riverviewtech.net \
    --to=gtaylor@riverviewtech.net \
    --cc=dufresne@sysinfo.com \
    --cc=netfilter@lists.netfilter.org \
    --cc=vic778@hotmail.com \
    /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