From: Ahsan Ali <ahsanali@gmail.com>
To: linux-admin@vger.kernel.org
Subject: Re: looking at the network traffic
Date: Sat, 26 Jun 2004 11:24:30 +0500 [thread overview]
Message-ID: <17daa8560406252324490e0da4@mail.gmail.com> (raw)
In-Reply-To: <1088177229.4306.7.camel@chris.livedata.com>
You can use managed switches to mirror traffic from a port to a
monitoring port on managed switches.
You can also use utilities such as macof or angst
[http://freshmeat.net/projects/angst/] (not tested by me myself) to
flood the switch databases and make switches forward traffic out on
all ports so you can capture network traffic.
On 25 Jun 2004 11:27:09 -0400, Chris DiTrani <chris@livedata.com> wrote:
>
> On Fri, 2004-06-25 at 10:52, Luca Ferrari wrote:
> > Hi,
> > using program such as ethereal, tcpdump, etc. is it possible to see the
> > network traffic also if the hosts are connected thru a switch? I mean, if
> > A,B,C, are on the same network, connected with a switch, can A see the
> > traffic among B and C? I suppose no, since the switch should route the
> > traffic to the right host directly (while an hub should not), and the only
> > thing I can see should be message broadcasts and something similar. Is it
> > right? Is there a way to observe the traffic over a network even if there are
> > switches?
> > I don't want to break user's privacy, but since I'm developing a program
> > which should connect to a peer-to-peer client, and I don't have protocol
> > specifications, I was wondering about a traffic dump of a session among two
> > users. Nevertheless I was unable due to (I suppose) the switch.
>
> You are correct, but if you have a managed switch it can likely be set
> up with a port seeing all/selected port traffic ('port' in this context
> being a physical port on the switch).
>
> CD
prev parent reply other threads:[~2004-06-26 6:24 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-06-25 14:52 looking at the network traffic Luca Ferrari
2004-06-25 15:27 ` Chris DiTrani
2004-06-26 6:24 ` Ahsan Ali [this message]
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=17daa8560406252324490e0da4@mail.gmail.com \
--to=ahsanali@gmail.com \
--cc=linux-admin@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).