On Mon, Nov 15, 2010 at 5:59 PM, Guy Harris g...@alum.mit.edu wrote:
Just been busy. I've assigned 231 as DLT_DBUS/LINKTYPE_DBUS, and checked the
changes into the trunk and 1.1 branches and pushed them.
Thank you, Guy!
I have just published a tool to capture D-Bus messages in a libpcap
On Wed, Nov 3, 2010 at 2:45 PM, Martin Vidner mar...@vidner.net wrote:
Guy Harris wrote:
On Oct 31, 2010, at 12:29 AM, Martin Vidner wrote:
please allocate a new network type for libpcap dump files, as
described in
http://wiki.wireshark.org/Development/LibpcapFileFormat#Global_Header
.
It
On Nov 15, 2010, at 8:23 AM, Martin Vidner wrote:
Hello? Are there some concerns that I should address? Just too busy?
Just been busy. I've assigned 231 as DLT_DBUS/LINKTYPE_DBUS, and checked the
changes into the trunk and 1.1 branches and pushed them.-
This is the tcpdump-workers list.
Guy Harris wrote:
On Oct 31, 2010, at 12:29 AM, Martin Vidner wrote:
please allocate a new network type for libpcap dump files, as
described in
http://wiki.wireshark.org/Development/LibpcapFileFormat#Global_Header
.
It is for dumping traffic on D-Bus,
http://en.wikipedia.org/wiki/D-Bus
,
Hi,
please allocate a new network type for libpcap dump files, as
described in
http://wiki.wireshark.org/Development/LibpcapFileFormat#Global_Header
.
It is for dumping traffic on D-Bus, http://en.wikipedia.org/wiki/D-Bus
, and the packets would contain raw D-Bus messages:
On Oct 31, 2010, at 12:29 AM, Martin Vidner wrote:
please allocate a new network type for libpcap dump files, as
described in
http://wiki.wireshark.org/Development/LibpcapFileFormat#Global_Header
.
It is for dumping traffic on D-Bus, http://en.wikipedia.org/wiki/D-Bus
, and the packets
