Hi I do actually have several ideas, all surrounding the two dissectors for POWERLINK (epl_v2) and openSAFETY (openSAFETY).
First, let me explain, I am working for the Austrian company, which invented both protocols and is pushing it behind the user organization EPSG, among several others. I am also the author of the openSAFETY dissector. For POWERLINK right now we have just a bunch of improvements to the way the dissector displays the package information, as well as cleaning up the code. For openSAFETY i would like to implement a state machine, where information across multiple packages could be collected (it is a segmented data download) and dissected rather like a segmented TCP or UDP stream. Whoever would do this, would have to implement a small but tricky state machine to monitor and update a buffer in the background, as the information gets downloaded to a device. On a more general note, I would like to see some adaption to the code, where a field in a dissector can be used as an address field, rather than the physical package sender or receiver. In an industrial ethernet network, physical network devices often act as gateway devices between protocols, and therefore masquerading the true originator of the package. In the case of openSAFETY you can see it in the example package download, where multiple openSAFETY packages are part of the same ethernet frame. Now, not every frame should be displayed separately, but it should be easier tow generate statistics data over a dissector, if the dissector is viable for an industrial ethernet solution. For all the topics mentioned above I could act as a mentor if needed. I do have some experience with the program, as I have been a participant some years ago. cheers, Roland On Thu, Feb 14, 2013 at 11:18 PM, Gerald Combs <ger...@wireshark.org> wrote: > Google recently announced the Google Summer of Code 2013. Proposals are > due March 29. Anyone have any ideas for projects? > > > -------- Original Message -------- > Subject: Google Summer of Code 2013 > Date: Mon, 11 Feb 2013 11:02:27 -0800 > From: Carol Smith <car...@google.com> > Reply-To: google-summer-of-code-announce+own...@googlegroups.com > To: Google Summer of Code Announce > <google-summer-of-code-annou...@googlegroups.com> > > > > Hi all, > > We're pleased to announce that Google Summer of Code will be happening > for its ninth year this year. Please check out the blog post [1] about > the program and read the FAQs [2] and Timeline [3] on Melange for more > information. > > [1] - > > http://google-opensource.blogspot.com/2013/02/flip-bits-not-burgers-google-summer-of.html > [2] - > > http://www.google-melange.com/gsoc/document/show/gsoc_program/google/gsoc2013/help_page > [3] - http://www.google-melange.com/gsoc/events/google/gsoc2013 > > Cheers, > Carol > > -- > You received this message because you are subscribed to the Google > Groups "Google Summer of Code Announce" group. > To unsubscribe from this group and stop receiving emails from it, send > an email to google-summer-of-code-announce+unsubscr...@googlegroups.com. > To post to this group, send email to > google-summer-of-code-annou...@googlegroups.com. > Visit this group at > http://groups.google.com/group/google-summer-of-code-announce?hl=en. > For more options, visit https://groups.google.com/groups/opt_out. > > > > > ___________________________________________________________________________ > Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> > Archives: http://www.wireshark.org/lists/wireshark-dev > Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev > mailto:wireshark-dev-requ...@wireshark.org > ?subject=unsubscribe >
___________________________________________________________________________ Sent via: Wireshark-dev mailing list <wireshark-dev@wireshark.org> Archives: http://www.wireshark.org/lists/wireshark-dev Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev mailto:wireshark-dev-requ...@wireshark.org?subject=unsubscribe
