Date: Tue, 22 Dec 1998 18:33:01 +0100 From: Mark Huizer <freebsd@xaa.iae.nl> To: Erik Funkenbusch <erikf@visi.com>, freebsd-current@FreeBSD.ORG Subject: Re: Broken ipfw? Message-ID: <19981222183301.A72204@esmeralda.xaa.iae.nl> In-Reply-To: <003901be2d0a$6da7f800$0200a8c0@mn.mediaone.net>; from Erik Funkenbusch on Mon, Dec 21, 1998 at 11:47:15AM -0600 References: <003901be2d0a$6da7f800$0200a8c0@mn.mediaone.net>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Dec 21, 1998 at 11:47:15AM -0600, Erik Funkenbusch wrote: > 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 > > and of course no routing occurs. > > 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 > would indicate a change here. > > I'm using the de0 driver on an Asante NIC. I can ping anything on that > network, and I can ping stuff on my private network using the xl0 driver. dummynet got included, rebuild your ipfw (after redoing the include files). Easiest is a make world :-) Mark To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-current" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?19981222183301.A72204>