On 02/14/2014 04:46 PM, Guy Harris wrote:
>
> What is the "nanosecond offset to pcap timestamp"? pcap-ng lets you specify
> the resolution of time stamps, and even pcap lets you, at least with newer
> versions of libpcap and Wireshark, specify nanosecond resolution with a
> different magic num
On Feb 14, 2014, at 4:46 PM, Guy Harris wrote:
> Translating them into the style in the pages under
> http://www.tcpdump.org/linktypes would be helpful. It avoids worrying about
> C/C-derived-language data structure names - or anything *else* about C and
> languages derived from it - and als
On Feb 14, 2014, at 12:18 PM, Chris Kilgour wrote:
> I'd like to request two LINKTYPE/DLT allocations for RF Bluetooth Captures,
> with the details described here [2].
What is the "nanosecond offset to pcap timestamp"? pcap-ng lets you specify
the resolution of time stamps, and even pcap let
On Dec 27, 2013, at 3:13 AM, Michal Labedzki wrote:
> I think the best name for this is DLT_BLUETOOTH_LINUX_MONITOR, because
> this is Linux kernelspace, not BlueZ userland.
OK, LINKTYPE_BLUETOOTH_LINUX_MONITOR and DLT_BLUETOOTH_LINUX_MONITOR have been
assigned the value 254.
_
This email is submitted under the process described at [1].
I'd like to request two LINKTYPE/DLT allocations for RF Bluetooth Captures,
with the details described here [2]. The details there were compiled after
technical consultations on the Ubertooth mailing list and IRC.
To conform with the
Yes, even so
2014-02-13 16:36 GMT-05:00, Guy Harris :
>
> On Feb 13, 2014, at 1:24 PM, "Daniel H. Bahr" wrote:
>
>> For some reason, as I said earlier, if the SIGSEGV is not connected to
>> the bailout nothing queer happens,
>
> Even if you leave SIGQUIT and SIGTERM connected?
>
>
___
