Armand Passelac wrote:
YES your problem is the *s* at the and of the firewall_enable line ;-)
I can NOT believe how stupid I am...
I'm really sorry about this ;)
Moreover, according to me, a chmod 600 /etc/ipfw.conf seems to be better ;-)
Yes, of course, I just set it to 644 for my testings...
Tha
[ On Fri, 19 Sep, 2003 at 11:52, Michael L. Hostbaek wrote: ]
> Antoine Jacoutot (ajacoutot) writes:
> >
> > firewall_enables="YES"
> > firewall_script="/etc/ipfw.conf"
> > firewall_logging="YES"
> >
>
> try:
>
> firewall_enable="YES"
> firewall_type="/etc/ipfw.conf"
>
> I don't know w
try:
firewall_enable="YES"
firewall_type="/etc/ipfw.conf"
I already tried that, but it does not work :(
Antoine
___
[EMAIL PROTECTED] mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-questions
To unsubscribe, send any mail to "[EMAIL PROT
Antoine Jacoutot (ajacoutot) writes:
>
> firewall_enables="YES"
> firewall_script="/etc/ipfw.conf"
> firewall_logging="YES"
>
try:
firewall_enable="YES"
firewall_type="/etc/ipfw.conf"
I don't know why, but that works for me.
/mich
--
Best Regards,
Michael L. Hostbaek
FreeB
Hi !
I have a stange problem today.
I just set up a brand new 5.1 box. I added in my rc.conf:
firewall_enables="YES"
firewall_script="/etc/ipfw.conf"
firewall_logging="YES"
IPFW is compiled in the kernel.
If I go: "sh /etc/ipfw.conf"; the rules get loaded with no problem, but
when I reboot the co
