From mboxrd@z Thu Jan 1 00:00:00 1970 From: Martijn Lievaart Subject: Re: blocking all connections Date: Fri, 06 Apr 2007 23:15:35 +0200 Message-ID: <4616B877.90204@rtij.nl> References: <20070406091639.ganfslae8ks4wcsk@webmail.harrisonburg.k12.va.us> <4616719E.8050306@rtij.nl> <20070406154336.feq9mge2o4wocg8w@mail.harrisonburg.k12.va.us> Mime-Version: 1.0 Content-Transfer-Encoding: 7bit Return-path: In-Reply-To: <20070406154336.feq9mge2o4wocg8w@mail.harrisonburg.k12.va.us> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: netfilter-bounces@lists.netfilter.org Errors-To: netfilter-bounces@lists.netfilter.org Content-Type: text/plain; charset="us-ascii"; format="flowed" To: dhottinger@harrisonburg.k12.va.us Cc: netfilter@lists.netfilter.org dhottinger@harrisonburg.k12.va.us wrote: > Quoting Martijn Lievaart : > >> dhottinger@harrisonburg.k12.va.us wrote: >>> What is the best rule for blocking all connections to an ip >>> address. For example, lets say I want to block all connections to >>> the domain google.com. >> >> The domain google.com is not an ip address. If you want to block all >> web access to google, use a transparent cache. Otherwise I see no way >> to do this (reliably). >> >> M4 > > Google.com was just an example. Lets say I want to block all > connections to and from 194.67.57.26. > -I INPUT -j BLOCK -I FORWARD -j BLOCK -I OUTPUT -j BLOCK -N BLOCK -A BLOCK -s 194.67.57.26 -j DROP -A BLOCK -d 194.67.57.26 -j DROP HTH, M4