Bitcoin Forum

Bitcoin => Development & Technical Discussion => Topic started by: bluecmd on June 05, 2011, 10:30:30 AM



Title: Writing a dissector for wireshark
Post by: bluecmd on June 05, 2011, 10:30:30 AM
Hello.

After playing a bit with writing a python implementation of the protocol (extending pybitcoin) I find it very frustrating that I am unable to debug my packets. A quick scan around the wiki, IRC and forums revealed that no-one has stepped up to produce one, but I am going to write a wireshark dissector. Hopefully this will make the life of alternative implementations developers a bit easier.

I'll keep you posted - I should have something basic working by the end today or tomorrow and continue to extend it as I go along.


Title: Re: Writing a dissector for wireshark
Post by: bluecmd on June 05, 2011, 04:21:15 PM
You can track progress on https://github.com/blueCommand/bitcoin-dissector
Currently supporting version, verack and addr messages.


Title: Re: Writing a dissector for wireshark
Post by: blap on June 06, 2011, 12:04:40 AM
 :)


Title: Re: Writing a dissector for wireshark
Post by: alkor on June 06, 2011, 01:53:09 AM
In addition to pybitcoin, there is another python implementation of bitcion that you may be interested in:

https://github.com/phantomcircuit/bitcoin-alt

I think it is almost complete. The only thing that it is missing is the verify signature stuff in the scripting language.


Title: Re: Writing a dissector for wireshark
Post by: bluecmd on June 06, 2011, 08:03:38 AM
In addition to pybitcoin, there is another python implementation of bitcion that you may be interested in:

https://github.com/phantomcircuit/bitcoin-alt

I think it is almost complete. The only thing that it is missing is the verify signature stuff in the scripting language.
Perfect! pybitoin seems to be abandoned, this project is in a much better state. Thank you!
It will do nicely in testing the dissector.


Title: Re: Writing a dissector for wireshark
Post by: bluecmd on June 06, 2011, 06:30:00 PM
Success!

Every message except for IP transactions, alert and headers are handled. The reason why these are not implemented is that I cannot verify that they behave like the documentation. I will extend this as we go along, but this will hopefully help people debug their clients and such.

Screenshot:
http://data.fuskbugg.se/skalman02/4ded1c579b364_wireshark.jpg (http://data.fuskbugg.se/skalman02/4ded1c579b364_wireshark.jpg)


Title: Re: Writing a dissector for wireshark
Post by: Luke-Jr on June 07, 2011, 01:19:50 AM
Please add this project to BitGit (http://luke.dashjr.org/programs/bitcoin), and enable CIA notification :D