On Mon, Sep 22, 2014 at 11:03 AM, Michal Labedzki
wrote:
> Ok, so it is only additional filtering on specified interface. It is fine.
>
> By the way: do you have a plan to add some extcap tool or support into
> libpcap for usbpcap? It will be fine if user will have USB sniffing on
> Windows by def
Ok, so it is only additional filtering on specified interface. It is fine.
By the way: do you have a plan to add some extcap tool or support into
libpcap for usbpcap? It will be fine if user will have USB sniffing on
Windows by defaults (out-of-box).
On 22 September 2014 09:18, Tomasz Moń wrote:
On Mon, Sep 22, 2014 at 8:54 AM, Michal Labedzki
wrote:
> It seems that you try to move some interfaces from interfaces list to
> one of interface. Why do not you add as much interfaces as you need?
> It seems to be similar case with Android: There is one devices (phone)
> connected by USB to comp
Hello Tomasz,
Thanks for this patch, but I have a question:
It seems that you try to move some interfaces from interfaces list to
one of interface. Why do not you add as much interfaces as you need?
It seems to be similar case with Android: There is one devices (phone)
connected by USB to compute
On Tue, Sep 16, 2014 at 10:29 AM, Tomasz Moń wrote:
> Is there anything like checkbox treeview currently in the works? Or
> could Mr. Someone propose a grammar for that and/or handle the
> implementation?
Never fear, Mr. Someone is here!
Multicheck was nearly exactly was I needed. I have just su
Hello folks,
Recent merge of extcap into Wireshark development tree got me
thinking about improving USBPcap user experience. The idea is to allow
user to select individual USB devices to capture from with the option
to automatically capture from newly connected devices.
I am thinking about someth
