[jboss-jira] [JBoss JIRA] Commented: (JGRP-324) Wireshark plugin for JGroups

[Richard Achmatowicz (JIRA)]

    [ https://jira.jboss.org/jira/browse/JGRP-324?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12437749#action_12437749 ] 

Richard Achmatowicz commented on JGRP-324:
------------------------------------------

Released a new version (0.1.0) of the dissector, to replace the draft version.

Here are the main changes from the change log:

7 November 2008: (version 0.1.0)
- Moved from port-based dissection (where the JGroups dissector is only
applied if the source or dest port of the packet packet matches a specified port)
to heuristic dissection (where the JGroups dissector is applied if the payload
of the packet is identified as a JGroups message).
- Added in support for checking wireformat version and whether or not the
plugin supports that wireformat version. At present, only 2.6.4 and binary-compatible versions are supported.
- Added in user profile settings to turn on/turn off display of Message subtrees and
Header subtrees in UI. This reduces the number of drill downs required to get at the
data in the captured packets.

One way to move this forward will be to complete the basic list of headers to be processed.

These are the headers which have already been implemented:
* TP/TCP/UDP
* PING
* NAKACK
* UNICAST
* GMS
* FDSOCK

These are some of the headers we need to go in (according to Bela and Vladimir):
* FD / FD_ALL
* FC
* STABLE
* STATE_TRANSFER
* MERGE2 


> Wireshark plugin for JGroups
> ----------------------------
>
>                 Key: JGRP-324
>                 URL: https://jira.jboss.org/jira/browse/JGRP-324
>             Project: JGroups
>          Issue Type: Feature Request
>            Reporter: Bela Ban
>            Assignee: Richard Achmatowicz
>            Priority: Minor
>             Fix For: 2.x
>
>         Attachments: Wireshark-subtree-options.jpg
>
>
> Write a C implementation of a Wireshark plugin which understands the JGroups wire format and displays information about the JGroups messages (e.g. sender, receiver, headers) in ethereal.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira