[prev in list] [next in list] [prev in thread] [next in thread] 

List:       wireshark-dev
Subject:    [Wireshark-dev] best practice questions - a tn3270 dissector
From:       Robert Hogan <robert () roberthogan ! net>
Date:       2009-02-13 20:32:38
Message-ID: 200902132032.38200.robert () roberthogan ! net
[Download RAW message or body]

I'm most of the way (I hope) through a tn3270 dissector. However I'm not 
sure of the most acceptable way of doing a couple of things:

- Should I just make TN3270 a sub-dissector of telnet? So users 
select 'decode as telnet' and get the tn3270 dissected implicitly? Or 
should it have a separate 'decode as' entry? If the latter, I'm not sure 
how I can call telnet as a 'super-dissector' or alternatively, avoid 
duplicating code.

- The best way of recognizing a tn3270 session is through the 'terminal 
type' telnet option at session negotiation. Browsing through other 
dissector code I can't find a canonical way of storing information about a 
given stream, other than possibly misusing the conversation api. I'm sure 
I'm missing a trick. What is the standard way of recognizing that a packet 
is from a stream previously identified as requiring a specific 
sub-dissector?

Thanks!
Robert
___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@wireshark.org>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
             mailto:wireshark-dev-request@wireshark.org?subject=unsubscribe
[prev in list] [next in list] [prev in thread] [next in thread]