Hi, any chance that a "usbany" (or similar) pseudo-device could be added in
a future version to capture on all USB buses, similar to the standard "any"
device for non-USB interfaces?
Thanks, Tyson.
On Mon, Nov 24, 2008 at 8:10 PM, Guy Harris <[EMAIL PROTECTED]> wrote:
>
> On Oct 29, 2008, at 7:3
On Oct 29, 2008, at 7:38 PM, Jean-Louis wrote:
in accordance with usbmon.txt in "mmap mode" the data is at
&mmap_area[vec[i]] + 64;
rather than
&mmap_area[vec[i]] + 48;
with mmap ther'is 16Byte filled with 0 first to the real data...
so if i.e. I have caplen = 18Byte, in file.pcap I have 1
On Oct 29, 2008, at 7:35 PM, Jean-Louis wrote:
Added possibility to set "snaplen" also in "mmap mode"
Checked in (with a variable name change to make it clear that the
variable in question is the maximum length).
-
This is the tcpdump-workers list.
Visit https://cod.sandelman.ca/ to unsubs
On Oct 29, 2008, at 7:32 PM, Jean-Louis wrote:
in "text mode" ther'is direction check, I don't know how I can use
this "filter", but the check is broken
It can only be used by calling pcap_setdirection() in an application.
I don't know what the motivation is for inverting the direction on
On Oct 29, 2008, at 7:29 PM, Jean-Louis wrote:
*** pcap-usb-linux.c29 Oct 2008 14:17:44 - 1.2
--- pcap-usb-linux.c29 Oct 2008 15:03:27 - 1.3
***
*** 67,78
#define USB_LINE_LEN 4096
- #define PIPE_IN 0x80
- #define PIPE_ISOCHRON
On Nov 24, 2008, at 10:53 AM, Guy Harris wrote:
On Oct 29, 2008, at 7:27 PM, Jean-Louis wrote:
transfer direction in "text mode" is broken...
in accordance with usbmon.txt transfer direction is in
endpoint_number rather than transfer type
ther'is premature stop when capture traffic on li
On Oct 29, 2008, at 7:27 PM, Jean-Louis wrote:
transfer direction in "text mode" is broken...
in accordance with usbmon.txt transfer direction is in
endpoint_number rather than transfer type
ther'is premature stop when capture traffic on linux with "text
mode" due to incorrect check of ur
