Date: Tue, 13 Mar 2001 22:20:28 -0600 From: David Kelly <dkelly@hiwaay.net> To: Joel CARNAT <joel.carnat@noos.fr> Cc: freebsd-questions@FreeBSD.ORG Subject: Re: PING filtering Message-ID: <200103140420.f2E4KSe16527@grumpy.dyndns.org> In-Reply-To: Message from Joel CARNAT <joel.carnat@noos.fr> of "Tue, 13 Mar 2001 09:11:56 GMT." <20010313091156.042ce93e.joel.carnat@noos.fr>
next in thread | previous in thread | raw e-mail | index | archive | help
Joel CARNAT writes: > On Mon, 12 Mar 2001 22:10:42 -0600 > David Kelly <dkelly@hiwaay.net> wrote: > > > Joel CARNAT writes: > > [...] > > > -3- use syslog to watch who ping's me so that I may tune the rules later. .. > > > # IPFW logging :) > > > !ipfw > > > *.* /var/log/ipfw.log > > > > Good for you for knowing to divert syslogd's output into a file. But > > ipfw also happens to be written to /var/log/security, by default. :-) > > mouarf ... > newbie me :)) > that's good to know... You're doing better than a newbie. You knew syslogd was there and how to redirect its logging information. More than once I've felt like pulling my hair out when something (lately an Ascend Pipeline) is logging via syslogd and I'm trying to figure out how the data was tagged for priority. Such as the priority assigned to ipfw logs. Its not in ipfw or ipfirewall. But happens to be mentioned in syslog(3). Don't know why I thought to look there just now and search for ipfw. What I have learned is when looking for log information don't be afraid to grep /var/log/* as often that will find what you are looking for. -- David Kelly N4HHE, dkelly@hiwaay.net ===================================================================== The human mind ordinarily operates at only ten percent of its capacity -- the rest is overhead for the operating system. 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?200103140420.f2E4KSe16527>