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 sends a flow of data, even when both computers aren't using the link (presumably heartbeat traffic?). Assuming that Linux doesn't use some weird custom header, the USB Forum specifications might be of use.
Hope that helps.
On Jan 31, 2008 10:57 PM, Bill Fassler <
bill.fassler@xxxxxxxxx> wrote:
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 headers, wrappers and such.
In an attempt to understand things I installed snoopypro and upgraded my Wireshark to 99.7, then I ping the windows box and it responds and I capture the traffic using both sniffers (yours and snoopypro). I can not yet however, find a packet for packet correlation. The sequence numbers are different. I suppose that is because Wireshark sequence numbers are soley based on the Ethernet traffic (ARP and PING), when snoopypro picks up the higher layer and the sequence numbers reflect that.
I tried to limit the traffic to just one ping. Figuring that should be easy. It wasn't since apparently the linux
ethernet over USB driver sends stuff out almost constantly regardless of whether there is ethernet traffic.
Any hoooo... you guys are the experts here. I imagine I am making a simple task difficult. How can I understand the ethernet over USB packet better? I am thinking about writing a non-linux based version of this...... and don't understand it enough to even start just yet..
Bill Fassler
Be a better friend, newshound, and
know-it-all with Yahoo! Mobile.
Try it now.
_______________________________________________
Wireshark-dev mailing list
Wireshark-dev@xxxxxxxxxxxxx
http://www.wireshark.org/mailman/listinfo/wireshark-dev
