[netflow-tools] Flowd-0.9 Python Library Problem

Jesse Kempf jkempf at davisvision.com
Tue Sep 18 07:35:43 EST 2007

On Mon, 17 Sep 2007 10:34:16 -0400
Jesse Kempf <jkempf at davisvision.com> wrote:

> > I agree that a making a lightweight NetFlow parser library out of  
> > flowd's
> > guts would be a good thing though :)
> I find myself wondering whether it would be better from a system  
> building perspective to build this thing as a backend for flowd by  
> way of the Unix domain socket export, or actually break down and make  
> a libnetflow and then create a python wrapper around it.

Having given this more than three or four seconds of thought now, the insanity of this suggestion is obvious to me.

I'm looking at extracting the individual netflow parsers from flowd.c, but it seems like each of the process_netflow_v?() functions are tightly bound to flowd's tracking of the sanity of the sending agents.

It shouldn't be too unreasonable to generalize this with a struct of function pointers for handlers for each of the error conditions checked for in process_netflow_v?(). Then the caller could have his functions handled however he may please, as in the incrementing of peer->ninvalid in flowd.c, or throwing exceptions in the case of a Python library.

-Jesse Kempf

The information contained in this communication is intended
only for the use of the recipient(s) named above. It may
contain information that is privileged or confidential, and
may be protected by State and/or Federal Regulations. If
the reader of this message is not the intended recipient,
you are hereby notified that any dissemination,
distribution, or copying of this communication, or any of
its contents, is strictly prohibited. If you have received
this communication in error, please return it to the sender
immediately and delete the original message and any copy
of it from your computer system. If you have any questions
concerning this message, please contact the sender.

More information about the netflow-tools mailing list