From owner-freebsd-stable Mon Feb 26 04:29:22 1996 Return-Path: owner-stable Received: (from root@localhost) by freefall.freebsd.org (8.7.3/8.7.3) id EAA15985 for stable-outgoing; Mon, 26 Feb 1996 04:29:22 -0800 (PST) Received: from asstdc.scgt.oz.au (root@asstdc.scgt.oz.au [202.14.234.65]) by freefall.freebsd.org (8.7.3/8.7.3) with SMTP id EAA15963 Mon, 26 Feb 1996 04:29:02 -0800 (PST) Received: (from imb@localhost) by asstdc.scgt.oz.au (8.6.12/BSD4.4) id XAA07877; Mon, 26 Feb 1996 23:28:57 +1100 From: michael butler Message-Id: <199602261228.XAA07877@asstdc.scgt.oz.au> Subject: -stable hangs at boot (fwd) To: stable@freebsd.org Date: Mon, 26 Feb 1996 23:28:56 +1100 (EST) Cc: current@freebsd.org X-Mailer: ELM [version 2.4 PL24beta] MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Sender: owner-stable@freebsd.org Precedence: bulk I wrote: > Having backed out the troublesome /usr/lib/libc/db/hash/hash.c change, I > still have the problem of a recently built -stable kernel stopping during > start-up immediately after "ifconfig ed0 .." but before "ifconfig lo0 .." > If I wait long enough, it seems that it will eventually continue but cannot > transmit packets at all on the ed0 interface. This is as a direct consequence of compiling IPFW into the kernel .. it can't receive packets from its own ethernet interface ! If you ^C your way to a shell prompt, there's a single rule that's in the firewall list saying "deny all from any to any". Courtesy of the same recent brain-damage in ipfw(8), you can't delete this rule either ("setsockopt failed"). I suspect the very same problem in -current. The only workaround I can think of is to add "ipfw addf accept .." statements _prior_ to the running of ifconfig in netstart .. theory as yet untested .. michael