:~# time usb_modeswitch -c /etc/usb_modeswitch.d/1edf\:6003

Looking for default devices ...
Found default devices (1)
Accessing device 004 on bus 003 ...

USB description data (for identification)
-------------------------
Manufacturer: Selectwireless Incorporated
Product: Selectwireless CDMA ...

Works great!


Oct 26 17:17:34 t500 kernel: [531365.905190] scsi 4:0:0:0: rejecting I/O to dead device
Oct 26 17:17:34 t500 kernel: [531365.911728] cdc_acm 6-2:2.0: ttyACM0: USB ACM device
Oct 26 17:17:34 t500 kernel: [531365.914426] usbcore: registered new interface driver cdc_acm
Oct 26 17:17:34 ...

After updating libpcap I see my wireshark dump as follows from link: http://pastebin.com/4FPMbxXX
It looks almost similar to SniffUSB one.
I suspect that I connected the usb-device to the virtualbox machine near the frame#165.

I even used ...

Got it.
I'll update my wireshark/libcap to avoid packet truncation and try capturing again.

I really doubt that it may be helpful but could you take a look at log: http://pastebin.com/St5Jd7F3

I think I understood the idea. I see only class=2 device in my sniffusb logs. at the same time the wireshark truncated analyzed usb packets.
Could you give me an example of working captured log where switching message (as it is in the log) may be seen? The whole packet surrounded by a couple of ...

Josh, does the message string appear in a sniffer log explicitly (may be included in some other data message) or it is constructed from some other data?

I've got linux wireshark logs for different device pluggingin stages and related windows logs (windows works in virtualbox) except the stage of ...