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] Dissecting a portion of a protocol owned by anotherdissector

From: "Jeremy O'Brien" <obrien654j@xxxxxxxxx>
Date: Tue, 23 Feb 2010 14:50:09 -0500
Hmm... I was trying to avoid touching any existing dissectors to allow
my plugin to be as modular as possible. There's no other (easy) way?

On Tue, Feb 23, 2010 at 14:11, Anders Broman <a.broman@xxxxxxxxx> wrote:
> Hi,
> Not easily, but if you are doing something reasonably like dissecting
> Vendor specific fields a patch to the existing dissector providing a "hook"
> For a plugin would be acceptable, like registering a dissector table a
> Custom plugin could register in.
>
> Regards
> Anders
> -----Ursprungligt meddelande-----
> Från: wireshark-dev-bounces@xxxxxxxxxxxxx
> [mailto:wireshark-dev-bounces@xxxxxxxxxxxxx] För Jeremy O'Brien
> Skickat: den 23 februari 2010 19:02
> Till: Developer support list for Wireshark
> Ämne: [Wireshark-dev] Dissecting a portion of a protocol owned by
> anotherdissector
>
> Hello,
>
> I am trying to write a wireshark plugin that dissects only a certain
> field of another dissector. I read about writing tap dissectors, but
> these seem to still receive entire packets rather than just the
> portion I'm interested in. I am trying to avoid copying large chunks
> of the main dissector just to get down to the area my dissector is
> interested in. Does wireshark provide a way to do this?
>
> Thank you,
> Jeremy
> ___________________________________________________________________________
> 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
>
> ___________________________________________________________________________
> 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
>