ANNOUNCEMENT: Live Wireshark University & Allegro Packets online APAC Wireshark Training Session
April 17th, 2024 | 14:30-16:00 SGT (UTC+8) | Online

Wireshark-dev: Re: [Wireshark-dev] Wireshark 1.3.1 and python dissector

From: Joni Korhonen <joni.korhonen@xxxxxxxxx>
Date: Mon, 9 Nov 2009 17:39:00 +0200
Hello Sebastien,

OK, I'll be following this project...well because python is python :-)

Let us know when you have something

Regards,
Joni

>From: Sébastien Tandel <sebastien.tandel@xxxxxxxxx>
>Date: Mon, 9 Nov 2009 10:41:18 +0100
>
>Hi Joni,
>
>
>python dissectors is something highly experimental and not complete 'til now. I made only one commit to the tree ;)
>
>The tests I made were only with tshark and on Linux. It appears that it is not working for windows nor with wireshark. I'm not >sure why in the case of wireshark. I thought that if working with tshark, it should work for wireshark too but it seems that it >needs some additional stuffs.
>
>I will have some time these next weeks to work on this and hope to fix and extend a bit this first draft.
>
>
>Regards,
>Sebastien Tandel
>>2009/11/9 Joni Korhonen <joni.korhonen@xxxxxxxxx>:
>> Hello,
>> First of all, I was more than happy to hear that ws dissectors could
>> also be done with python :-)
>> Has there been any changes in how to use python dissector in ws 1.3.1?
>>
>> I tried the example showed in wiki page
>> (http://wiki.wireshark.org/Python), but it didn't work at all:
>> (register_protocol): subt = tp.subtrees() causes "Subtree object is
>> not callable", since its a reference to Subtree object...
>>
>> changing to:
>>
>> subt = tp.subtrees caused crash:
>> **
>> ERROR:packet.c:728:dissector_add: assertion failed: (sub_dissectors)
>> Aborted
>>
>> Basic info:
>> (Ubuntu 9.04)
>> I used developement version of wireshark (1.3.1)
>> gcc (GCC) 4.2.4
>> Python 2.6.2
>>
>> Any Ideas what I'm missing?
>>
>> Br
>> Joni
>>