Linux Netfilter discussions
 help / color / mirror / Atom feed
From: alvin.ml@Mail.DDoS-Mitigator.net
To: Antonio Prado <thinkofit@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: iptables TCP DDoS filtering
Date: Wed, 6 Jul 2016 10:45:40 -0700	[thread overview]
Message-ID: <20160706174540.GA610@Mail.DDoS-Mitigator.net> (raw)
In-Reply-To: <6a0dd625-fe5a-d3df-bf33-75a39613fa5b@gmail.com>


hi antonio

On 07/06/16 at 05:36pm, Antonio Prado wrote:
> 
> at BGP level, when an AS is DDoSed with a 10Gbps rate (or maybe more),

10Gbps ( bits/sec ) is not that big of an ISP but still not ez to DDoS

it seems, some of the ISPs like to use RTBH for DDoS mitigation, but,
that'd still imply they received the DDoS packets in order that they
can /dev/null it ...

i wonder why they don't traceroute back to the original attacker
and have the local law enforcement come knocking on the door ..
i ISP know where all the packets is coming from that they in turn 
fwd to the next hop

> /usually/ there is a lot of gear inside an ISP that becomes unresponsive
> before it can reach an iptables/firewall/ddos-mitigation box

yup

> so, dealing with iptables to sort out some local rate-limit effect
> (until the pipe is not full) is ok, but it's useless if ASes don't
> adhere to BCP38 or if they don't deploy BGPSec (for instance)

yup

magic pixie dust
alvin

  reply	other threads:[~2016-07-06 17:45 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-05  6:53 iptables TCP DDoS filtering Josh Day
2016-07-05 19:08 ` alvin.ml
2016-07-06  7:07   ` John Wayne
2016-07-06 15:16     ` alvin.ml
2016-07-05 20:51 ` Neal P. Murphy
2016-07-06  8:29 ` Antonio Prado
2016-07-06 14:21   ` alvin.ml
2016-07-06 15:36     ` Antonio Prado
2016-07-06 17:45       ` alvin.ml [this message]
2016-07-06 19:13         ` Neal P. Murphy

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=20160706174540.GA610@Mail.DDoS-Mitigator.net \
    --to=alvin.ml@mail.ddos-mitigator.net \
    --cc=netfilter@vger.kernel.org \
    --cc=thinkofit@gmail.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