All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stig Thormodsrud <stig@vyatta.com>
To: netfilter@vger.kernel.org, roman@tsisyk.com
Subject: Re: NetFlow / sFlow / IPFIX network probe proposal
Date: Tue, 30 Mar 2010 12:06:32 -0700	[thread overview]
Message-ID: <4BB24BB8.7000808@vyatta.com> (raw)
In-Reply-To: <22578828.43001269973644747.JavaMail.root@tahiti.vyatta.com>

> What is wrong in ipt_NETFLOW module
> (http://sourceforge.net/projects/ipt-netflow/) ?
> Ipt_NETFLOW is a really useful module and it never load CPU more than
> 1%. But internal architecture of ipt_NETFLOW cannot support all of
> described above features (because have one common hash table and
> configuration with module params). I'd prefer not to reinvent the
> wheel and think about redesigning ipt_NETFLOW or writing new module
> using ipt_NETFLOW base.
> 
> I'm a student and want to work on this project within Summer of Code
> program. The Linux Foundation site pointed to the mail list.
> My main goal is to make high-quality featured module, that will be
> useful for anybody and acceptable for inclusion into mainstream
> Kernel.
> 
> What do you think about this? Please, advice me or give some ideas.
> May be somebody wanted to be a mentor? I'll send detailed information
> about my bio, contacts, skills, work experience as well as schedule
> plan directly to a potential mentor and/or GSoC site.
> 
> BTW, a NetFlow exporter feature is a most rated request on the Vyatta
> site, so it should be interesting not only for me.

Hi Roman,

You mentioned that netflow exporter is the most requested feature on
Vyatta.  That was true until today when VC6 was release with our 1st
netflow/sflow exporter.  I used pmacct (http://www.pmacct.net) and ULOG
to get the packets to uacctd.  There's certainly a lot more that can be
done to support higher bandwidth interfaces.  I'm considering PF_RING.
At any rate I'd be glad to work with you if you want to improve our
netflow support.  The pmacct developer is also very helpful in answering
 pmacct questions and getting patches integrated into pmacct.

For an example of how to use netflow in vyatta VC6 see:
http://www.vyatta.org/forum/viewtopic.php?p=27038#27038

stig



       reply	other threads:[~2010-03-30 19:06 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <22578828.43001269973644747.JavaMail.root@tahiti.vyatta.com>
2010-03-30 19:06 ` Stig Thormodsrud [this message]
2010-03-30 14:06 NetFlow / sFlow / IPFIX network probe proposal Roman Tsisyk
2010-03-30 14:29 ` Changli Gao
2010-03-30 14:29   ` Changli Gao
2010-03-30 14:56 ` Jan Engelhardt
2010-03-30 15:57   ` Roman Tsisyk
2010-03-30 16:07     ` Jan Engelhardt
2010-03-30 16:39   ` Patrick McHardy
2010-03-31 13:47     ` Roman Tsisyk
2010-04-01 10:22       ` Patrick McHardy
2010-04-01 12:05         ` Holger Eitzenberger
2010-04-01 14:29           ` Pablo Neira Ayuso
2010-04-01 14:33             ` Patrick McHardy
2010-04-01 14:46               ` Holger Eitzenberger
2010-04-01 14:55                 ` Patrick McHardy
2010-04-01 16:56                   ` Jan Engelhardt
2010-04-01 14:55                 ` Patrick McHardy
2010-04-08 14:55 ` Florian Weimer
2010-04-08 14:55   ` Florian Weimer

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4BB24BB8.7000808@vyatta.com \
    --to=stig@vyatta.com \
    --cc=netfilter@vger.kernel.org \
    --cc=roman@tsisyk.com \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.