The way that I do this is I have an ipchains ruleset running on my
workstation. If I want to see everything that is going on that is not
normal traffic I turn on logging for rejected/denied packets. It fills
the syslog very quick, but also contains much good info about the
offending machine.
JDF
Matt Herbert wrote:
>
> Hey everybody,
>
> Let me apologize in advance, this isn't directly linux related, but
> I thought I could draw on the deep pool of talented sys admins that
> frequent the list.
>
> Anyway, our lab network has become extremley bogged down, and we
> can't seem to figure out what is causing the problem. I suspect it
> is a machine hiding somewhere that has gone haywire and is barfing
> packets all over the place. Can anybody suggest a good sniffer to
> analyze the traffic flying around?
>
> -Matt
>
> **********************************************************
> To unsubscribe from this list, send mail to
> [EMAIL PROTECTED] with the following text in the
> *body* (*not* the subject line) of the letter:
> unsubscribe gnhlug
> **********************************************************
**********************************************************
To unsubscribe from this list, send mail to
[EMAIL PROTECTED] with the following text in the
*body* (*not* the subject line) of the letter:
unsubscribe gnhlug
**********************************************************
