Hi.
I think you are comparing apples to oranges here.
SnoopyPro is a USB capture tool and it captures the various layers of
the USB protocol.
When used for EthernetOverUSB several layers above the USB layer is
where you will find Ethernet frames.
So with SnoopyPro you are capturing USB
Hi, assuming that you're referring to USB Communications Device Class, or
ATM-over-USB devices (e.g. some consumer ADSL routers), everything gets sent
as a generic URB_BULK(?) transmission, if I remember correctly, which
Wireshark can't currently analyze. I'm not sure myself why it constantly
Tyson,
Thanks I'll check that out. I also had the idea that perhaps I could export
both capture logs into ASCII text and then use a perl script or something to
try and identify two corresponding packets the raw USB packet that snoopypro
has which matches the clean ethernet only packet(s) that
Well I found a packet to packet correlation between the two sniffers and then I
tried to hand dissect the snoopypro packet based on what I could learn from the
Wireshark Capture.
I have a couple questions, I understand this might be outside the normal scope
of things here, so if nobody knows
-dev] ethernet over USB
Bill Fassler [EMAIL PROTECTED]
Please respond to : Developer support list for Wireshark
wireshark-dev@wireshark.org
Sent by: [EMAIL PROTECTED]
01/02/2008 18:15
Well I found a packet to packet correlation between the two sniffers and
then I tried to hand dissect
Hey guys, I have been trying to understand ethernet over USB. I have ethernet
over USB working on an embedded development board running a blackfin DSP and
uClinux. I have everthing configured and can network with either linux or
windows. I am trying to understand the protocol and packet