From owner-freebsd-isp Sun Feb 18 3:35:24 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 7405B37B401 for ; Sun, 18 Feb 2001 03:35:20 -0800 (PST) Received: (from ernie@localhost) by spooky.eis.net.au (8.11.2/8.9.3) id f1IBZ3Z03490; Sun, 18 Feb 2001 21:35:03 +1000 (EST) (envelope-from ernie) From: Ernie Elu Message-Id: <200102181135.f1IBZ3Z03490@spooky.eis.net.au> Subject: Re: flow-tools port In-Reply-To: from Domas Mituzas at "Feb 16, 1 12:21:07 pm" To: domas.mituzas@delfi.lt (Domas Mituzas) Date: Sun, 18 Feb 2001 21:35:03 +1000 (EST) Cc: freebsd-isp@freebsd.org 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 > > flow-capture -z6 -E1G -c2 -w/var/flowdata > flow-capture -z9 -c2 -e48 -n23 -p15442 -w /opt/flowdata > > and it works fine. check if your process is running, also, syslog > entries. As you can see in my working example, I specified the port, to > which cisco is sending me it's messages (make sure, to which does yours > and specify also, it may help). > > > The program flow-receive seems to work, but I presume flow-capture is the > > heart of the thing. > > Both are working for me, both should work for you. > I tried the above but still no luck. I checked the syslogs and there was a message that might give a clue: flow-capture[23385]: setsockopt(SO_RCVBUF=246725): No buffer space available Any ideas? - Ernie. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-isp" in the body of the message