All of lore.kernel.org
 help / color / mirror / Atom feed
From: Alistair Tonner <Alistair@nerdnet.ca>
To: Vincent Haverlant <vincent@haverlant.org>, Mark Webb <webb@mmspl.com.au>
Cc: netfilter@lists.netfilter.org
Subject: Re: Monitoring problems...
Date: Fri, 31 Oct 2003 07:37:20 -0500	[thread overview]
Message-ID: <200310310737.20925.Alistair@nerdnet.ca> (raw)
In-Reply-To: <m21xst1zh0.fsf@feanor.haverlant.org>

On October 31, 2003 05:19 am, Vincent Haverlant wrote:
> "Mark Webb" <webb@mmspl.com.au> writes:
> > I was asked by the powers that be to set up some monitoring of our
>
> workplaces internet traffic. Basically a breakdown of the volume used
> and what protocol is using it.  i.e. 20% mail, 30% web, 10% ftp, etc....
>
> Hi Mark,
>
> You might want to have a look at ntop (http://www.ntop.org/) which looks
> like it does exactly what you want.
>
> Vincent.

	Mark:
	Essentially what is happening is that although you are on a hub and can 
technically see all the traffic for the pipe you are attached to, the box 
does not see all that traffic as being destined for your box, thus is 
ignoring packets NOT a) addressed to the box itself b) addressed to 
broadcast.

  Don't know about ntop myself, but it seems to have a number of fans on this 
list (Hey ...look theres one now... its Vincent)

	*shrugs* ... there are those that swear by other tools too... and difficult 
as ethereal is ... with careful configuration and a few good scripts... 
	

-- 

	Alistair Tonner
	nerdnet.ca
	Senior Systems Analyst - RSS
	
     Any sufficiently advanced technology will have the appearance of magic.
	Lets get magical!


  reply	other threads:[~2003-10-31 12:37 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-10-29 22:52 Monitoring problems Mark Webb
2003-10-31 10:19 ` Vincent Haverlant
2003-10-31 12:37   ` Alistair Tonner [this message]
2003-10-31 10:27 ` Chris Brenton

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=200310310737.20925.Alistair@nerdnet.ca \
    --to=alistair@nerdnet.ca \
    --cc=netfilter@lists.netfilter.org \
    --cc=vincent@haverlant.org \
    --cc=webb@mmspl.com.au \
    /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.