From owner-freebsd-ipfw@FreeBSD.ORG Mon Apr 12 17:47:12 2010 Return-Path: Delivered-To: freebsd-ipfw@freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:4f8:fff6::34]) by hub.freebsd.org (Postfix) with ESMTP id 91C7F1065676 for ; Mon, 12 Apr 2010 17:47:12 +0000 (UTC) (envelope-from fjwcash@gmail.com) Received: from mail-pv0-f182.google.com (mail-pv0-f182.google.com [74.125.83.182]) by mx1.freebsd.org (Postfix) with ESMTP id 63ED38FC12 for ; Mon, 12 Apr 2010 17:47:12 +0000 (UTC) Received: by pvc7 with SMTP id 7so3667661pvc.13 for ; Mon, 12 Apr 2010 10:47:11 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:received:message-id:subject:from:to:content-type; bh=JIupp9a/O5nxmiT8/x7kx0eROy1eChlMtBxo7boGHWI=; b=kYZ1XNBulsPnhGyUy0rOzKc9aLiiPVUaqMIMx5Z2m0kpUfFbZz/ymwl0pA2fDGq/0p OO5SzLcPIAQC/QjmB6v8YvsmDBbJqnK5WGBen/wmekfvINJd6uMsJRBEMz1bwXk16pqN 3PCnhZSkJ+gAcpI+DOZl4Ai15YI+/nHsGF6OM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=SLgGCjagNpbQgwBwhC5oHQXMwSTp7RblfGZ+lM4OGg7X3q5ssYBPbKkNMZYHE/mbMI 2pGfxyGwPhSfxO2XUZ65sUAEcO4zIxRZ1jALpdLTIvCsSq85nh/2+pH4CRnRsgQpFs0u O9Q/Y2F2PCIrhFNs16POhXz4cLc+d4sG5wrow= MIME-Version: 1.0 Received: by 10.231.14.76 with HTTP; Mon, 12 Apr 2010 10:47:11 -0700 (PDT) In-Reply-To: <1819469327.513811271001448449.JavaMail.root@mail-01.cse.ucsc.edu> References: <954074760.513761271001257209.JavaMail.root@mail-01.cse.ucsc.edu> <1819469327.513811271001448449.JavaMail.root@mail-01.cse.ucsc.edu> Date: Mon, 12 Apr 2010 10:47:11 -0700 Received: by 10.141.101.19 with SMTP id d19mr3788370rvm.154.1271094431143; Mon, 12 Apr 2010 10:47:11 -0700 (PDT) Message-ID: From: Freddie Cash To: freebsd-ipfw@freebsd.org Content-Type: text/plain; charset=UTF-8 X-Content-Filtered-By: Mailman/MimeDel 2.1.5 Subject: Re: Problems with ipfw in FreeBSD 8.0 / amd64 X-BeenThere: freebsd-ipfw@freebsd.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: IPFW Technical Discussions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Mon, 12 Apr 2010 17:47:12 -0000 On Sun, Apr 11, 2010 at 8:57 AM, Tim Gustafson wrote: > After a build/update to RELENG_8, I'm getting this as the last rule from > "ipfw list" > > 00000 ip from any to any > > And then I get these through syslog: > > ipfw: ouch!, skip past end of rules, denying packet > > The box then becomes unavailable over TCP. > > I know that there is some development work going on to clean up ipfw; > that's fine. My question is does anyone know if this is a problem in > RELENG_8_0_0_RELEASE as well? Should I change my csup tag to > RELENG_8_0_0_RELEASE and then do another build/install cycle to fix the > problem, or will the problem still be there? > > Also, I know this a volunteer effort so I have no right to be pushy, but is > there any ETR on this so that I can start tracking RELENG_8 again? > Use RELENG_8_0. That's the security branch for 8.0-RELEASE. -- Freddie Cash fjwcash@gmail.com