From owner-freebsd-questions Thu Mar 28 12:41:44 2002 Delivered-To: freebsd-questions@freebsd.org Received: from mail.k12us.com (mail.k12us.com [65.112.222.15]) by hub.freebsd.org (Postfix) with SMTP id 5C94737B41F for ; Thu, 28 Mar 2002 12:41:35 -0800 (PST) Received: (qmail 87277 invoked by uid 1001); 28 Mar 2002 20:41:29 -0000 Date: Thu, 28 Mar 2002 15:41:29 -0500 From: Christopher Weimann To: chip.wiegand@simrad.com Cc: freebsd-questions@freebsd.org Subject: Re: OT - network sniffing - is this what I need? Message-ID: <20020328154129.A53810@mail.k12us.com> References: Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5i In-Reply-To: ; from chip.wiegand@simrad.com on Thu, Mar 28, 2002 at 08:50:56AM -0800 X-AntiVirus: scanned for viruses by AMaViS 0.2.1 (http://amavis.org/) Sender: owner-freebsd-questions@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.ORG On Thu, Mar 28, 2002 at 08:50:56AM -0800, chip.wiegand@simrad.com wrote: > > I have a situation at work where we think we may need to do some network > sniffing, packet > tracing, something to figure out if one particular workstation's problems > are caused by the > network connection, hub, switch, nic, whatever. > You can run a sniffer on the BSD boxes but if you are using switches rather than hubs on your network the BSD box won't be able ot hear anything. The easiest solution would be to run the sniffer on the client machine and you are in luck since ethereal is available for windows. http://www.ethereal.com/ Your other choice is to hook the machine in question and the BSD box up to a hub and connect that hub into your networks switch so the BSD box can hear the the traffic. To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-questions" in the body of the message