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] Testing the new created .dll

From: Guy Harris <guy@xxxxxxxxxxxx>
Date: Tue, 16 Feb 2016 00:33:34 -0800
On Feb 16, 2016, at 12:24 AM, FIXED-TERM Scholz Tobias (DC-IA/EAI) <fixed-term.Tobias.Scholz@xxxxxxxxxxxxxxx> wrote:

> since I have compiled my new functions successfully for 2.1.0, I wanted to test it. On my computer it completely works for win64 and for win32 Wireshark 2.1.0 builds. Now I wanted to test the new Plug-In on the current available user version of Wireshark (2.0.1) on a different computer.

There is no guarantee that a plugin for one version of Wireshark will work with another version of Wireshark, other than that a plugin for an X.Y.Z release will work for an X.Y.W release, so there's no guarantee that a plugin built with 2.1.0 will work with 2.0.1 unless you recompile it.
> First off all, I even didn’t change anything for this variable. Second point is, that in my source code for 2.1.0 the type of this variable is defined as FT_FLOAT with BASE_NONE. So why is he telling me that I am using FT_ABSOLUTE_TIME?

The numerical value of FT_FLOAT, in 2.1.0, is 21.  The numerical value of FT_ABSOLUTE_TIME, in 2.0.1, is 21, so any code built with Wireshark 2.1.0 that uses FT_FLOAT will be interpreted as using FT_ABSOLUTE_TIME if run with 2.0.1.

So you'll have to recompile your plugin to work with 2.0.x.