This is our old Q&A Site. Please post any new questions and answers at ask.wireshark.org.

Hi guys,

I have finished developing(on Ubuntu 12.4) my second dissector for Wireshark as a plugin and made a patch file(.diff). However, when I went to patch the Wireshark source, obtained by 'svn co http://anonsvn.wireshark.org/wireshark/trunk/', the patch failed because the source had been updated to not include one of the plugins it used to and that I have on my main computer("giop" is the name). I know a way to fix this issue, I will just go in manually and add my dissectors as plugins but this defeats the whole purpose of the patch file. The version of the source on my main computer is only a month or two old. Is there any better way to make a patch file or something like it? I would hate to have to go through manually every month or so and re add all my dissectors.

My thought right now is to just download the source and save it to my drive and use the same source every time when I want to put it on a new computer. Any other ideas or critiques of mine would be greatly appreciated!

Thanks, Thomas

asked 10 Jul '12, 07:45

hildesht's gravatar image

hildesht
6114
accept rate: 0%

Just realized that I should probably be using a release version of Wireshark and not the trunk version. I'm assuming the trunk version is more of a developmental version, correct me if I am wrong but I hope switching to this will help.

(10 Jul '12, 07:50) hildesht

Correct: the stable/release versions are, well, more stable (meaning: less things change) so sticking to a release branch (the current one is trunk-1.8) is a good idea.

An even better idea would be to clean up your dissector and submit it to Wireshark so maintaining it becomes the core developers' job. :-)

(That being said, yes, I, too, maintain a number of "private" dissectors; I usually figure the punishment for this "sin" is having to maintain them myself.)

Also: the GIOP dissector did not go away, it was simply moved from being a plugin to being a built-in dissector (in epan/dissectors/ instead of plugins/giop).

permanent link

answered 10 Jul '12, 12:21

JeffMorriss's gravatar image

JeffMorriss ♦
6.2k572
accept rate: 27%

Thanks for the information! So far I have made 2 dissectors as plugins. One for the commands sent to the Parrot AR Drone (a quad copter that is available commercially) and a dissector for the MAVLink protocol that is used by arduPlanes. Do you think anyone else would be interested in these? I would like to share my work with the community but only if this is something that would be helpful.

Thanks, Thomas

(12 Jul '12, 10:53) hildesht

Well, one never knows. There are a LOT of protocol dissectors in Wireshark that are really quite specialized. Chances are if you're interested in dissecting those packets, somebody else will be too at some point or another. See this page for instructions on submitting your dissector(s) if you choose to do so:

http://www.wireshark.org/docs/wsdg_html_chunked/ChSrcContribute.html

(12 Jul '12, 15:57) JeffMorriss ♦

Remote-controlled planes sound like major nerd magnets, so I can imagine significant interest in dissecting both protocols by Wireshark users (I'm guessing the "ardu" in "arduPlanes" refers to Arduino, so we're definitely talking nerd magnet :-)). As such, both dissectors would probably be worthwhile additions to Wireshark for at least some users.

(12 Jul '12, 19:46) Guy Harris ♦♦
Your answer
toggle preview

Follow this question

By Email:

Once you sign in you will be able to subscribe for any updates here

By RSS:

Answers

Answers and Comments

Markdown Basics

  • *italic* or _italic_
  • **bold** or __bold__
  • link:[text](http://url.com/ "title")
  • image?![alt text](/path/img.jpg "title")
  • numbered list: 1. Foo 2. Bar
  • to add a line break simply add two spaces to where you would like the new line to be.
  • basic HTML tags are also supported

Question tags:

×637
×173
×11

question asked: 10 Jul '12, 07:45

question was seen: 2,193 times

last updated: 12 Jul '12, 19:46

p​o​w​e​r​e​d by O​S​Q​A