The portion of your note I copied below is easily answered. A switch port
will not see traffic bound for machines on ports other than itself unless
that port has been configured as a "mirroring" port. If the port is set to
mirror traffic, it can potentially see 100Mbit/s of traffic. This means if
there are two other ports both sitting at high utilization, you will most
likely see only a portion of the traffic from each port. The only way to
monitor all traffic from a specific workstation that is connected to a
switch is to use a (rather expensive) inline analyzer between the machine
and the switch port.
I cannot answer why tcpdump does not see the pings being transmitted across
the hub. It should. The pings are successful, correct?
-----Original Message-----
From: Robert Tagliarini [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 12, 2000 6:47 AM
To: [EMAIL PROTECTED]
Subject: tcpdump and 10/100 NICs
A neighbor in the next cube with similar hardware (both our hubs go to the
same 3Com switch) running network ASSOCIATES Sniffer on an NT 4 workstation
also fails to see these pings.
-
To unsubscribe from this list: send the line "unsubscribe linux-net" in
the body of a message to [EMAIL PROTECTED]
