[Tyson Key <tyson.key@xxxxxxxxx>]

Hi Thomas,

If I remember correctly*, there is a method of forcing the D-BUS server and client to use TCP over the loopback interface for various purposes. 

When I was interested in working with IPC systems, about a year ago, I managed to build a reasonably large library of trace files that way (although I can't locate any at the moment), and I would have been interested in a D-BUS dissector for Wireshark.

* According to the manual page for the D-BUS Daemon , adding <listen>tcp:host=localhost,port=1234</listen> to one of the D-BUS configuration files, substituting 1234 in the example for your chosen port number should enable you for handling traffic via TCP.

I hope that helps.

Tyson.

On 17 September 2010 09:02, Thomas PABST <thomas.pabst@xxxxxxxxx> wrote:

Hi,

I'm going to make a new dissector for a new protocol. However, I would like to get some information before to start to be sure wireshark will be able to do it.

The protocol referred is D-Bus. However it seems D-Dbus use only UNIX Socket to communicate.
The purpose of this is to determine the better way to analyze all D-Bus message. Use wireshark or make my own application.

Best Regards


-----------------------------------------------------
Thomas PABST
thomas.pabst@xxxxxxxxx

___________________________________________________________________________
Sent via:    Wireshark-dev mailing list <wireshark-dev@xxxxxxxxxxxxx>
Archives:    http://www.wireshark.org/lists/wireshark-dev
Unsubscribe: https://wireshark.org/mailman/options/wireshark-dev
            mailto:wireshark-dev-request@xxxxxxxxxxxxx?subject=unsubscribe

-- 
                                          Fight Internet Censorship! http://www.eff.org
http://vmlemon.wordpress.com | Twitter/FriendFeed/Skype: vmlemon | 00447934365844