finn.drablos@sintef.no (Finn Drablos) (03/25/91)
We have a local network with 8 workstations/large computers connected to
the cable, and we are also connected (via a bridge) to a larger network.
Now some of the traffic coming in over the bridge gives a VMS-based
computer problems during file transfer, and we want to find out where
the offending traffic stems from. So I am looking for a tool for looking
at the network traffic, something like tcpdump for sun (we don't have
any suns (!)). It don't need to be very sophisticated, we just want to
find out if we really need this traffic.
==================
Finn Drablos PHONE +47 7 997710 FAX +47 7 997708
MR-Senteret, UNIMED, SINTEF C=no;P=uninett;O=sintef;G=finn;S=drablos;
N-7034 TRONDHEIM, NORWAY MHS(EAN) : finn.drablos@sintef.no
EARN/BITNET : drabloes@norunit
----------------------------------------------------------------------srp@babar.mmwb.ucsf.edu (Scott R. Presnell) (03/26/91)
finn.drablos@sintef.no (Finn Drablos) writes: >the offending traffic stems from. So I am looking for a tool for looking >at the network traffic, something like tcpdump for sun (we don't have >any suns (!)). It don't need to be very sophisticated, we just want to >find out if we really need this traffic. I was able to port the more recent version of tcpdump, 2.0, to the IRIX snoop(7) network interface. Moreover, the developers of tcpdump have cleaned up the code some so that there are not the memory alignment problems that there were before. Tcpdump now recognizes several different packet semantices (sp?): this makes it a more useful tool than before. You can find tcpdump 2.0 with support for IRIX on babar.mmwb.ucsf.edu [128.218.21.42] in ~ftp/pub/tcpdump2.0.tar.Z Good Luck. - Scott Presnell (srp@cgl.ucsf.edu) -- Scott Presnell +1 (415) 476-9890 Pharm. Chem., S-926 Internet: srp@cgl.ucsf.edu University of California UUCP: ...ucbvax!ucsfcgl!srp San Francisco, CA. 94143-0446 Bitnet: srp@ucsfcgl.bitnet