[Wireshark-dev] Reassembly Fragment fail

2015-02-17 Thread Raj sekar
Hi, Hi , Iam developing a custom dissector on top of UDP which uses PDCP layer PDU RFC 2507 Selective Repeat ARQ Mechanism for segmentation and Reassembly. My message contains Beginning of Message continuation of message and end of message Messages are not

[Wireshark-dev] Dissector plugin not working with wireshark 1.12.3

2015-02-17 Thread yannick omnes
Hi list, I've recently updated my Wireshark to 1.12.3. I created a plugin that worked fine with previous versions but now I'm facing some problems. The plugins still compile and is correctly loaded by wireshark on Windows On my ubuntu 14.04, it is not loaded anymore. The problem seems to

Re: [Wireshark-dev] Dissector plugin not working with wireshark 1.12.3

2015-02-17 Thread Pascal Quantin
2015-02-17 10:08 GMT+01:00 yannick omnes yom...@aviwest.com: Hi list, I've recently updated my Wireshark to 1.12.3. I created a plugin that worked fine with previous versions but now I'm facing some problems. The plugins still compile and is correctly loaded by wireshark on Windows On my

Re: [Wireshark-dev] function of dissector_try_uint()

2015-02-17 Thread Pascal Quantin
2015-02-17 8:48 GMT+01:00 Vishnu Bhatt vishnu.bh...@aricent.com: Thanks for the reply. Can you please tell me what is the function of p_get_proto_data() in Wireshark. Specifically, in case of FP frame, what is the role of this function? p_fp_info = (fp_info

Re: [Wireshark-dev] Dissector plugin not working with wireshark 1.12.3

2015-02-17 Thread yannick omnes
Hi Pascal, Thank you for your answer, The plugin crashes (dereferencing a NULL pointer) in the second iteration of the loop in proto_register_field_array. Looking around, i noticed that the bitmask field of header_field_info changed betwen 1.10.6 and 1.12.3, it was a guint64 and is now a

Re: [Wireshark-dev] False positive from the new Look for incomplete dissectors function.

2015-02-17 Thread Dario Lombardo
On Fri, Feb 13, 2015 at 5:15 PM, Jeff Morriss jeff.morriss...@gmail.com wrote: I have to admit that I like being able to click on a byte and see what field it maps to. From that perspective I like when padding is claimed by the dissector which knew it was padding. And when CR+NL are claimed

Re: [Wireshark-dev] Dissector plugin not working with wireshark 1.12.3

2015-02-17 Thread Pascal Quantin
2015-02-17 12:41 GMT+01:00 yannick omnes yom...@aviwest.com: Hi Pascal, Thank you for your answer, The plugin crashes (dereferencing a NULL pointer) in the second iteration of the loop in proto_register_field_array. Looking around, i noticed that the bitmask field of header_field_info