From owner-freebsd-isp  Fri Feb 16  0:29: 8 2001
Delivered-To: freebsd-isp@freebsd.org
Received: from spooky.eis.net.au (spooky.eis.net.au [203.12.171.2])
	by hub.freebsd.org (Postfix) with ESMTP id 7B8E837B67D
	for <freebsd-isp@freebsd.org>; Fri, 16 Feb 2001 00:29:03 -0800 (PST)
Received: (from ernie@localhost)
	by spooky.eis.net.au (8.11.2/8.9.3) id f1G8Sxd44438
	for freebsd-isp@freebsd.org; Fri, 16 Feb 2001 18:28:59 +1000 (EST)
	(envelope-from ernie)
From: Ernie Elu <ernie@spooky.eis.net.au>
Message-Id: <200102160828.f1G8Sxd44438@spooky.eis.net.au>
Subject: flow-tools port
To: freebsd-isp@freebsd.org
Date: Fri, 16 Feb 2001 18:28:58 +1000 (EST)
X-Mailer: ELM [version 2.4ME+ PL40 (25)]
MIME-Version: 1.0
Content-Type: text/plain; charset=US-ASCII
Content-Transfer-Encoding: 7bit
Sender: owner-freebsd-isp@FreeBSD.ORG
Precedence: bulk
X-Loop: FreeBSD.org

Has anyone used the flow-tools port to capture Netflow data from a Cisco
router?

I can get flow-capture to do anything, it just quits out.

I tried the example:

flow-capture -z6 -E1G -c2 -w/var/flowdata

after making sure I created the /var/flowdata dir but still nothing.

The program flow-receive seems to work, but I presume flow-capture is the
heart of the thing.

Any clues?

- Ernie.


To Unsubscribe: send mail to majordomo@FreeBSD.org
with "unsubscribe freebsd-isp" in the body of the message