Results 1 to 7 of 7
I am working on USB Connectivity between android 2.1 Host and Windows Mobiles 6.1 device...When I connect the windows mobile device to android host through USB (in RNDIS Mode), It ...
- 06-01-2011 #1Just Joined!
- Join Date
- Jun 2011
- Posts
- 3
'eth1' instead of 'usb0'
I am working on USB Connectivity between android 2.1 Host and Windows Mobiles 6.1 device...When I connect the windows mobile device to android host through USB (in RNDIS Mode), It is appearing as 'eth1' interface instead of 'usb0' interface.
Why 'eth1' instead of 'usb0' ?
Does behaviour of 'eth1' is same as 'usb0'?
Please provide me some help...
Thanks in advance
Regards,
Ganesh
- 06-01-2011 #2Just Joined!
- Join Date
- May 2011
- Location
- NJ
- Posts
- 45
In RNDIS mode, the device is recognized as a network device.
- 06-01-2011 #3Just Joined!
- Join Date
- May 2011
- Location
- NJ
- Posts
- 45
Apparently, I need 15 posts to post a link, but a quick google on RNDIS behavior will help you with the behavior
- 06-01-2011 #4Just Joined!
- Join Date
- Jun 2011
- Posts
- 3
Re: 'eth1' instead of 'usb0'
Sorry...I didn't give much info on what i have to do...
Case 1: I connected my Samsung Galaxy I7500 phone (android phone) to my Host (android) through USB Cable. It was in ECM Mode.It is detecting as 'usb0' device.
Case 2: I connected Windows Mobile to my Host(android) through USB Cable.It was in RNDIS Mode.It is detecting as 'eth1' device.
Being both phones connected through USB Cable, Why windows phone is detecting as 'eth1' device.
As u have said, It is recognising as network device. But 'usb0' is also network device. So why the difference comes?
[ECM and RNDIS are one and the same.]
Please help me...
Regards,
Ganesh
- 06-01-2011 #5Just Joined!
- Join Date
- May 2011
- Location
- NJ
- Posts
- 45
from the wiki.The Remote Network Driver Interface Specification (RNDIS) is a Microsoft proprietary protocol used mostly on top of USB. It provides a virtual Ethernet link to most versions of the Windows operating system.
Also
from the wiki.These issues complicate third-party implementations.
The USB Implementers Forum (USB-IF) defines at least three non-proprietary USB Communications Device Class (CDC) protocols with comparable "virtual Ethernet" functionality; one of them (CDC-ECM) predates RNDIS and is widely used for interoperability with non-Microsoft operating systems, but it has no native Windows support.
- 06-01-2011 #6Just Joined!
- Join Date
- Jun 2011
- Posts
- 3
RE:'eth1' instead of 'usb0'
Thank You for your support.
- 06-01-2011 #7Just Joined!
- Join Date
- May 2011
- Location
- NJ
- Posts
- 45
No problem.


Reply With Quote