Hello, I just modified our private plugins codes and made it compiled and built successfully after making changes to be compatible with the latest wireshark source code version 1.12. I was able to run the wireshark.exe without these modified plugins. But with the 2 modified plugins, when I tried to run the wireshark.exe, it gave me error as below in teh Wireshark Debug Console. Err Field 'L2TP Version' does not have an abbreviation. The plugin code does not have the L2TP anywhere and was wondering whether I need to make changes to any other files to be able to run these two new dll's. These new dll's ran fine with version 1.7 wireshark code at one point. I was just trying to update these to be able to run with v1.12. Please suggest. thanks Muriel asked 05 Sep '14, 10:59  christenmu |
This is a static archive of our old Q&A Site.
Please post any new questions and answers at ask.wireshark.org.
Try to run the checkapi and checkhf scripts in the Tools folder on your plugin.
Does your hf declarations follow the form of
static int hf_PROTOABBREV_FIELDABBREV = -1;
: static hf_register_info hf[] = { { &hf_PROTOABBREV_FIELDABBREV, { "FIELDNAME", "PROTOABBREV.FIELDABBREV", FT_FIELDTYPE, FIELDDISPLAY, FIELDCONVERT, BITMASK, "FIELDDESCR", HFILL } } };
thanks will take a look. Also, found out that the Makefiles that I was using are kind of old for these plugins, they are version 1.2 from 2011. When I used the makefiles from gryphon, I got compiler errors on the files that I did not touch.
Perhaps due to API cahnges or warnings turned errors.
I found out that the issue was with the PROTOABBREV.FIELDABBREV cannot be NULL string. Once I fixed several of the hf parameters' abbreviation field, it is working now. At some point, it must be ok to have this field as NULL. Thanks for steering me into looking at these hf fields.
No it's not as that's the filter name to be used in the filter "box" defining it as NULL would defy the purpose of defining a fileter in the first place...