All of lore.kernel.org
 help / color / mirror / Atom feed
From: Florian Weimer <fw@deneb.enyo.de>
To: linux-kernel@vger.kernel.org
Subject: Re: NetFlow export
Date: Thu, 13 Mar 2003 14:46:04 +0100	[thread overview]
Message-ID: <87llzj8jmr.fsf@deneb.enyo.de> (raw)
In-Reply-To: <20030313122932.GB29730@unthought.net> (Jakob Oestergaard's message of "Thu, 13 Mar 2003 13:29:33 +0100")

Jakob Oestergaard <jakob@unthought.net> writes:

> You asked for netflow data export. Netramet can give you something
> similar to netflow (I never used netflow, but from what I hear, netramet
> is similar only more flexible).

I need the NetFlow data format, not something else.

> With 10 lines of Perl you could do full ASN-1   ;)

NetFlow is not based on ASN.1.  It's a completely different format (an
industry standard which is implemented by quite a few vendors).

> Point being; if what you want is flow information from a Linux router,
> excellent user space software (both "meter" and retrieval/filtering
> tools) already exist for that.

I fear the performance impact of copying all packet headers to user
space.

> If you want something else, then I have completely misread your mails.
> Please elaborate, in that case  :)

I'd like to see something which has virtually no impact on forwarding,
so that it's a no-brainer to enable it.  I doubt copying all the
packet headers to user space falls into this category.

  reply	other threads:[~2003-03-13 13:35 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-03-13 11:07 NetFlow export Florian Weimer
2003-03-13 11:48 ` Jakob Oestergaard
2003-03-13 11:57   ` Florian Weimer
2003-03-13 12:29     ` Jakob Oestergaard
2003-03-13 13:46       ` Florian Weimer [this message]
2003-03-13 16:45         ` Jakob Oestergaard
2003-03-14  9:32         ` David Luyer

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=87llzj8jmr.fsf@deneb.enyo.de \
    --to=fw@deneb.enyo.de \
    --cc=linux-kernel@vger.kernel.org \
    /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.