Hi, thanks for the tip (it was probably an oversight on my part, since I didn't know about that limitation). It seems to work fine now, although I could probably do with automatically setting the "snaplen" somehow. Thanks.
On Tue, Oct 28, 2008 at 11:54 PM, Guy Harris <[EMAIL PROTECTED]> wrote: > > On Oct 28, 2008, at 2:05 PM, Tyson Key wrote: > > Hi, nice to see a shiny new release of libpcap and tcpdump so soon. >> Out of interest, is the "tcpdump: unsupported data link type USB_LINUX" >> bug/issue resolved when trying to capture USB traffic on a Linux box? >> > > If you mean "if I try to capture USB traffic on a Linux box, and don't give > the '-w' flag to get it to write the raw traffic to a file, will it print > 'tcpdump: unsupported data link type USB_LINUX'?", the answer is "yes", > because nobody's written a USB printer routine for tcpdump, so it *can't* > handle USB traffic in that case. If that's the problem in question - which > is more of a "lack of a feature" than a bug - it's still there. > > if you mwan "if I try to capture USB traffic on a Linux box, and *do* give > the '-w' flag to get it to write the raw traffic to a file, will it print > 'tcpdump: unsupported data link type USB_LINUX'?", the answer is "no", > because it just dumps the traffic out without interpretation, regardless of > whether it has a printer for the link-layer type or not, and thus can handle > USB traffic or any other type of traffic. If that's the problem in > question, it's fixed. > > - > This is the tcpdump-workers list. > Visit https://cod.sandelman.ca/ to unsubscribe. > -- Fight Internet Censorship! http://www.eff.org ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ Open-Source Community, and Technology Testbed: http://www.house404.co.uk/ - This is the tcpdump-workers list. Visit https://cod.sandelman.ca/ to unsubscribe.
