On Sep 20, 2007, at 5:37 AM, Paolo Abeni wrote:
Hopefully this time the attachment should be plain text and avoiding
strange MS encoding.
Yup, it worked.
Checked in, along with updates to FILES and INSTALL.txt.
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubscrib
hello,
on Thu 9/20/2007 12:18 AM Guy Harris wrote:
> Could you re-attach that patch as text? It appears to be in
> Microsoft's TNEF format;
Sorry for the issue. I'm not sure that the exchange server will preserve
the plain text formatting [ :-) ], so I'm using another mail account...
The p
Hello,
on Thu 9/20/2007 12:18 AM Guy Harris wrote:
> Could you re-attach that patch as text? It appears to be in
> Microsoft's TNEF format;
I'm sorry for the issue. I have to use exchange and this lead to
problems...
Hopefully this time the attachment should be plain text and avoiding
strang
On Sep 19, 2007, at 12:09 AM, Abeni Paolo wrote:
Thanks! The attached patch used the newly added DLT for hci h4
frames, adding an informative header to each frame.
The header carries (in the first bit in network byte order) the
direction bit for the associated frame and nothing else.
It also
on Wed 9/19/2007 4:53 AM Guy Harris wrote:
> I've assigned DLT_BLUETOOTH_HCI_H4_WITH_PHDR, with a value of 201. If
> there's anything else that would be useful, that could be added to the
> header as well.
Thanks! The attached patch used the newly added DLT for hci h4 frames, adding
an inf
On Sep 7, 2007, at 1:23 AM, Abeni Paolo wrote:
following the discussion about the missing direction information in
bluetooth H4 captures(see http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1751)
, I would like to request a new DLT type for a modified bluetooth
linktype.
I'm planning to
hello,
following the discussion about the missing direction information in bluetooth
H4 captures(see http://bugs.wireshark.org/bugzilla/show_bug.cgi?id=1751), I
would like to request a new DLT type for a modified bluetooth linktype.
I'm planning to add 32 bit header (so big just for alignment
