Re: Question regarding SCSI dissectors

[Jaap Keuter <jaap.keuter () xs4all nl>]

Hi,

This would be one for the developer list.
Anyway, if you/someone can whip together a patch it will be considered.

Thanks,
Jaap

Jay Ribak wrote:
> I apologize in advance if this question is more appropriate for the
> developers list...
>
> I have been using Wireshark to analyze some iSCSI traffic recently and I
> am wondering if there are any planned enhancements to decode the SCSI
> Payload data, or if there are technical limitations preventing this from
> occurring.
>
> For example, I am looking at the response from a PRIN command, Wireshark
> displays the SCSI Payload but does not break out the individual fields
> in that payload.   For example, the SPC-4 defines the response data for
> a PRIN Read Keys service action in the format:
>
> Bytes 0-3-PRgeneration
> Bytes 4-7-Additional Length  (n-7)
> Bytes 8-15-Reservation Key 1
> Bytes (n-7)-n-Additional Reservation Keys
>
> It is relatively trivial to decode the payload manually, but it would be
> extremely convenient if Wireshark would do the dissection automatically
> and display fields like the PRgeneration and the actual reservation
> keys.
>
> Regards,
> Jay

___________________________________________________________________________
Sent via:    Wireshark-users mailing list <wireshark-users () wireshark org>
Archives:    http://www.wireshark.org/lists/wireshark-users
Unsubscribe: https://wireshark.org/mailman/options/wireshark-users
             mailto:wireshark-users-request () wireshark org?subject=unsubscribe