Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!mnetor!seismo!lll-crg!nike!ucbcad!ucbvax!TOPAZ.RUTGERS.EDU!hedrick
From: hedrick@TOPAZ.RUTGERS.EDU (Charles Hedrick)
Newsgroups: mod.protocols.tcp-ip
Subject: Re:  network monitors
Message-ID: <8610290632.AA05428@topaz.rutgers.edu>
Date: Wed, 29-Oct-86 01:32:20 EST
Article-I.D.: topaz.8610290632.AA05428
Posted: Wed Oct 29 01:32:20 1986
Date-Received: Tue, 4-Nov-86 05:01:00 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Organization: The ARPA Internet
Lines: 9
Approved: tcp-ip@sri-nic.arpa

We find the most generally useful network monitor to be a Sun.
Traffic is good for general watching, and etherfind for looking at
individual packets.  For many purposes an IBM PC with the MIT
public-domain netwatch is quite useful.  It just shows you packets,
with some limited ability to select based on source, dest, etc.  We
understand that the HP Ethernet monitor will be really great when the
next software release comes out, but for the moment it's useful only
when you really want to look at the bits (and want to make sure you
aren't dropping any packets in a high-speed network).