Ethereal-dev: [Ethereal-dev] Dissector Question

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

Date Index Thread Index Other Months All Mailing Lists
Date Prev Date Next Thread Prev Thread Next
From: "Steve Dickson" <steved@xxxxxxxxxxxx>
Date: Fri, 20 Jul 2001 18:42:21 -0400
Title: Dissector Question

Hello,

A few days ago, I submitted the PGM dissector. Since PGM is a transport protocol, I wanted people to be able to dissect protocols that were layered on top of PGM. So after I was done dissecting a PGM data packet, I called decided to call decode_tcp_ports(). This turns out not to be such a good idea, since a customer called wondering why his data (i.e the data after PGM) was being called iSCSI data (instead of just data).  I explained to him what the issues was, but it made me think that maybe there was better way.

So at this point I’m thinking my only options I have is either call dissect_data() and not give the ability to dissect protocols layered on PGM or used decode_tcp_port() and live with the uncertainties of what it comes up with.

Is there a better way?