From: "Pablo Sanchez" <pablo@blueoakdb.com>
To: netfilter@lists.netfilter.org
Subject: RE: Someone is using too much bandwidth???
Date: Tue, 21 Nov 2006 13:13:12 -0500 [thread overview]
Message-ID: <003f01c70d98$b4f1bd00$0419a8c0@fly> (raw)
In-Reply-To: <380-2200611221172226406@zamnet.zm>
> -----Original Message-----
> From: netfilter-bounces@lists.netfilter.org
> [mailto:netfilter-bounces@lists.netfilter.org] On Behalf Of lubasi
> Sent: Tuesday, November 21, 2006 12:22 PM
> To: netfilter@lists.netfilter.org
> Subject: RE: Someone is using too much bandwidth???
>
> Hello,
>
> Indeed its true, and i dont know what machine it is.
You could setup an iptables rule to log all traffic or do what I believe may
be simpler: use tcpdump
Let's say you have two NIC's on your machine:
// Internet // - [eth0] - [gateway] - [eth1] - // Internal Network
//
You can run tcpdump on your Internet Network:
tcpdump -i eth1
If you've ssh'd to your gateway machine from your Internal Network, your
host and ssh information will also be spewed. Probably not what you want.
A simple tweak will handle it:
tcpdump -i eth1 not host your.IP.address.here
The above should give you some quick answers.
Cheers,
---
Pablo Sanchez - Blueoak Database Engineering, Inc
Ph: 819.459.1926 Toll free: 888.459.1926
Cell: 819.918.9731 Pgr: pablo_p@blueoakdb.com
Fax: 603.720.7723 (US)
next prev parent reply other threads:[~2006-11-21 18:13 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-11-21 17:22 Someone is using too much bandwidth??? lubasi
2006-11-21 18:13 ` Pablo Sanchez [this message]
2006-11-21 18:25 ` Taylor, Grant
2006-11-21 18:28 ` tom
2006-11-22 5:48 ` Danny
2006-11-25 18:54 ` R. DuFresne
-- strict thread matches above, loose matches on Subject: below --
2006-11-22 5:57 lubasi
2006-11-22 15:15 ` Taylor, Grant
2006-11-22 14:44 lubasi
2006-11-22 15:08 ` Gavin White
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='003f01c70d98$b4f1bd00$0419a8c0@fly' \
--to=pablo@blueoakdb.com \
--cc=netfilter@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox