From owner-freebsd-questions Wed Jul 11 16:36:49 2001 Delivered-To: freebsd-questions@freebsd.org Received: from wombat.bytecraft.au.com (wombat.bytecraft.au.com [203.39.118.3]) by hub.freebsd.org (Postfix) with ESMTP id 338AB37B406 for ; Wed, 11 Jul 2001 16:36:43 -0700 (PDT) (envelope-from taylorm@bytecraft.au.com) Received: from pc99101401.bytecraft.au.com (unknown [203.39.118.42]) by wombat.bytecraft.au.com (Postfix) with SMTP id 9D3F23E9F; Thu, 12 Jul 2001 09:36:41 +1000 (EST) Message-ID: <007901c10a62$9f68c1c0$2a7627cb@pc99101401.bytecraft.au.com> Reply-To: "Murray Taylor" From: "Murray Taylor" To: "Tony Wells" , "Murray Taylor" Cc: Subject: Re: ipfw and #comments Date: Thu, 12 Jul 2001 09:38:43 +1000 X-Priority: 3 X-MSMail-Priority: Normal X-Mailer: Microsoft Outlook Express 4.72.3110.5 X-MimeOLE: Produced By Microsoft MimeOLE V4.72.3110.3 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 This I know ... and if I wish to use these lines in rc.conf firewall_enable="YES" firewall_type="/etc/rulesfile" and leave rc.firewall as distributed then I need to have a file of just valid commands and rules. In this case it would be nice if the rules file could cope with comments in a simple form # must be first non-blank char on line # comment continues up to and including newline all else must be rules and commands as at present. Murray Taylor Project Manager Bytecraft Systems Pty Ltd ph: +61 3 9587 2555 Fax: +61 3 9587 1614 Email: taylorm@bytecraftsystems.com -----Original Message----- From: Tony Wells To: Murray Taylor Cc: questions@FreeBSD.ORG Date: Thursday, 12 July 2001 00:10 Subject: Re: ipfw and #comments > >If you look at the example /etc/rc.firewall file, it's actually a shell >script. You can put comments in a script that performs the ipfw >commands. If you make your firewall commands permanent by adding the >pertinent lines to /etc/rc.conf, it will expect the file to be a shell >script anyway. > >Once again, look at /etc/rc.firewall for guidance. > >Murray Taylor wrote: >> >> Has anyone looked into allowing # comments in the >> rules file that can be fed into ipfw ?? >> >> It would be great if one could intersperse the >> rule and command lines with comments in the file >> given to ipfw via >> >> ipfw /etc/rulefile >> >> I cant yet as I an up to my whatzit in alligators as we >> relocate the business, but its an idea.... >> >> Murray Taylor >> Project Manager >> Bytecraft Systems Pty Ltd >> ph: +61 3 9587 2555 >> Fax: +61 3 9587 1614 >> Email: taylorm@bytecraftsystems.com >> >> To Unsubscribe: send mail to majordomo@FreeBSD.org >> with "unsubscribe freebsd-questions" in the body of the message > To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message