From owner-freebsd-current@FreeBSD.ORG  Sat Feb 28 15:59:54 2004
Return-Path: <owner-freebsd-current@FreeBSD.ORG>
Delivered-To: freebsd-current@freebsd.org
Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125])
	by hub.freebsd.org (Postfix) with ESMTP
	id 5230B16A4CE; Sat, 28 Feb 2004 15:59:54 -0800 (PST)
Received: from orinoco.swatweb.co.uk
	(82-35-132-132.cable.ubr02.enfi.blueyonder.co.uk [82.35.132.132])
	by mx1.FreeBSD.org (Postfix) with ESMTP
	id B206F43D1D; Sat, 28 Feb 2004 15:59:53 -0800 (PST)
	(envelope-from simon@swat.me.uk)
Received: from tomsk.home (tomsk.home [192.168.1.2])
	by orinoco.swatweb.co.uk (Postfix) with ESMTP
	id 09A3C399FF; Sat, 28 Feb 2004 23:59:52 +0000 (GMT)
From: Simon Watson <simon@swat.me.uk>
To: Vincent Poy <vince@oahu.WURLDLINK.NET>
In-Reply-To: <20040228131212.G8264-100000@oahu.WURLDLINK.NET>
References: <20040228131212.G8264-100000@oahu.WURLDLINK.NET>
Content-Type: text/plain
Message-Id: <1078012800.30996.1.camel@tomsk.home>
Mime-Version: 1.0
X-Mailer: Ximian Evolution 1.5.4 
Date: Sun, 29 Feb 2004 00:00:00 +0000
Content-Transfer-Encoding: 7bit
cc: alc@freebsd.org
cc: Robert Watson <rwatson@freebsd.org>
cc: current@freebsd.org
cc: Kris Kennaway <kris@obsecurity.org>
Subject: Re: HEADSUP: Sleep queues added to kernel, so be careful.
X-BeenThere: freebsd-current@freebsd.org
X-Mailman-Version: 2.1.1
Precedence: list
List-Id: Discussions about the use of FreeBSD-current
	<freebsd-current.freebsd.org>
List-Unsubscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=unsubscribe>
List-Archive: <http://lists.freebsd.org/pipermail/freebsd-current>
List-Post: <mailto:freebsd-current@freebsd.org>
List-Help: <mailto:freebsd-current-request@freebsd.org?subject=help>
List-Subscribe: <http://lists.freebsd.org/mailman/listinfo/freebsd-current>,
	<mailto:freebsd-current-request@freebsd.org?subject=subscribe>
X-List-Received-Date: Sat, 28 Feb 2004 23:59:54 -0000

> firewall_enable="NO"           # Set to YES to enable firewall functionality
> 
> in /etc/rc.conf, it would disable ipfw from being loaded.  open is what I
> am using since that seems to add a rule 100, 200, 300 as well as a 65000
> and the 65535 but if one had natd_enable in /etc/rc.conf, it adds a rule
> 50 that diverts to natd from any to any which is the one that seems to be
> the problem.
> 

I'm not 100% on this, but I just upgraded to -current from 5.2.1, and
have experienced similar problems. All I did though to resolve it was
run /etc/rc.d/ipfw restart - and it all started working again.

Simon