From owner-freebsd-current Fri Dec 25 08:38:13 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id IAA17224 for freebsd-current-outgoing; Fri, 25 Dec 1998 08:38:13 -0800 (PST) (envelope-from owner-freebsd-current@FreeBSD.ORG) Received: from tim.xenologics.com (tim.xenologics.com [194.77.5.24]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id IAA17219 for ; Fri, 25 Dec 1998 08:38:11 -0800 (PST) (envelope-from seggers@semyam.dinoco.de) Received: (from uucp@localhost) by tim.xenologics.com (8.8.5/8.8.8) with UUCP id RAA12040; Fri, 25 Dec 1998 17:36:23 +0100 (MET) Received: from semyam.dinoco.de (semyam.dinoco.de [127.0.0.1]) by semyam.dinoco.de (8.9.1/8.8.8) with ESMTP id RAA12096; Fri, 25 Dec 1998 17:25:06 +0100 (CET) (envelope-from seggers@semyam.dinoco.de) Message-Id: <199812251625.RAA12096@semyam.dinoco.de> To: "Erik Funkenbusch" cc: freebsd-current@FreeBSD.ORG, seggers@semyam.dinoco.de Subject: Re: Broken ipfw? In-reply-to: Your message of "Mon, 21 Dec 1998 11:47:15 CST." <003901be2d0a$6da7f800$0200a8c0@mn.mediaone.net> Date: Fri, 25 Dec 1998 17:25:05 +0100 From: Stefan Eggers Sender: owner-freebsd-current@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG > After cvsuping on saturday natd has suddenly stopped working with the kernel > I built on saturday and after cvsuping today and rebuilding as well. > > After executing an ipfw rule it responds with: > > ip_fw_ctl: empty interface name > /sbin/ipfw: setsockopt(IP_FW_ADD): Invalid Argument Using a kernel module for ipfw? I used it preloaded by /boot/loader and with a world (and kernel, of course) from last weekend the kernel did see there was a preloaded ELF module but it never got integrated into the system - ipfw's initial message during startup was missing and I had a similar problem. The result was a kernel without working ipfw. See PR kern/9178. If anybody needs more details for this I can easily reproduce the problem. I still have a kernel w/o ipfw and could test it. > Any ideas? I'm planning on rebuilding world to see if it was some fix to > both kernel and natd, but I can't seem to find anything in the cvs list that Adding IPFW to the kernel instead of using a module is what I'd suggest to try. Stefan. -- Stefan Eggers Lu4 yao2 zhi1 ma3 li4, Max-Slevogt-Str. 1 ri4 jiu3 jian4 ren2 xin1. 51109 Koeln Federal Republic of Germany To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message