since there were no takers i went ahead and did it.
The repo at http://code.google.com/p/netmap/ has been
updated with a newer version of netmap, and the extra/
directory contains a netmap backend for libpcap
https://code.google.com/p/netmap/source/browse/extra/libpcap-netmap.diff
which works ag
15.01.2014, 00:10, "Luigi Rizzo" :
> since there were no takers i went ahead and did it.
>
> The repo at http://code.google.com/p/netmap/ has been
> updated with a newer version of netmap, and the extra/
> directory contains a netmap backend for libpcap
> https://code.google.com/p/netmap/source/br
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
>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
