Date: Sat, 07 Feb 2015 10:44:22 +0000 From: Arthur Chance <freebsd@qeng-ho.org> To: "Dan Mahoney, System Admin" <danm@prime.gushi.org>, questions@freebsd.org Subject: Re: IPFW script that supports some kind of rc.d directory? Message-ID: <54D5EC86.6050806@qeng-ho.org> In-Reply-To: <alpine.BSF.2.00.1502070159120.13139@prime.gushi.org> References: <alpine.BSF.2.00.1502070159120.13139@prime.gushi.org>
next in thread | previous in thread | raw e-mail | index | archive | help
On 07/02/2015 10:02, Dan Mahoney, System Admin wrote: > Hey all, > > This seems like the kind of thing that people have needed often enough > -- for example when you want to have specific ipfw rules for specific > installed services, and your ipfw config to be multiple files loaded in > some kind of order, but my google-fu is failing me. > > Failing that, I know FreeBSD has some rcorder, which might be usable for > this, but I don't know if it's extensible to a whole separate class of > things (or if trying to do that is overkill). > > Is this a problem someone else has had/solved before? > I've no idea if someone has already done this, but the final form of ipfw in the manual is ipfw [-cfnNqS] [-p preproc [preproc-flags]] pathname Using cpp as the preprocessor (or maybe m4 if you're a quote loving masochist :-) would let you use #include or the equivalent. That's not quite up what you're asking, but a start. m4 with syscmd and (s)include would go further. I think the major problem would be if different sets of rules had to be interleaved. That would require a careful choice of rule numbering. -- Those who do not learn from computing history are doomed to GOTO 1
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?54D5EC86.6050806>