From owner-freebsd-questions Tue Jul 3 7:27:25 2001 Delivered-To: freebsd-questions@freebsd.org Received: from mail.metrocon.com (metrocon.com [198.143.64.100]) by hub.freebsd.org (Postfix) with ESMTP id D5F0E37B401 for ; Tue, 3 Jul 2001 07:27:21 -0700 (PDT) (envelope-from tzink@metrocon.com) Received: from coldstone.metrocon.com (access.metrocon.com [198.143.64.40]) by mail.metrocon.com (8.9.3/8.9.3) with SMTP id KAA01282; Tue, 3 Jul 2001 10:27:16 -0400 (EDT) (envelope-from tzink@metrocon.com) Content-Type: text/plain; charset="iso-8859-1" From: Terry Zink Organization: Metrocon Communications To: Jason Nugent Subject: Re: More on the NFS issue Date: Tue, 3 Jul 2001 10:27:18 -0400 X-Mailer: KMail [version 1.2] References: In-Reply-To: Cc: freebsd-questions@freebsd.org MIME-Version: 1.0 Message-Id: <01070310271807.22407@coldstone.metrocon.com> Content-Transfer-Encoding: 8bit Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG type kldstat Basically, the rc.conf loads a kernel module I believe. Thats all that firewall_enable entry does to my KNOWLEDGE. (ive never checked it though). On Tuesday 03 July 2001 09:31, you wrote: > Hi, folks, > > Yeap, I'm still fiddling with this. I've discovered even more interesting > things. > > If you recall, I was having difficulty getting my NFS partitions to mount > correctly after upgrading to the latest 4.3-STABLE. My latest experiment > was to see if IPFW was causing problems, so I performed the following > steps: > > 1. I re-cvsup'ped the latest 4.3-stable source, and created a new kernel > config file called TEST that was essentially a direct copy of GENERIC. > The only thing I changed was the IDENT and the MAXUSERS. > > 2. I did a new make buildworld and make buildkernel using my test kernel. > I then performed a make installkernel with this new kernel. I did -not- > perform a make installworld. > > 3. I rebooted the machine from my terminal server and watched, with a > certain amount of glee, as it booted up with no errors. I shelled in, and > made sure all my partitions were mounted. I was happy. > > 4. I found something quite interesting at that point. You see, I had > left my old firewall rules in /etc/rc.firewall. I had also left my > firewall_enable="yes" and firewall_type="client" config options in > /etc/rc.conf. What surprised me, therefore, was that all my rules were > loaded and active, and working (I tested my rules from various other > machines, and used ipfw to add and remove them). > > But, I thought I had removed all IPFW support from my test kernel? It was > a copy of GENERIC? > > So, my question is, why would my rules still be working? I realize > that I had left things turned on in my config file, but I was expecting > those options to cause errors since IPFW was turned off in my test kernel. > > Regards, > > Jason > > ---------------------- > Jason Nugent > Aka MalHavoc > Server Programmer and Administrator > > S T O M P E D . C O M > > For PGP public key: http://malhavoc.stomped.com > > > To Unsubscribe: send mail to majordomo@FreeBSD.org > with "unsubscribe freebsd-questions" in the body of the message -- Regards, Terry Zink System Administrator Metrocon Communications Phone: (212) 661-6800 x 1553 To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message