I am working on adapting some tcpdump patches for Transarc RX protocol
support to ethereal.
RX is the lower level protocol. The data portion of it's packets are
processed differently according to the different services it is talking to.
For example: ... UDP / RX / AFS-File-Server-Request, UDP / RX /
AFS-File-Server-Reply,
UDP / RX / AFS-Callback-Request ....
It seems to me that this would make sense to register as another protocol,
but at the same time, it is very distinctly a component of the RX packets.
The main thing is it seems more intuitive for it to have it's own item in
the protocol tree instead of being buried inside another.
Would it be better to register "AFS-File-Server-Request" as another
protocol, or add it as a subtree of RX? If I add is as a subtree of RX, what
would be the best way to have the "AFS..." added to the tree? As a FT_BYTE
item that contains the entire data portion of the RX packet, or using
add_text, or some other way?
If I were to register it as another protocol, I was thinking along the lines
of registering it as:
proto_rx
proto_rx_fs
proto_rx_cb
proto_rx_.... several others
How would you suggest I go about structuring this?
-- Nathan
------------------------------------------------------------
Nathan Neulinger EMail: nneul@xxxxxxx
University of Missouri - Rolla Phone: (573) 341-4841
Computing Services Fax: (573) 341-4216
