OSEC

Neohapsis is currently accepting applications for employment. For more information, please visit our website www.neohapsis.com or email hr@neohapsis.com
 
Re: ipf stopped working on 5.3

From: John Fitzgerald (jjfitzgeraldgmail.com)
Date: Wed Oct 26 2005 - 07:56:52 CDT


It doesn't work on boot or after ipf -D; ipf -E -f /etc/ipf.rules. My
rc.conf specifies the rules file so it's the same thing and I don't have any
other scripts that could be interfering with it (that I know of).

The only thing they installed that might have affected it (?) is "cronolog".
I've never used it before and it just appears to be a log parser. Other than
that, it's just a web box so I have openssl, mod_ssl, mod_perl, mason, php,
mysql, and apache installed with nothing else to speak of. I don't like a
lot of miscellany on my servers so it's hard to say that it might be a
conflict with something that was put on there.

-JJ

On 10/26/05, Christopher H. Laco <clacochrislaco.com> wrote:
>
> John Fitzgerald wrote:
> > Yeah, options INET6 is already in there (by default). It's curious that
> it
> > would stop working on one of my servers, yet remain functional on the
> other.
> >
> > -JJ
> >
>
> I missed most of this thread, so I'm sure this has been covered.
>
> Does it just not work after boot, but works after issuing ipf -Fav -f
> /etc/ipf.rules?
>
> I spent a couple of days trying to figure out why my ipf rules were
> loading on boot...and the it turned out to be the fact that I put bash
> in my roots .cshrc file...it was short cirtuiting the startup scripts
> for ipf...
>
> -=Chris
>
>
>
_______________________________________________
freebsd-securityfreebsd.org mailing list
http://lists.freebsd.org/mailman/listinfo/freebsd-security
To unsubscribe, send any mail to "freebsd-security-unsubscribefreebsd.org"