Re: [Wireshark-dev] Various problems with tshark

2015-08-30 Thread Pascal Quantin
Hi Jörg, 2015-08-31 5:34 GMT+02:00 Joerg Mayer : > When using tshark from head I have a bunch of problems right now: > > 1) stderr is getting spammed with > (process:9870): Capture-WARNING **: Dissector stp incomplete in frame > 41915: undecoded byte number 57 (0x0030+9) > You seem to have activ

[Wireshark-dev] Various problems with tshark

2015-08-30 Thread Joerg Mayer
When using tshark from head I have a bunch of problems right now: 1) stderr is getting spammed with (process:9870): Capture-WARNING **: Dissector stp incomplete in frame 41915: undecoded byte number 57 (0x0030+9) 2) -T fields -e _ws.col.info isn't working (empty column), both with and without -V

Re: [Wireshark-dev] MSVC 2015 (VC14) notes/issue

2015-08-30 Thread Bill Meier
On 8/12/2015 12:21 PM, Bill Meier wrote: 2. I had to disable building with geoip because: #error: Macro definition of snprintf conflicts with Stan dard Library function declaration (compiling source file packet-ip.c) A little digging finds that the Windows Wireshark version of the GeoIP

Re: [Wireshark-dev] Problem writing a file dissector for vwr capture files

2015-08-30 Thread Hadriel Kaplan
When you say "properly", you mean like so it can be submitted into master? I think the *right* thing is a much bigger change, and involves creating wiretype subtypes for each file-format reader type. But in the meantime you could wrap all your code in #ifdef so it's not normally compiled in, but wh

Re: [Wireshark-dev] Problem writing a file dissector for vwr capture files

2015-08-30 Thread Joerg Mayer
On Sun, Aug 30, 2015 at 07:53:09AM -0400, Hadriel Kaplan wrote: > Did you add the magic info into the magic_files array in > wiretap/mime_file.c? It looks like it's necessary. Ah, that was the part I was missing. Thanks! Of course now that I did look at it, it doesn't help me because the file for

Re: [Wireshark-dev] Problem writing a file dissector for vwr capture files

2015-08-30 Thread Hadriel Kaplan
Did you add the magic info into the magic_files array in wiretap/mime_file.c? It looks like it's necessary. -hadriel On Sun, Aug 30, 2015 at 4:22 AM, Joerg Mayer wrote: > Hello, > > I'm trying to write a file dissector for the IxVeriWave (.vwr) capture files > (without loosing the ability to ope

Re: [Wireshark-dev] Can I compile only the plugins on Windows?

2015-08-30 Thread Anders Broman
Den 30 aug 2015 10:15 skrev "Adir Shemesh" : > > I already have Wireshark compiled, but I'm developing a plugin and compiling everything takes a lot of time. > In Linux I can use "make -C plugins" but I couldn't find a solution for windows. > Run the nmake command in the plugins directory, you may

[Wireshark-dev] Problem writing a file dissector for vwr capture files

2015-08-30 Thread Joerg Mayer
Hello, I'm trying to write a file dissector for the IxVeriWave (.vwr) capture files (without loosing the ability to open said capture files normally of course) and am failing: Running "tshark -X 'read_format:MIME Files Format' -V -r testfile.vwr" (or the equivalent steps in wireshark) results in

[Wireshark-dev] Can I compile only the plugins on Windows?

2015-08-30 Thread Adir Shemesh
I already have Wireshark compiled, but I'm developing a plugin and compiling everything takes a lot of time. In Linux I can use "make -C plugins" but I couldn't find a solution for windows. ___ Sent via:Wireshark-dev mailin