From owner-freebsd-ipfw Mon Aug 28 16:19:28 2000 Delivered-To: freebsd-ipfw@freebsd.org Received: from jade.chc-chimes.com (jade.chc-chimes.com [216.28.46.6]) by hub.freebsd.org (Postfix) with ESMTP id 574CC37B443 for ; Mon, 28 Aug 2000 16:19:27 -0700 (PDT) Received: by jade.chc-chimes.com (Postfix, from userid 1001) id D08ED1C41; Mon, 28 Aug 2000 19:19:26 -0400 (EDT) Date: Mon, 28 Aug 2000 19:19:26 -0400 From: Bill Fumerola To: Scott Blachowicz Cc: Daryl Chance , FreeBSD IPFW Subject: Re: ipfw add exec(blah).... Message-ID: <20000828191926.O33771@jade.chc-chimes.com> References: <005f01c01104$b382a980$0200000a@development1> <200008282313.QAA43037@ns1.rresearch.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Mailer: Mutt 1.0i In-Reply-To: <200008282313.QAA43037@ns1.rresearch.com>; from scott@sabmail.rresearch.com on Mon, Aug 28, 2000 at 04:13:44PM -0700 X-Operating-System: FreeBSD 3.3-STABLE i386 Sender: owner-freebsd-ipfw@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.ORG On Mon, Aug 28, 2000 at 04:13:44PM -0700, Scott Blachowicz wrote: > Well...ipfw can log to syslog and syslogd can run a command on receipt > of messages - check 'man syslog.conf' for details. I'd guess that > since the capability is already there in that form, it shouldn't be > necessary to stick it in ipfw "itself". Yes. Matt Ayres and I discussed this today and we pretty much both agreed that this would be the work of an external daemon monitoring the packet count or looking for specific syslog type things. The logisitics of trying to make ipfw run a program isn't something I'd like to think about either. -- Bill Fumerola - Network Architect, BOFH / Chimes, Inc. billf@chimesnet.com / billf@FreeBSD.org To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-ipfw" in the body of the message