From owner-freebsd-current@freebsd.org Fri Aug 11 22:23:30 2017 Return-Path: Delivered-To: freebsd-current@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 85695DCB541 for ; Fri, 11 Aug 2017 22:23:30 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (108-84-10-9.lightspeed.austtx.sbcglobal.net [108.84.10.9]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client CN "darth.immure.com", Issuer "darth.immure.com" (not verified)) by mx1.freebsd.org (Postfix) with ESMTPS id 311C66746C; Fri, 11 Aug 2017 22:23:29 +0000 (UTC) (envelope-from bob@rancor.immure.com) Received: from rancor.immure.com (localhost [127.0.0.1]) by rancor.immure.com (8.15.2/8.15.2) with ESMTPS id v7BMNQAB021107 (version=TLSv1.2 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=NO); Fri, 11 Aug 2017 17:23:26 -0500 (CDT) (envelope-from bob@rancor.immure.com) Received: (from bob@localhost) by rancor.immure.com (8.15.2/8.15.2/Submit) id v7BMNQ8o021106; Fri, 11 Aug 2017 17:23:26 -0500 (CDT) (envelope-from bob) Date: Fri, 11 Aug 2017 17:23:26 -0500 From: Bob Willcox To: Ngie Cooper Cc: Mark Johnston , current list Subject: Re: ipfw kernel module not being built Message-ID: <20170811222326.GC20555@rancor.immure.com> Reply-To: Bob Willcox References: <20170811163639.GA19733@rancor.immure.com> <5B2835E9-4EE8-47FC-9A81-C4D60B4822F0@gmail.com> <20170811190602.GA20555@rancor.immure.com> <20170811192148.GA19972@wkstn-mjohnston.west.isilon.com> <20170811193453.GB20555@rancor.immure.com> <636F12A1-8A0E-4508-9015-EE4675A5FCEE@gmail.com> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <636F12A1-8A0E-4508-9015-EE4675A5FCEE@gmail.com> User-Agent: Mutt/1.8.3 (2017-05-23) X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: Discussions about the use of FreeBSD-current List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Fri, 11 Aug 2017 22:23:30 -0000 On Fri, Aug 11, 2017 at 03:14:39PM -0700, Ngie Cooper wrote: > > > On Aug 11, 2017, at 12:34, Bob Willcox wrote: > > > >> On Fri, Aug 11, 2017 at 12:21:49PM -0700, Mark Johnston wrote: > >> On Fri, Aug 11, 2017 at 02:06:02PM -0500, Bob Willcox wrote: > >>>>> On Aug 11, 2017, at 10:36, Bob Willcox wrote: > >>>>> > >>>>> When I rebuild my kernel on Jun 13th none of the previous ipfw kernel modules were built: > >>>>> > >>>>> ipfw.ko > >>>>> ipfw_nat.ko > >>>>> ipfw_nat64.ko > >>>>> ipfw_nptv6.ko > >>>>> ng_ipfw.ko > >>>>> > >>>>> and only this ipfw module was built: > >>>>> > >>>>> ng_ipfw.ko > >>>>> > >>>>> However, the verson of /etc/rc.d/ipfw that I'm running (from the > >>>>> freebsd-base-graphics branch) is failing to load ipfw so my firewall isn't > >>>>> starting. > >>>>> > >>>>> So, what am I missing? Is it possible that the freebsd-base-graphics branch > >>>>> that I'm running has an old or improper version of /etc/rc.d/ipfw? > >> > >> [...] > >> > >>> include GENERIC_DRM > >> > >> GENERIC_DRM sets MODULES_OVERRIDE, so only the specified modules are > >> built. In particular, ipfw*.ko does not get built. You'll need to either > >> remove the MODULES_OVERRIDE setting in GENERIC_DRM (which will make > >> kernel builds somewhat slower), or add > >> > >> makeoptions MODULES_OVERRIDE+= ipfw ... > >> > >> to your custom config. > > Or add "MODULES_OVERRIDE+= ipfw..." to your src.conf. > Cheers, > -Ngie Well, I added the 'makeoptions MODULES_OVERRIDE+= ipfw' to my kernel config and rebuilt my kernel and it did build ipfw.ko as expected. I haven't installed this new kernel yet since I am not at a good point here at work to do that right now...but will when I get a chance. Thanks all for the help. -- Bob Willcox | Lawsuit, n.: A machine which you go into as a pig and bob@immure.com | come out as a sausage. Austin, TX | -- Ambrose Bierce