Huge thanks to our Platinum Members Endace and LiveAction,
and our Silver Member Veeam, for supporting the Wireshark Foundation and project.

Wireshark-dev: Re: [Wireshark-dev] Problems to fill COL_INFO in a new dissector

From: "BARILLY YANN" <Yann.Barilly@xxxxxxxxxxxxxxxxx>
Date: Fri, 13 Feb 2009 16:17:42 +0100
Hi,
I don't think you can get the info without find it in the tvbuff.

In my opinion, 2 possibilities:

- if the data is always at the same position, set an offset :
tvb_get_*(tvb(, ), STANDARD_OFFSET(, length));

- when you populate, update the COLL_INFO :
if (check_col(pinfo->cinfo, COL_INFO))
	col_append_fstr(pinfo->cinfo, COL_INFO, " data: %s", data);

___________________
Yann BARILLY
Alcatel-Lucent Orvault
Internal : 2 105 1224
External : + 33 2 51 78 12 24


-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of
xourciere.ext@xxxxxxxxxxxxxxxxxx
Sent: Thursday, February 12, 2009 7:30 PM
To: wireshark-dev@xxxxxxxxxxxxx
Subject: [Wireshark-dev] Problems to fill COL_INFO in a new dissector

Hello,

Well here is the full story.

I managed to code a new dissector from its ASN.1 description (Cisco
CRSPv3).
Everything is working except that I want to have some informations
showed in the column "Info".

At this time I can parse the tvb to match the info I need, but in this
case the dissector does the same work 2 times (one time to get the info
I need in the "Info" column and the other time with the dissector
generated code to populate the tree).

So, is there a way to get the information dissected in the packet
without parsing and doing the work of the dissector itself ? (NB: The
code of the dissector is generated from the ASN.1 file)

Regards,
------------------------------------------
Xavier OURCIERE.
France Telecom R&D
------------------------------------------


________________________________________________________________________
___
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
 
mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe