Date: Tue, 15 Oct 2002 13:32:39 -0500 From: "Jack L. Stone" <jackstone@sage-one.net> To: budsz <budsz@kumprang.or.id> Cc: FreeBSD-Questions <freebsd-questions@FreeBSD.ORG> Subject: Re: About rc.firewall Message-ID: <3.0.5.32.20021015133239.0136e5e8@mail.sage-one.net> In-Reply-To: <20021015173223.GA2352@kumprang.or.id> References: <3.0.5.32.20021015103018.0136e5e8@mail.sage-one.net> <200210151023430685.13684C4D@home.24cl.com> <20021015135723.GA1427@kumprang.or.id> <200210151023430685.13684C4D@home.24cl.com> <3.0.5.32.20021015103018.0136e5e8@mail.sage-one.net>
next in thread | previous in thread | raw e-mail | index | archive | help
At 12:32 AM 10.16.2002 +0700, budsz wrote: >On Tue, Oct 15, 2002 at 10:30:18AM -0500, Jack L. Stone wrote: >>Designating the type "open" will make your system set up wide open and can >>be useful when debugging the rc.firewall script and the kernel has been >>compiled to "deny all". If you want to the rc.firewall to load and bee >>effective though, you must modify it for your own use, incuding the proper >>designations of interfaces, ports, and rules. > >Sorry, I mean is: >What is the relation between firewall_type in /etc/rc.conf and the same >statement; firewall_type in rc.firewall? Is it enough if i only define >the firewall_type just once; In rc.firewall only? > >-- >budsz > No, you just need to set "type" in rc.conf. If you look closely at rc.firewall, it reads your rc.conf file to check the settings. Leave the type alone in rc.firewall. Hope this clarifies.... Best regards, Jack L. Stone, Administrator SageOne Net http://www.sage-one.net jackstone@sage-one.net To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?3.0.5.32.20021015133239.0136e5e8>