From owner-freebsd-net@FreeBSD.ORG Thu Aug 28 13:01:58 2003 Return-Path: Delivered-To: freebsd-net@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 76E3916A4BF for ; Thu, 28 Aug 2003 13:01:58 -0700 (PDT) Received: from silver.he.iki.fi (silver.he.iki.fi [193.64.42.241]) by mx1.FreeBSD.org (Postfix) with ESMTP id 15B8543FE0 for ; Thu, 28 Aug 2003 13:01:57 -0700 (PDT) (envelope-from pete@he.iki.fi) Received: from he.iki.fi (h81.vuokselantie10.fi [193.64.42.129]) by silver.he.iki.fi (8.12.9/8.11.4) with ESMTP id h7SK1s5L019710 for ; Thu, 28 Aug 2003 23:01:55 +0300 (EEST) (envelope-from pete@he.iki.fi) Message-ID: <3F4E5FAF.2080705@he.iki.fi> Date: Thu, 28 Aug 2003 23:01:51 +0300 From: Petri Helenius User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.4) Gecko/20030624 X-Accept-Language: en-us, en MIME-Version: 1.0 To: freebsd-net@freebsd.org Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Subject: ipfw parsing bug X-BeenThere: freebsd-net@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list List-Id: Networking and TCP/IP with FreeBSD List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Thu, 28 Aug 2003 20:01:58 -0000 ipfw seems to have developed a bug lately on 5-CURRENT; # ipfw add 2042 allow tcp from 0.0.0.0/0 to me 42 02042 allow tcp from me to me dst-port 42 It used to work that 0.0.0.0/0 was "any" instead of "me". Last I checked the notation is also widely used in networking gear for default route which is a "catch any" definition. Pete