From owner-freebsd-questions Thu Dec 30 13:14:17 1999 Delivered-To: freebsd-questions@freebsd.org Received: from tetron02.tetronsoftware.com (ftp.tetronsoftware.com [208.236.46.106]) by hub.freebsd.org (Postfix) with ESMTP id BEFEB14D47 for ; Thu, 30 Dec 1999 13:14:11 -0800 (PST) (envelope-from zeus@tetronsoftware.com) Received: from tetron02.tetronsoftware.com (zeus@tetron02.tetronsoftware.com [208.236.46.106]) by tetron02.tetronsoftware.com (8.9.3/8.9.3) with ESMTP id PAA01916 for ; Thu, 30 Dec 1999 15:16:58 -0600 (CST) (envelope-from zeus@tetronsoftware.com) Date: Thu, 30 Dec 1999 15:16:58 -0600 (CST) From: Gene Harris To: freebsd-questions@freebsd.org Subject: Re: IPFW troubles on 3.4-R In-Reply-To: Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Thu, 30 Dec 1999 adric@mindspring.com wrote: > I'm having some trouble getting rc.firewall (et al) to play nice. > Here's the last few lines of dmesg: > Can you execute your firewall script from the command prompt? su to root and then try ./rc.firewall. It should execute just like it did before the upgrade. > changing root device to wd0s1a > IP packet filtering initialized, divert disabled, rule-based forwarding disabled, logging disabled > ip_fw_ctl: invalid command > What the heck is ip_fw_ctl? I use ipfw on my machine. Has your rc.firewall script become corrupted? You should be able to enter some manual commands from your firewall script to verify that your system is forwarding packets and filtering properly. If you enter "ipfw -F; ipfw add pass any from any via fxp0" or whatever your network card is, your network should open up and act ok. This would indicate you have a syntax error in your script. Gene Harris To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message