From: Feizhou <feizhou@linuxmail.org>
To: Alex Sirbu <alex@as.ro>
Cc: netfilter@lists.netfilter.org
Subject: Re: over a 1,000,000,000 individual ips to block
Date: Mon, 28 Jun 2004 21:36:25 +0800 [thread overview]
Message-ID: <40E01ED9.6050607@linuxmail.org> (raw)
In-Reply-To: <42481.194.102.197.244.1088427899.squirrel@www.as.ro>
Alex Sirbu wrote:
> For blocking pourposes why don't you use blackholes ?
> I have a webserver that is permanently under DoS attacks , so I use blackholes.
>
> Routing table can have million of rules or static routes, so is not a problem .
>
> Let's say you want to block ip 11.22.33.44 . just type :
>
> #ip route add blackhole 11.22.33.44/32
>
> and all packets to 11.22.33.44 will be discarded.
All packets to 11.22.33.44 is discarded...but will 11.22.33.44 be able
to generate a connection socket?
>
> if you type than :
> #ip ro | grep blackhole
> you will see all blackholes defined by you
How maintainable is such a list compared to iptables which has
iptables-save and iptables-restore?
>
> you can blackhole your incomming traffic, but be carefull what you are doing .
>
Is there something I am missing here?
next prev parent reply other threads:[~2004-06-28 13:36 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-24 14:57 over a 1,000,000,000 individual ips to block Timothy Webster
2004-06-28 12:45 ` Michael Gale
2004-06-28 13:04 ` Alex Sirbu
2004-06-28 13:36 ` Feizhou [this message]
2004-06-28 13:52 ` Alex Sirbu
2004-06-28 14:14 ` Feizhou
2004-06-28 13:20 ` Feizhou
2004-06-28 16:31 ` Michael Gale
-- strict thread matches above, loose matches on Subject: below --
2004-06-29 11:04 Timothy Webster
2004-06-29 11:43 ` Feizhou
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=40E01ED9.6050607@linuxmail.org \
--to=feizhou@linuxmail.org \
--cc=alex@as.ro \
--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