Ethereal-users: Re: [Ethereal-users] capturing scsi data

Note: This archive is from the project's previous web site, ethereal.com. This list is no longer active.

From: "Martin Regner" <martin.regner@xxxxxxxxx>
Date: Sun, 17 Nov 2002 14:34:28 +0100
Hi,

I'm quite sure that Ethereal (or actually libpcap/wincap) cannot not capture SCSI traffic.

There seems also not to be any support for reading some type of SCSI capture files in Ethereal (if there
was some other program/utility that could be used to capture the data). 

It seems that currently the only way the SCSI dissector is used is from the iSCSI dissector.
iSCSI means "SCSI over TCP/IP".
http://www.diskdrive.com/reading-room/standards.html

There is also a protocol called hyperscsi (SCSI over Ethernet) implemented in Ethereal.
http://nst.dsi.a-star.edu.sg/mcsa/hyperscsi/spec-intro.pdf
But the hyperscsi dissector seems not to use the SCSI dissector.

Regards,
  Martin

PS! If you want to look on an iSCSI capture sample - there is one in the following message.

http://www.ethereal.com/lists/ethereal-dev/200110/msg00227.html

The port number used in that file is not the IANA registered port for iSCSI (3260) but instead the preliminar port number 5003 that
was used earlier by some iSCSI implementations (e.g. Cisco).

By default the messages in that file may not be decoded as iSCSI if you don't change the "Preferences/Protocols/iSCSI/Target port" to 5003  (or 0).

Frame 1 (114 bytes on wire, 114 bytes captured)
    Arrival Time: Oct 20, 2001 19:43:24.620299000
    Time delta from previous packet: 0.000000000 seconds
    Time relative to first packet: 0.000000000 seconds
    Frame Number: 1
    Packet Length: 114 bytes
    Capture Length: 114 bytes
Ethernet II, Src: 00:80:c8:ec:85:9a, Dst: 00:04:76:98:2e:6b
    Destination: 00:04:76:98:2e:6b (00:04:76:98:2e:6b)
    Source: 00:80:c8:ec:85:9a (00:80:c8:ec:85:9a)
    Type: IP (0x0800)
Internet Protocol, Src Addr: 192.168.1.20 (192.168.1.20), Dst Addr: 192.168.1.21 (192.168.1.21)
    Version: 4
    Header length: 20 bytes
    Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
        0000 00.. = Differentiated Services Codepoint: Default (0x00)
        .... ..0. = ECN-Capable Transport (ECT): 0
        .... ...0 = ECN-CE: 0
    Total Length: 100
    Identification: 0x751c
    Flags: 0x04
        .1.. = Don't fragment: Set
        ..0. = More fragments: Not set
    Fragment offset: 0
    Time to live: 64
    Protocol: TCP (0x06)
    Header checksum: 0x41fe (correct)
    Source: 192.168.1.20 (192.168.1.20)
    Destination: 192.168.1.21 (192.168.1.21)
Transmission Control Protocol, Src Port: 1025 (1025), Dst Port: 5003 (5003), Seq: 3580059735, Ack: 3823250098, Len: 48
    Source port: 1025 (1025)
    Destination port: 5003 (5003)
    Sequence number: 3580059735
    Next sequence number: 3580059783
    Acknowledgement number: 3823250098
    Header length: 32 bytes
    Flags: 0x0018 (PSH, ACK)
        0... .... = Congestion Window Reduced (CWR): Not set
        .0.. .... = ECN-Echo: Not set
        ..0. .... = Urgent: Not set
        ...1 .... = Acknowledgment: Set
        .... 1... = Push: Set
        .... .0.. = Reset: Not set
        .... ..0. = Syn: Not set
        .... ...0 = Fin: Not set
    Window size: 63712
    Checksum: 0x5a2b
    Options: (12 bytes)
        NOP
        NOP
        Time stamp: tsval 1074526, tsecr 28891501
iSCSI (SCSI Command)
    Opcode: SCSI Command (0x01)
    0... .... = X: Not retry
    .0.. .... = I: Queued delivery
    Flags: 0xc1
        1... .... = F: Final PDU in sequence
        .1.. .... = R: Data will be read from target
        ..0. .... = W: No data will be written to target
        .... .001 = Attr: Simple (0x01)
    CRN: 0x00
    TotalAHSLength: 0x00
    DataSegmentLength: 0x00000000
    LUN: 0000000000000000
    InitiatorTaskTag: 0x000a16c3
    ExpectedDataTransferLength: 0x00001000
    CmdSN: 0x000a16c2
    ExpStatSN: 0x000a16c2
SCSI CDB
    Opcode: Read(10) (0x28)
    DPO = 0, FUA = 0, RelAddr = 0
    Logical Block Address (LBA): 43940554
    Transfer Length: 8
    Vendor Unique = 0, NACA = 0, Link = 0


-----Original Message-----
From: Saul Tamari <saul@xxxxxxxxxx>
To: ethereal-users@xxxxxxxxxxxx <ethereal-users@xxxxxxxxxxxx>
Date: Sunday, November 17, 2002 1:27 PM
Subject: [Ethereal-users] capturing scsi data


hi

I noticed that Ethereal can decode scsi capture files. How do I capture
scsi data? Is there a way to capture it with Ethereal?


Thanks,
Saul
_______________________________________________
Ethereal-users mailing list
Ethereal-users@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-users