From owner-freebsd-scsi Mon Aug 12 11:31: 7 2002 Delivered-To: freebsd-scsi@freebsd.org Received: from mx1.FreeBSD.org (mx1.FreeBSD.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E505937B400 for ; Mon, 12 Aug 2002 11:31:04 -0700 (PDT) Received: from goliath.siemens.de (goliath.siemens.de [192.35.17.28]) by mx1.FreeBSD.org (Postfix) with ESMTP id 7399343E6E for ; Mon, 12 Aug 2002 11:31:03 -0700 (PDT) (envelope-from andre.albsmeier@mchp.siemens.de) Received: from mail1.siemens.de (mail1.siemens.de [139.23.33.14]) by goliath.siemens.de (8.11.6/8.11.6) with ESMTP id g7CIV2517716; Mon, 12 Aug 2002 20:31:02 +0200 (MEST) Received: from curry.mchp.siemens.de (curry.mchp.siemens.de [139.25.42.7]) by mail1.siemens.de (8.11.6/8.11.6) with ESMTP id g7CIV1o12587; Mon, 12 Aug 2002 20:31:01 +0200 (MEST) Received: (from localhost) by curry.mchp.siemens.de (8.12.5/8.12.5) id g7CIV1t7063241; Date: Mon, 12 Aug 2002 20:31:00 +0200 From: Andre Albsmeier To: "Kenneth D. Merry" Cc: Andre Albsmeier , freebsd-scsi@FreeBSD.ORG Subject: Re: Using FreeBSD to monitor SCSI traffic Message-ID: <20020812203100.A1450@curry.mchp.siemens.de> References: <20020812125306.A46653@curry.mchp.siemens.de> <20020812100418.A43928@panzer.kdm.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline User-Agent: Mutt/1.2.5.1i In-Reply-To: <20020812100418.A43928@panzer.kdm.org>; from ken@kdm.org on Mon, Aug 12, 2002 at 10:04:18AM -0600 X-Echelon: BND CIA NSA Mossad KGB MI6 IRA detonator nuclear assault strike Sender: owner-freebsd-scsi@FreeBSD.ORG Precedence: bulk List-ID: List-Archive: (Web Archive) List-Help: (List Instructions) List-Subscribe: List-Unsubscribe: X-Loop: FreeBSD.org On Mon, 12-Aug-2002 at 10:04:18 -0600, Kenneth D. Merry wrote: > On Mon, Aug 12, 2002 at 12:53:06 +0200, Andre Albsmeier wrote: > > I have a win32 program to update the firmware on a specific SCSI > > device. I assume, it uses the "Write Buffer 0x3B" command but I > > don't know the exact parameters. I want to include this device > > in my SCSI firmware update tool which runs under FreeBSD and > > already supports some devices. > > > > Maybe one of the SCSI specialists (Justin, Ken, ...) has an idea > > if the following scenario could work: > > > > I use a standard winblows box with an 29160 Controller to update > > the device in question. To the SCSI same cable I attach another > > machine running FreeBSD. Is it possible to make the FreeBSD box > > watch and report the traffic on the SCSI bus? Will there be > > any problems since I now have two initiators attached to the > > same bus? I assume, I have to use CAM_DEBUG in my kernel to > > see anything at all... > > I don't think you can really put a SCSI device in "promiscuous" mode, to > use the networking term. Generally you've got one initiator and one target > for communication over the bus. > > What you really want is a bus analyzer, but they're pretty expensive. Yes, unfortunately. > (Although you might be able to find a previous generation bus analyzer, say > an Ultra or Ultra2 analyzer, for not too much money.) Well, I didn't want to put any money into that. As I said, I just wanted to teach my firmware upgrade tool how to download the fw to another brand of CDROM drives. I can still use the supplied DOS tool. I even found a DLL that replaces the normal winaspi.dll and logs stuff to some file. But the vendor only supports a DOS tool for downloading the fw so I am lost here. (Yes, I wrote that I have a WIN32 tool but I was wrong :-(). > > You could also do it with something like a passthrough disk emulator. > Basically, you run a target mode device on the SCSI bus in question, and > pass all SCSI requests out to the disk you're trying to update on another > SCSI bus. When they go through the FreeBSD system, you can log whatever > you want. > > I believe Nate Lawson is working on the target mode code, > you might want to contact him and see if his code might be a starting point > for something like this. (If you want to write code for it -- my guess is > that there isn't anything out there for FreeBSD that'll do what you want > out of the box.) That sounds interesting. Unfortunately, I can't spend a lot of time for playing around. Thanks a lot for your information, Ken. -Andre To Unsubscribe: send mail to majordomo@FreeBSD.org with "unsubscribe freebsd-scsi" in the body of the message