Wireshark-bugs: [Wireshark-bugs] [Bug 3232] New: dissectors for totemnet and totemsrp protocols 
      
      
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=3232
           Summary: dissectors for totemnet and totemsrp protocols
                    implemented in corosync cluster engine
           Product: Wireshark
           Version: SVN
          Platform: PC
               URL: http://openais.org/doku.php
        OS/Version: All
            Status: NEW
          Severity: Enhancement
          Priority: Low
         Component: Wireshark
        AssignedTo: wireshark-bugs@xxxxxxxxxxxxx
        ReportedBy: yamato@xxxxxxxxxx
Masatake YAMATO <yamato@xxxxxxxxxx> changed:
           What    |Removed                     |Added
----------------------------------------------------------------------------
   Attachment #2713|                            |review_for_checkin?
               Flag|                            |
Created an attachment (id=2713)
 --> (https://bugs.wireshark.org/bugzilla/attachment.cgi?id=2713)
The patch deals the protocols.
Build Information:
Just apply the corosyn0.patch.
--
corosync is core part of openais cluster software.
This patch deals two lower layer protocols used in the corosync: totemnet and
totemsrp. The main aim of totemnet is encryption of udp multicast communication
in a cluster. The main aim of totemsrp is to implement Totem Single Ring
Protocol.
There are two capture files.
corosync-totemsrp--noencypted--2nodes.pcap: The packets in this file are not
encrypted. So you can dissect the packets in this file with no special
operation. 
corosync-totemsrp--key:example.com--2nodes.pcap: The packets in this file are
encrypted. So a key is needed to decrypt them. Open the Preferences dialog and
choose COROSYNC/TOTEMNET in Protocols branch. You will see "Totemnet Layer of
Corosync Cluster Engine" dialog. Give a key, "example.com" to "Private Key"
text field. Then push Apply or OK button.
-- 
Configure bugmail: https://bugs.wireshark.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.