From: lists+netfilter@roth.lu
To: howard chen <howachen@gmail.com>
Cc: netfilter@vger.kernel.org
Subject: Re: Handling large list of rules - Efficient or not?
Date: Sat, 17 May 2008 17:59:22 +0200 [thread overview]
Message-ID: <482F00DA.8010607@roth.lu> (raw)
In-Reply-To: <b66ddc900805170728h34511bb7r9be1324034745748@mail.gmail.com>
howard chen wrote:
> My server sometimes is under attack by DDOS, so I want to make a
> simple script which read the log (Apache access log), do the analysis,
> and set the rule to drop the packets from a specific IP.
>
> Since it is DDOS, so I assume there will be large ammount of unique IP
> needed to be input into the iptables.
>
> I want to know, are there any hidden efficiency problem in this setup?
> Or any better method?
>
>
> Howard.
> --
> To unsubscribe from this list: send the line "unsubscribe netfilter" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at http://vger.kernel.org/majordomo-info.html
>
Haven't we had this discussion several times in the very recent past?
See the archives.
Hint: if the list is really large use ipsets.
prev parent reply other threads:[~2008-05-17 15:59 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-05-17 14:28 Handling large list of rules - Efficient or not? howard chen
2008-05-17 15:59 ` lists+netfilter [this message]
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=482F00DA.8010607@roth.lu \
--to=lists+netfilter@roth.lu \
--cc=howachen@gmail.com \
--cc=netfilter@vger.kernel.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.