From owner-freebsd-questions@FreeBSD.ORG Thu Jun 17 20:41:28 2010 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id C2BAF1065675 for ; Thu, 17 Jun 2010 20:41:28 +0000 (UTC) (envelope-from cswiger@mac.com) Received: from asmtpout025.mac.com (asmtpout025.mac.com [17.148.16.100]) by mx1.freebsd.org (Postfix) with ESMTP id AA4478FC14 for ; Thu, 17 Jun 2010 20:41:28 +0000 (UTC) MIME-version: 1.0 Content-transfer-encoding: 7BIT Content-type: text/plain; charset=us-ascii Received: from cswiger1.apple.com ([17.209.4.71]) by asmtp025.mac.com (Sun Java(tm) System Messaging Server 6.3-8.01 (built Dec 16 2008; 32bit)) with ESMTPSA id <0L4600HASESJ7850@asmtp025.mac.com> for freebsd-questions@freebsd.org; Thu, 17 Jun 2010 13:41:08 -0700 (PDT) X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 spamscore=0 ipscore=0 phishscore=0 bulkscore=0 adultscore=0 classifier=spam adjust=0 reason=mlx engine=6.0.2-1004200000 definitions=main-1006170123 X-Proofpoint-Virus-Version: vendor=fsecure engine=1.12.8161:2.4.5,1.2.40,4.0.166 definitions=2010-06-17_03:2010-02-06, 2010-06-17, 2010-06-17 signatures=0 From: Chuck Swiger In-reply-to: <939113.8942.qm@web30705.mail.mud.yahoo.com> Date: Thu, 17 Jun 2010 13:41:07 -0700 Message-id: <761D9A06-7AB3-4A7D-BDE4-A5BBC8CBA4B9@mac.com> References: <939113.8942.qm@web30705.mail.mud.yahoo.com> To: Valerian Galeru X-Mailer: Apple Mail (2.1081) Cc: freebsd-questions@freebsd.org Subject: Re: FreeBSD router (IPFW-based): how to block an URL (all IPs of an A-like HOSTNAME) X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 17 Jun 2010 20:41:28 -0000 On Jun 17, 2010, at 1:01 PM, Valerian Galeru wrote: > Does anyone have any ideas how to block all requests using an IPFW-based router (FreeBSD 6.4) to and from a HOSTNAME (which has more DNS A entries) or better, from any *.HOSTNAME.COM ???? Start by blocking all traffic, add permit rules to only pass traffic which is allowed. :-) Judging by your question, however, it sounds more like you want to use regex based blocking of hostnames within a web proxy like Squid or Varnish than IP-level firewalls. Regards, -- -Chuck