From: thegeezer <thegeezer@thegeezer.net>
To: gentoo-user@lists.gentoo.org
Subject: Re: [gentoo-user] Something firewall-ish
Date: Tue, 16 Dec 2014 10:53:30 +0000 [thread overview]
Message-ID: <54900F2A.1090802@thegeezer.net> (raw)
In-Reply-To: <548F4711.3030603@gmail.com>
On 15/12/14 20:39, Alan McKinnon wrote:
> On 15/12/2014 18:47, meino.cramer@gmx.de wrote:
>> Hi,
>>
>> this question is not related to a fully fledged,
>> big local area network with DMZs and such.
>>
>> Even the word "firewall" seems to be a little too
>> "huge and mighty" in this context to me.
>>
>> "The network" consists of a PC, which is connected
>> to a FritzBox (cable, no Wifi/WLAN), which connects
>> to the ISP (internet) and (same adress range) to a
>> embedded system (eth1)
>>
>> There are two additional embedded systems, both on
>> a separate interface (eth over usb: usb0 & usb1).
>>
>> I want to block (DROP or REJECT) the access to certain
>> sites (the "noise" which is produced mostly by sites,
>> which all exclusively "only want my best": ads, trackers, analysts
>> and so on...)
>>
>> I tried different tools: fwbuilder, which locks up either itsself
>> or my rulesset...I had to reboot and Shorewall, which definitely
>> is a great tool....a little too great tool and much more capable
>> as I am... ;)
>>
>> I am sure that the problems are mostly not the problems of the
>> tools but mine.
>>
>> Is there any simple straight forward tool to just block accesses
>> to certain sites?
>
>
> to do it network-wide: squid
+1
and not in transparent mode either -- if you have a proxy server set
then https traffic is filtered by domain name as it is part of the proxy
connection request.
squid + squidGuard / dansguardian is the way forward.
for examle, in my "advertisers/tracking" database there are some 12
thousand domains listed. good luck adding those individually to iptables.
the only other way to do things super paranoidly is by whitelisting
i.e. on the router just keep adding ip and port to whitelist table for
those you _want_
iptables -N whitelist
iptables -A whitelist -d 8.8.8.8 -m udp --dport 53 -j ACCEPT
iptables -A FORWARD -i LAN -o WAN -j whitelist
iptables -A FORWARD -J REJECT
this takes longer to "start" but is easier to maintain, as facebook for
example are constantly buying ip ranges and adding them to their global
domination, so you start by thinking you have blocked all 100 facebook
ip addresses and then a month or two later discover they have another
200 you need to block
>
> to do it on a per-pc per-browser basis: there's a large variety of
> firefox plugins to chose from that will block this and allow that. It
> seems to me this is the better approach as you want to stop your browser
> chatting with sites who only have your best interest at heart :-)
>
>
> Either way, the list of black and white lists gets very big very quick,
> so chose your tool carefully. Try a bunch and pick one that makes sense
> to you, bonus points if it comes with a community-supported blacklist
> you can drop in, maintained by people whose POV matches your own.
>
> You don't want a classic firewall for this; firewalls are mostly built
> to block based on address and port, this is not how you solve your problem
>
next prev parent reply other threads:[~2014-12-16 10:53 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-15 16:47 [gentoo-user] Something firewall-ish meino.cramer
2014-12-15 17:20 ` Emanuele Rusconi
2014-12-15 18:14 ` meino.cramer
2014-12-16 5:09 ` Walter Dnes
2014-12-15 20:39 ` Alan McKinnon
2014-12-16 4:02 ` meino.cramer
2014-12-16 4:24 ` [gentoo-user] " »Q«
2014-12-16 4:46 ` meino.cramer
2014-12-16 5:03 ` »Q«
2014-12-16 6:51 ` J. Roeleveld
2014-12-16 7:07 ` [gentoo-user] " Alan McKinnon
2014-12-16 10:53 ` thegeezer [this message]
2014-12-16 14:31 ` Pandu Poluan
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=54900F2A.1090802@thegeezer.net \
--to=thegeezer@thegeezer.net \
--cc=gentoo-user@lists.gentoo.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