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] Filtering

From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Tue, 31 Mar 2009 16:30:47 -0700

On Mar 31, 2009, at 4:22 PM, gogrady@xxxxxxxxx wrote:

The only way to dissect this protocol is through the dll, i cannot create it soley in the plugin as is the design requirements.

Can you tell whoever imposed those design requirements that perhaps they should impose *on the DLL* a design requirement that there be ways of getting, for each field, the *raw data* rather than some "helpful" human-readable interpretation of the field - and that it return the raw byte offset and length-in-bytes of a field, if it doesn't do so already - if they're going to make use of the DLL a requirement for the design of the Wireshark dissector?

Otherwise, it's somewhat like imposing a design requirement on a house that the only form of hammers to be used when building the house are sledgehammers, even for hammering nails into walls.