From owner-freebsd-stable Mon Oct 5 09:16:18 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id JAA02150 for freebsd-stable-outgoing; Mon, 5 Oct 1998 09:16:18 -0700 (PDT) (envelope-from owner-freebsd-stable@FreeBSD.ORG) Received: from pn.wagsky.com (wagsky.vip.best.com [206.86.71.127]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id JAA02133 for ; Mon, 5 Oct 1998 09:16:14 -0700 (PDT) (envelope-from Jeff@Wagsky.com) Received: from [192.168.6.3] (mac.pn.wagsky.com [192.168.6.3]) by pn.wagsky.com (8.8.8/8.8.8) with ESMTP id JAA09588 for ; Mon, 5 Oct 1998 09:15:50 -0700 (PDT) (envelope-from Jeff@Wagsky.com) X-Sender: mailman@mail.pn.wagsky.com Message-Id: Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Date: Mon, 5 Oct 1998 09:15:45 -0700 To: freebsd-stable@FreeBSD.ORG From: Jeff Kletsky Subject: ipfw SkipTo behavior changed Sender: owner-freebsd-stable@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG In trying to resolve puzzling behavior on a "new" FreeBSD box (2.2.7-STABLE, cvsup as of 980929), it appears that the behavior of the SkipTo rules in ipfw/kernel have changed. Previously a rule such as 2200 skipto 3000 all from 127.0.0.1 to 127.0.0.1 recv lo0 in would "skipto" the next-higher numbered rule in the list if 3000 did not exist. This build seems to require that a rule 3000 explicitly exist. If it does not exist, it proceeds as if rule 2200 is not matched. Is this an "intentional" change in the firewall code? If not, has a later release changed back to the older behavior? Jeff To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-stable" in the body of the message