From owner-freebsd-questions Tue Oct 27 04:01:42 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id EAA09654 for freebsd-questions-outgoing; Tue, 27 Oct 1998 04:01:42 -0800 (PST) (envelope-from owner-freebsd-questions@FreeBSD.ORG) Received: from rucus.ru.ac.za (rucus.ru.ac.za [146.231.29.2]) by hub.freebsd.org (8.8.8/8.8.8) with SMTP id EAA09600 for ; Tue, 27 Oct 1998 04:01:32 -0800 (PST) (envelope-from nbm@rucus.ru.ac.za) Received: (qmail 1773 invoked by uid 1003); 27 Oct 1998 12:00:45 -0000 Message-ID: <19981027140045.A867@rucus.ru.ac.za> Date: Tue, 27 Oct 1998 14:00:45 +0200 From: Neil Blakey-Milner To: Stephen A Derdau , freebsd-questions@FreeBSD.ORG Subject: Re: ip_fw_ctl: len=104 want 96 ? References: <3635A949.67D73FF7@ne.mediaone.net> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 0.93.2i In-Reply-To: <3635A949.67D73FF7@ne.mediaone.net>; from Stephen A Derdau on Tue, Oct 27, 1998 at 06:06:49AM -0500 Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Tue 1998-10-27 (06:06), Stephen A Derdau wrote: > I had natd running great for a few weeks. > not sure what happened. > > Now It doesn't want to work and when the system > boots I see > ip_fw_ctl: len=104 want 96 when the system is booted I have a friend with the exact same problem, started I assume by a kernel compile recently - I've told him to remake world too, since he didn't do that before, since I assumed it was some sort of inconsistency between world's ipfw and the ipfw calls in the kernel. Very recent 2.2.7-STABLE. Neil -- Neil Blakey-Milner nbm@rucus.ru.ac.za To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message