Date: Tue, 20 Mar 2018 08:35:33 +0100 From: Hans Petter Selasky <hps@selasky.org> To: "freebsd-usb@FreeBSD.org" <freebsd-usb@FreeBSD.org> Subject: Re: R: usb's quirks ... how to sniff bios'es messages addressed to usb rom chip Message-ID: <670d0202-09a7-259e-c03c-54bc255d702a@selasky.org> In-Reply-To: <000401d3bfbe$c7f99370$57ecba50$@it> References: <!&!AAAAAAAAAAAYAAAAAAAAANB1sR69XHJMoG%2BMU1AT/qLCgAAAEAAAAP7hvnBBMjhJr%2Bv0J6Z9h1UBAAAAAA==@alice.it> <77f62042-bb44-7b36-0845-b88d233bfed0@selasky.org> <000401d3bfbe$c7f99370$57ecba50$@it>
next in thread | previous in thread | raw e-mail | index | archive | help
On 03/19/18 21:13, Vincenzo Di Salvo wrote: > Thanks. > > I have read the usbdump man page ... and I know that is wireshark is able to sniff usb traffic. > > My problem is how to detect the bit that increment the counter (always that the chip of the usb drive allows a such action). > Hi, I think you misunderstand what USB is. USB is a protocol. A processor runs on the USB device replying to this protocol. There is no direct hardware access. You need to ask the manufacturer which USB request returns the counter you are asking for. --HPS > Again: I kindly contact you to know if someone of the list has already done this test, if he can address me on the right street among the numerous informations shown by wireshark or usbdump. > > Tutorials weblink are appreciated (if they exist). > > Regards. > > Vincenzo.
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?670d0202-09a7-259e-c03c-54bc255d702a>