Dinesh,
Thank you for the response. I will look into that file. Does the packet-brdwlk.c take into account a 2148 byte Fibre Channel frame? Or is it assumed to be a truncated 1500 byte Ethernet format? If smaller than a 2148 byte frame then when decoding ISL information I might lose GEPT or zoning information. Or is it across multiple packets? As well, will it decode the SCSI command set?
Thank you,
Michael
-----Original Message-----
From: Dinesh G Dutt [mailto:ddutt@xxxxxxxxx]
Sent: Friday, July 02, 2004 11:49 PM
To: Ethereal development
Subject: Re: [Ethereal-dev] Fibre Channel decoding question
Multiple ways:
- FCIP
- Cisco Port Analyzer Adapter Format (see packet-brdwlk.c)
- This encaps an FC frame into Ethernet
- Internal Cisco switch format (packet-mdshdr.c)
Dinesh
Rydeen, Mike writes:
> I posted this to the users mailing list originally, but believe that it
> should have been posted to this group instead...
>
> Hopefully this will be a quick question/answer, but you never know. Looking
> through the Ethereal supported protocols it appears that you support a large
> part of the Fibre Channel standard protocols (FC, FC-dns, FC-FCS, etc).
> After decoding the libpcap file format, I was able to create a supported
> Ethereal file out of a series of raw Fibre Channel frames. Currently I am
> using the IP over FC (122 - 0x7a) as my link layer type, but it appears that
> this LL does not decode the Common Transport layer, it is only looking for
> the payload IP contents from the Network Header, SNAP and down the list.
>
> Looking through the libpcap/tcpdump code I did not really see any other LL
> type. If there is not a supported type, how will Ethereal know how to
> decode the file? Is there a different file type that Ethereal is looking
> for? Or is this a "in the works" item?
>
--
Become the change you want to see in the world - Gandhi
_______________________________________________
Ethereal-dev mailing list
Ethereal-dev@xxxxxxxxxxxx
http://www.ethereal.com/mailman/listinfo/ethereal-dev
