[Wireshark-dev] A plugin dissector and fragmented messages

2008-06-30 Thread Still Life
Hi, I'm developing a plugin dissector for a protocol used by a telephony over IP application on top of TCP protocol. Wireshark version is 0.99.5. Packets have this format: fmessage == one pdu (length=messagelength+18) |--|

[Wireshark-dev] A plugin dissector and fragmented messages

2008-06-30 Thread Still Life
Hi, my name is Fabio and I'm from Genova, Italy. I'm developing a plugin dissector for a protocol used by a telephony over IP application on top of TCP protocol. Packets have this format: fmessage == one pdu (lenght=messagelenght+18)

Re: [Wireshark-dev] A plugin dissector and fragmented messages

2008-06-30 Thread Still Life
Hi, I'm developing a plugin dissector for a protocol used by a telephony over IP application on top of TCP protocol. Wireshark version is 0.99.5. Packets have this format: Following this bug: https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1124 marked as a duplicate of bug 2103:

Re: [Wireshark-dev] H.223 dissector: how to retrive the name of subdissectors called over the H.223 payloads

2007-03-12 Thread Still Life
How about calling dissector_handle_get_short_name on the subdissector handle in dissect_mux_al_pdu? Thanks, it work! -- Email.it, the professional e-mail, gratis per te: http://www.email.it/f Sponsor: Questo inverno scaldale il cuore, con il prezioso calore di un Diamante. * Non

[Wireshark-dev] H.223 dissector: how to retrive the name of subdissectors called over the H.223 payloads

2007-03-08 Thread Still Life
Hi to all, I'm working on the H.223 dissector and I would like to retrive the name of the called subdissectors over the media streams payloads (AMR, H.263 ecc..) from within the H.223 dissector. Debugging the code I had the illusion of a solution looking at pinfo-layer_names-str but unfortunately

[Wireshark-dev] Developing Wireshark under Visual Studio 2003/2005

2007-02-13 Thread Still Life
Hi to all, H've already worked on a plugin dissector for Wireshark and I was able to develop it using a visual studio 2003 project. Now I need to add some feature to the Statistics menu and I'm thinking to create a visual studio project to work on the whole Wireshark source code. I read the

Re: [Wireshark-dev] Developing Wireshark under Visual Studio 2003/2005

2007-02-13 Thread Still Life
Thank you for the anwers, I asked this question to be sure there is not some official VS project. I'll use this solution, feel that will be quite confortable. :-) TNX, Fabio You can also create a makefile project to build with the custom wirshark makefile. Then drop in the

[Wireshark-dev] Save the bytes of a particular field from all the displayed packets in one file

2007-02-07 Thread Still Life
Excuse the double post here and on wireshark-users, the question span over the two topic... Hi to all, my question is general but I'll use my particular case to explain it. I would like to save a particular portion of an H223 over TCP capture file. Imagine you develop a display filter like this:

[Wireshark-dev] h.223 dissector: maybe a bug, mabe a fix?

2007-01-18 Thread Still Life
...or maybe a version mismatch between Wireshark and the H.223 dissector? Hi to all, I'm trying to do a fake h.223 over TCP/IP traffic between two terminals using, as sources, two raw h.223 dump files. The idea is to make an approximate Ethernet-TCP/IP header and fill it's datagram payload with

Re: [Wireshark-dev] problems with fragmented reassembly on tcp

2006-10-05 Thread Still Life
Jaap Keuter wrote: Hi, Have you checked chapter 2.7 of doc/README.developer? I guess Wireshark already provides all the tools you need for this. Yes, I read this chapter, probably I miss to understand something, maybe I have some difficult with the english language.

Re: [Wireshark-dev] A plugin dissector and fragmented messages

2006-09-07 Thread Still Life
Check out doc/README.developer chapter 2.7 Reassembly/desegmentation for protocols running atop TCP. Thanx, Jaap Thank you Jaap! I resolved my problem with the second method exposed in chapter 2.7. Now things seems to work. Cheers -- Email.it, the professional e-mail, gratis per te: