[email protected]'s profile - activity

the foo.dll now shows up on wireshark help menu-> plugins along with others with no issue. Thank you so very much for

Sorry!!!! I found out after looking through my notes. I removed those 2 lines from that file. I will add that back in. T

I used git extension to clone the branch master-2.6

sorry, here it is. https://drive.google.com/file/d/12QSpIOFtSxCSdTZ6JlOVLEqJrTRZoXto/view?usp=sharing

here's the link to make-plugin-reg.py https://drive.google.com/file/d/1ah6e6m_GLTVteXvULvkFGwuihm-tN2Rr/view?usp=sharing

sorry to have to inform you that the plugin_version issue still persist with building in ws64build directory as well. Th

ok, got it. hope this will fix the plugin version issue. Will let you know. And thank you for all your help.

ok, I remembered now. when I tried to generate build under wsbuild64, it gave me error as below. C:\Development\wsbuild

yes in tree. I did try earlier with wsbuild64 but with other errors I went back to in tree. I can try the wsbuild64 agai

I see plugin.c file being generated for gryphon source directory as well. I always run "msbuild /m /p:Configuration=RelW

yes, there's a plugin.c file sitting next to source code. That's what I copied and pasted on my previous comment. and I

Here's the output. plugin.txt on google drive. https://drive.google.com/file/d/1ah6e6m_GLTVteXvULvkFGwuihm-tN2Rr/view?us

Here's the output. plugin.txt on google drive. https://drive.google.com/file/d/1ah6e6m_GLTVteXvULvkFGwuihm-tN2Rr/view?us

Does it matter where the custom source code is? I had it under plugins/epan/... instead of directly under plugins. These

This is the generated plugin.c file from C:\Development\wireshark\plugins\epan\BDCP. include "config.h" include <gm

The warnings for bdcp are old code and no longer used. That's why I did not fix, but will comment the code later. Here's

https://drive.google.com/file/d/1TcUri7aAFGCsMT7_ovwsEH15F-uJ48dq/view?usp=sharing let me know if you have issue viewin

No "plugin_version" symbol for the custom dlls are still an issue when wireshark is launched. This is after repairing VS

sorry that I did not explained clearly. I have 2 virtual machines, one with windows7 wireshark version 1.12.6 which have

I deleted the zlib folders and rebuilt and that seems to have solved the issue. Right now, it generated dll's fine,but s

I deleted the zlib folders and rebuilt and that seems to have solved the issue. Right now, it generated dll's fine,but s

I deleted the zlib folders and rebuilt and that seems to have solved the issue. Right now, it generated dll's fine,but s

I deleted the zlib folders and rebuilt and that seems to have solved the issue. Right now, it generated dll's fine,but s

So, I repaired the VS2015 and that fixed the rc.exe and redl.dll issue. But it did not fix the plugin_version issue. So,

So, I repaired the VS2015 and that

mine is include(WiresharkPlugin) Plugin name and version info (major minor micro extra) set_module_info(bdcp 0 0 1 0)

I am having a similar issue currently that my custom.dll are not being recognized by wireshark verion 2.6. I added my p

I had a similar issue currently that my custom.dll are not being recognized by wireshark verion 2.6. I added my plugins

yeah, when I added my custom dlls in the downloaded wireshark folder /plugins/2.6/epan and when launch the wireshark, I

yes, I tried to download the qt5.9 and got error in installation. That's why I had to use their 5.11 which installed suc

Yes, not sure because I have windows 10 with 64 bit machine and also had to use a different qt version 5.11 instead of 5

Here's another one with register void proto_register_bdcp(void) { /* A header field is something you can search/filt

static void dissect_3146(tvbuff_t tvb, packet_info *pinfo, proto_tree *tree,void data); void proto_register_3146(void) {

here's one of my proto_reg_handoff file looks like. I tried to fix the warnings associated to my file and pretty much cl

was wondering before changing the build-in dissector, whether wireshark can provide a method to choose the frame prefere

tried disabling ll2tp protocol from GUI Analyze->EnabledProtocols-> unchecked the l2tp, and the frames are decode

oh, I saw my custom dll and gryphon.dll in run/RelWithDebInfo/plugins/2.6/epan instead of under run/RelWithDebInfo. It

oh, I saw my custom dll and gryphon.dll in run/RelWithDebInfo/plugins/2.6/epan instead of under run/RelWithDebInfo. It

oh, I saw my custom dll and gryphon.dll in run/RelWithDebInfo/plugins/2.6/epan instead of under run/RelWithDebInfo. It

after I changed the function to dissector_add_uint_with_preference, the dll did not get generated, instead when I launch

I believe this instruction maybe an issue. This is in proto_reg_handoff pmi_handle = create_dissector_handle(dissect

Our custom dll is to dissect l2tpv3 frames. It generates the custom dll in the RelWithDebInfo but when open wireshark, i

Our custom dll is to dissect l2tpv3 frames. It generates the custom dll in the RelWithDebInfo but when open wireshark, i

Our custom dissector is actually a modified l2tpv3 frames. Hence I believe I may some how need to route the l2tp dissect

I think I found the new dll's that I added in /run/RelWithDebInfo. But the dll's doesn't seem to dissect when I open the