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.
_
Ping.
--
Pozdrawiam / Best regards
-
Michał Łabędzki, Software Engineer
Tieto Corporation
Product Development Services
http://www.tieto.com / http://www.tieto.pl
---
ASCII: Michal Labedz
Hello,
Can I help you with something? (aka ping). Can I do Pull Request(s)?
Pozdrawiam / Best regards
-
Michał Łabędzki, Software Engineer
Tieto Corporation
Product Development Services
It seems that new bluetooth DLT will be similar to existing LLCP:
http://www.tcpdump.org/linktypes/LINKTYPE_NFC_LLCP.html
Adapter Number -> Adapter Id (2 ocetets, network order)
Flags -> Opcode (2 octets, network order)
Payload -> Payload
Pozdrawiam / Best regards
---
>I'd like to suggest that "struct _pcap_bluetooth_monitor_
header" is too generic a name when this header only applies to the
internal workings of an operating system's HCI and adapter-lifetime
traffic.
Ok, "struct _pcap_bluetooth_linux_monitor_header" is ok?
But this is for second phase. There is
I'd like to suggest that "struct _pcap_bluetooth_monitor_header" is too generic
a name when this header only applies to the internal workings of an operating
system's HCI and adapter-lifetime traffic.
There are other forms of bluetooth monitoring that are not OS-specific nor even
cover HCI. Fo
On 10 January 2014 01:47, Guy Harris wrote:
>
> On Dec 29, 2013, at 11:21 PM, Michal Labedzki
> wrote:
>
>> Implementation in libpcap is very similar to pcap-bt-linux.c, but:
>> 1. There is only one interface, let call it bluetooth-monitor
>
> I.e., it's like the "any" device".
"Any Bluetooth D
On Dec 29, 2013, at 11:21 PM, Michal Labedzki wrote:
> Implementation in libpcap is very similar to pcap-bt-linux.c, but:
> 1. There is only one interface, let call it bluetooth-monitor
I.e., it's like the "any" device".
> 2. Pseudo header is:
>guint16 adapter_id;
So that presumably ind
Hello,
You can see code in Wireshark side (great example, very similar, but
this is only support for capture file changes):
https://bugs.wireshark.org/bugzilla/attachment.cgi?id=12394
Implementation in libpcap is very similar to pcap-bt-linux.c, but:
1. There is only one interface, let call it bl
On Dec 27, 2013, at 3:13 AM, Michal Labedzki wrote:
> 1. Bluetooth Linux Monitor use psedoheader to provide Opcode and
> Adater Id which are required to correctly dissect payload (like
> Bluetooth H4 with pseudoheader)
What is the detailed format of the pseudo-header, and what is the payload th
Hello again,
I think the best name for this is DLT_BLUETOOTH_LINUX_MONITOR, because
this is Linux kernelspace, not BlueZ userland.
By the way: I have completed implementation for new interface called
bluetooth-monitor, based on this DLT. Please let me know when I can
send patch on github for incl
Hello,
It seems that in BlueZ 5 there is no interface provided for better
user experience. Let call it "monitor" and it is used for capture all
Bluetooth adapter in the same time within information about adding new
adapter or delete existing one (there are special opcodes for that
[separated packe
12 matches
Mail list logo
