From: Mart Frauenlob <mart.frauenlob@chello.at>
To: netfilter@vger.kernel.org
Cc: e2ia.ci@gmail.com
Subject: Re: iptable how many rule can manage iptable
Date: Wed, 12 May 2010 22:47:03 +0200 [thread overview]
Message-ID: <4BEB13C7.2040600@chello.at> (raw)
In-Reply-To: <20100512200954.3f53f3f6@catlap>
>> i'd like to know how many rule can manage iptable.
>> I'm asking that because i'd to drop all traffric from my localnet to
>> porn site. I've a database of porn site witch contain about 900 000
>> domains. I know there are solutions like squidguard. But for my linux
>> box i'd to use iptable to prevent users access to porn site and other
>> blacklist site.
>
> It's not feasible to implement 900 000 long ruleset in iptables
> even with ipset extension or with fancy hierarchical chains. The
> other problem is that iptables works on ip addresses and your database
> is comprised of domains. There can be more then one site on single ip
> address. Blocking IPs and not domains could cut access to some legit
> sites.
>
> Squid+squidguard is good option. I've heard of some dns based
> solutions (domain blacklisting on dnscache level), but I don't know any
> actual software.
i.e.
http://www.peereboom.us/adsuck/
adsuck is a small dns server that spoofs blacklisted addresses and
forwards all other queries. The idea is to be able to prevent
connections to undesirable sites such as ad servers, crawlers, etc. It
can be used locally, for the road warrior, or on the network perimeter
in order to protect local machines from malicious sites.
prev parent reply other threads:[~2010-05-12 20:47 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-05-12 17:09 iptable how many rule can manage iptable Mamadou Touré
2010-05-12 17:39 ` Jan Engelhardt
2010-05-12 18:05 ` Mamadou Touré
2010-05-12 19:23 ` Jan Engelhardt
[not found] ` <AANLkTil4jAxQ-JvggsqWtLmAaasn9gb-CAsY-Pim1dXF@mail.gmail.com>
2010-05-12 20:19 ` Fwd: " Mistick Levi
2010-05-12 18:09 ` Marek Kierdelewicz
2010-05-12 20:47 ` Mart Frauenlob [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=4BEB13C7.2040600@chello.at \
--to=mart.frauenlob@chello.at \
--cc=e2ia.ci@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).