From owner-freebsd-isp Wed Apr 29 15:39:23 1998 Return-Path: Received: (from majordom@localhost) by hub.freebsd.org (8.8.8/8.8.8) id PAA22556 for freebsd-isp-outgoing; Wed, 29 Apr 1998 15:39:23 -0700 (PDT) (envelope-from owner-freebsd-isp@FreeBSD.ORG) Received: from panda.hilink.com.au (panda.hilink.com.au [203.8.15.25]) by hub.freebsd.org (8.8.8/8.8.8) with ESMTP id PAA22489 for ; Wed, 29 Apr 1998 15:39:11 -0700 (PDT) (envelope-from danny@panda.hilink.com.au) Received: (from danny@localhost) by panda.hilink.com.au (8.8.5/8.8.5) id IAA02557; Thu, 30 Apr 1998 08:38:38 +1000 (EST) Date: Thu, 30 Apr 1998 08:38:38 +1000 (EST) From: "Daniel O'Callaghan" To: Karl Pielorz cc: isp@FreeBSD.ORG Subject: Re: IPFW - Diverts, logging and capture... In-Reply-To: <35473AE9.C42190F2@tdx.co.uk> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: owner-freebsd-isp@FreeBSD.ORG Precedence: bulk X-Loop: FreeBSD.org > actually 'capture' the rogue packets? - Or divert them onto another box > /port which 'accepts' the connection - and logs all the data / packets it > receives? > > I guess at lot of this might be solved with ipfw's divert capabilities? Just write a divert program which receives packets and writes them where you want them to go. I can probably dig out a sample divert program. Danny To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message