ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Dissector - how to reject packets

From: "Barnes, Pat" <Pat.Barnes@xxxxxxxxxxxxxxxxxx>
Date: Mon, 14 Jul 2008 13:11:58 +1000
Not displayed in the sense that packet-mbtcp.c does this:

proto_tree_add_text(modbus_tree, tvb, payload_start + 1, byte_cnt,
"Data");

That would be the latter, I guess.

-----Original Message-----
From: wireshark-dev-bounces@xxxxxxxxxxxxx
[mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] On Behalf Of Guy Harris
Sent: Monday, 14 July 2008 12:58 PM
To: Developer support list for Wireshark
Subject: Re: [Wireshark-dev] Dissector - how to reject packets


On Jul 13, 2008, at 5:30 PM, Barnes, Pat wrote:

> The application whose traffic I'm interested uses only Modbus messages
> 0x03 and 0x17, with register addresses above 1000. Each packet is 
> similar to an RPC call or response.
>
> The mbtcp dissector claims to intrepret the entire packet, but part of

> the relevant data I want to show is claimed by the dissector and not 
> displayed.

"Not displayed" in the sense that there's no item in the packet detail
pane that, when clicked, corresponds to the relevant data, or "not
displayed" in the sense that there is such an item, but it's just
displayed as raw data?
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
https://wireshark.org/mailman/listinfo/wireshark-dev



DISCLAIMER:---------------------------------------------------------------------------
This e-mail transmission and any documents, files and previous e-mail messages
attached to it are private and confidential. They may contain proprietary or copyright
material or information that is subject to legal professional privilege. They are for
the use of the intended recipient only.  Any unauthorised viewing, use, disclosure,
copying, alteration, storage or distribution of, or reliance on, this message is
strictly prohibited. No part may be reproduced, adapted or transmitted without the
written permission of the owner. If you have received this transmission in error, or
are not an authorised recipient, please immediately notify the sender by return email,
delete this message and all copies from your e-mail system, and destroy any printed
copies. Receipt by anyone other than the intended recipient should not be deemed a
waiver of any privilege or protection. Thales Australia does not warrant or represent
that this e-mail or any documents, files and previous e-mail messages attached are
error or virus free.
--------------------------------------------------------------------------------------