All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kenneth Porter <shiva@sewingwitch.com>
To: netfilter-devel@lists.netfilter.org
Subject: Re: New target to control a fake network interface
Date: Wed, 22 Jun 2005 06:18:04 -0700	[thread overview]
Message-ID: <8C06C084907746238C329ABC@[10.0.0.14]> (raw)
In-Reply-To: <1119319953.4109.59.camel@envy>

--On Tuesday, June 21, 2005 2:12 AM +0000 Corey Giovanella 
<coreygiovanella@challenge-engineering.com> wrote:

> I've posted the source and perhaps a better description on my web site:
> http://challenge-engineering.com/~corey/projects/fake_if/

You're echoing iptables packet counts into a fake interface to make it 
available to an existing graphical monitor application. The app has a 
plugin system, so wouldn't it be better to write an iptables plugin for it? 
What's the advantage of copying the counters to another kernel object?

The fake interface is an interesting object but maybe not the best solution 
for this particular problem.

Given a general iptables plugin, this would make a good replacement for 
ntop as a packet-counting protocol analyzer. I find ntop (which uses 
libpcap) a bit "heavyweight" for just counting packets, as it also does 
deep analysis of their content and hence uses a fair amount of memory and 
CPU. (ntop also exposes the data via web interface, which is nice for 
non-Linux clients.)

  parent reply	other threads:[~2005-06-22 13:18 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2005-06-21  2:12 New target to control a fake network interface Corey Giovanella
2005-06-22 12:00 ` Harald Welte
2005-06-24  4:12   ` Corey Giovanella
2005-06-22 12:56 ` Jan Engelhardt
2005-06-22 13:18 ` Kenneth Porter [this message]
2005-06-24  4:12   ` Corey Giovanella
2005-06-24 16:13     ` Patrick Schaaf

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='8C06C084907746238C329ABC@[10.0.0.14]' \
    --to=shiva@sewingwitch.com \
    --cc=netfilter-devel@lists.netfilter.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.