On 9/6/07, Marc G. Fournier <[EMAIL PROTECTED]> wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Today, I got hit by an attack, but haven't been able to easily determine whom
> was being attacked ...
>
> I run ipaudit to monitor bandwidth usage, so I have 'source / destination'
> info
On Thu, Sep 06, 2007 at 03:48:37PM -0300, Marc G. Fournier wrote:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Today, I got hit by an attack, but haven't been able to easily determine whom
> was being attacked ...
>
> I run ipaudit to monitor bandwidth usage, so I have 'source / dest
On Thursday 06 September 2007 14:59:36 Olivier Brisson wrote:
> * Marc G. Fournier <[EMAIL PROTECTED]> [070906 21:28]:
> > Is there either a command line command, or ports tool, that I can use
> > similar to top, or systat -iostat, that will help identify the IP that is
> > being attacked?
>
> In s
On Thu, Sep 06, 2007 at 03:48:37PM -0300, Marc G. Fournier wrote:
>
> Is there either a command line command, or ports tool, that I can use similar
> to top, or systat -iostat, that will help identify the IP that is being
> attacked?
>
I've found net-mgmt/iftop to be very usefull in the past.
* Marc G. Fournier <[EMAIL PROTECTED]> [070906 21:28]:
>
> Is there either a command line command, or ports tool, that I can use similar
> to top, or systat -iostat, that will help identify the IP that is being
> attacked?
In some way, you could also use wireshark:
http://www.wireshark.org/
Ol
On Sep 6, 2007, at 1:48 PMSep 6, 2007, Marc G. Fournier wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Today, I got hit by an attack, but haven't been able to easily
determine whom
was being attacked ...
I run ipaudit to monitor bandwidth usage, so I have 'source /
destination'
inf
