Date: Mon, 19 Feb 2001 13:54:49 -0800 From: "Crist J. Clark" <cjclark@reflexnet.net> To: Tony Wells <awells@journalstar.com> Cc: questions@FreeBSD.ORG Subject: Re: IPFirewall & syslogd Message-ID: <20010219135449.A70899@rfx-216-196-73-168.users.reflex> In-Reply-To: <3A914E07.DF2E62EF@journalstar.com>; from awells@journalstar.com on Mon, Feb 19, 2001 at 10:47:03AM -0600 References: <3A8D846F.8824EEB9@journalstar.com> <20010218001901.F62368@rfx-216-196-73-168.users.reflex> <3A914E07.DF2E62EF@journalstar.com>
next in thread | previous in thread | raw e-mail | index | archive | help
On Mon, Feb 19, 2001 at 10:47:03AM -0600, Tony Wells wrote: > I didn't add anything, I guess I assumed the default "security" line > would catch it. Since it's a kernel thing and not a process, I'm not > sure what I would put in syslogd to catch the messages. ipfw logs to security.info. If you have the default security entry in /etc/syslog.conf, security.* /var/log/security It should be logging them. Does the file /var/log/security exist? You can catch ipfw only by adding, !ipfw As the "program" name. -- Crist J. Clark cjclark@alum.mit.edu 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?20010219135449.A70899>