From: Morten Nilsen <morten@nilsen.com>
To: lartc@vger.kernel.org
Subject: Re: [LARTC] Trafic monitor
Date: Thu, 17 Jun 2004 07:59:03 +0000 [thread overview]
Message-ID: <40D14F47.2070602@nilsen.com> (raw)
In-Reply-To: <001901c45376$cb7fe760$05d24d52@unixyv5xl6jssn>
[-- Attachment #1: Type: text/plain, Size: 1263 bytes --]
Thilo Schulz wrote:
> On Wednesday 16 June 2004 09:51, Ionut Gogu wrote:
>> I search for a tool show-me on real time the trafic made by all/one IPon
>> the interface eth1
>
> I'm working on one _RIGHT_NOW_ and expect it to be usable today.
> It will be configurable over a webinterface, and will manipulate the iptables
> using a small setuid C-Program I wrote. (I know, setuid root sucks, but
> you'll have to make sure noone else on this server can access or run the
> executable file using the webserver .. that's your job.)
> It uses ulogd and stores the traffic in a webinterface, it also does update
> the statistics database once a given limit of traffic has been reached, or a
> certain timeout has been hit. I might give out a usable version tomorrow, but
> I cannot guarantee for its bugfreeness. Though, most of the parts are done
> and they also seem to work the way I want them to.
> Plus, it won't destroy any already-present firewall setups.
I find that thing intriguing, but I have a couple questions;
- How will your solution scale? can it handle 200Mb traffic full duplex
on a Xeon 2.8GHz without choking? what about 100Mb on an AMD 800MHz?
- Could it affect latency?
- why not use sudo instead of setuid root?
Cheers,
--
Morten
[-- Attachment #2: S/MIME Cryptographic Signature --]
[-- Type: application/x-pkcs7-signature, Size: 3170 bytes --]
next prev parent reply other threads:[~2004-06-17 7:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-16 7:51 [LARTC] Trafic monitor Ionut Gogu
2004-06-16 11:06 ` Thilo Schulz
2004-06-17 7:59 ` Morten Nilsen [this message]
2004-06-17 10:18 ` Ed Wildgoose
2004-06-17 10:42 ` Ronny Aasen
2004-06-17 11:51 ` Thilo Schulz
2004-06-17 14:10 ` Thilo Schulz
2004-06-20 16:10 ` Thilo Schulz
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=40D14F47.2070602@nilsen.com \
--to=morten@nilsen.com \
--cc=lartc@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.