From owner-freebsd-questions@FreeBSD.ORG Thu Dec 23 22:33:13 2004 Return-Path: Delivered-To: freebsd-questions@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 9670D16A4CE for ; Thu, 23 Dec 2004 22:33:13 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 3A4B043D48 for ; Thu, 23 Dec 2004 22:33:13 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from [192.168.1.3] (pool-68-160-208-232.ny325.east.verizon.net [68.160.208.232]) by pi.codefab.com (8.12.11/8.12.11) with ESMTP id iBNMX65k006944 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Thu, 23 Dec 2004 17:33:08 -0500 (EST) Message-ID: <41CB4798.4090708@mac.com> Date: Thu, 23 Dec 2004 17:32:56 -0500 From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.3) Gecko/20040910 X-Accept-Language: en-us, en MIME-Version: 1.0 To: "Marc G. Fournier" References: <20041223125410.X1788@ganymede.hub.org> In-Reply-To: <20041223125410.X1788@ganymede.hub.org> X-Enigmail-Version: 0.89.5.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Spam-Status: No, score=1.8 required=5.5 tests=RCVD_IN_NJABL_DUL, RCVD_IN_SORBS_DUL autolearn=disabled version=3.0.1 X-Spam-Level: * X-Spam-Checker-Version: SpamAssassin 3.0.1 (2004-10-22) on pi.codefab.com cc: freebsd-questions@freebsd.org Subject: Re: Effective ipfw rules for blocking MSN Messenger ... ? X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 23 Dec 2004 22:33:13 -0000 Marc G. Fournier wrote: > I just setup a FreeBSD box for a router, so that I could make use of > ipfw to block MSN Messenger traffic ... but I'm having a bugger of a > time finding a "definitive" list of what needs to be blocked :( > > MSN Messenger appears to be smart enough to go *around* the usual port > 1863 and onto port 80 if it needs to ... Apparently the best way to accomplish this goal is to block all traffic to and from the MSN boxes, rather than trying to filter by port #. I thought I had a list of those IPs handy, but I can't find it... -- -Chuck