Re: issue configuring flowscan

Date view Thread view Subject view Author view

Subject: Re: issue configuring flowscan
From: Alex Rubenstein (alex@nac.net)
Date: Fri Jul 26 2002 - 13:44:46 CDT

Has anyone yet come up with a way to collect flow information without
using the netflow feature of a router? Perhaps, a unix box, that sits on
the side running promiscuously?



On Fri, 26 Jul 2002, Matt Selsky wrote:

> > I've had this problem before too. The author of the ConfigReader module
> > is not maintaining it any longer and the copy that is on CPAN has become
> > corrupted. I am not using the built in FlowScan reports any longer, so I
> > don't have a copy of ConfigReader that I could send you. Perhaps someone
> > else on the list will. You could also look at CUFlow at:
> >
> > http://www.columbia.edu/acis/networks/advanced/CUFlow/
> >
> > This report module does not need the ConfigReader module.
>
> flowscan itself still requires ConfigReader, though.  Would there be
> objections to using a home brew config parser, like CUFlow does or
> perhaps switching to ConfigReader-Simple which seems to be still
> supported (last release was 14th July 2002)?
>
> --
> Help        mailto:majordomo@net.doit.wisc.edu and say "help" in message body
> Unsubscribe mailto:majordomo@net.doit.wisc.edu and say
> "unsubscribe flowscan" in message body
> Archive     http://net.doit.wisc.edu/~plonka/list/flowscan/archive/
>

-- Alex Rubenstein, AR97, K2AHR, alex@nac.net, latency, Al Reuben --
--    Net Access Corporation, 800-NET-ME-36, http://www.nac.net   --



--
Help        mailto:majordomo@net.doit.wisc.edu and say "help" in message body
Unsubscribe mailto:majordomo@net.doit.wisc.edu and say
"unsubscribe flowscan" in message body
Archive     http://net.doit.wisc.edu/~plonka/list/flowscan/archive/

Date view Thread view Subject view Author view

This archive was generated by hypermail 2b25 : Fri Jul 26 2002 - 13:45:34 CDT